prochattools · stevewesthoek · Sep 29, 2026 · Sep 29, 2026
diff --git a/docs/implementation-plan.md b/docs/implementation-plan.md
@@ -1,6 +1,6 @@
 # ProChat website implementation plan
 
-Status: **website milestone complete**. Implementation, validation evidence, merge, deployment, live route checks, current-main source verification, fresh local browser QA, and safe cleanup of fully-contained branches/worktrees are complete. Feature commit `f09f92aab3327b3672df0d593e50040171cc1295` and renderer-sampling correction PR #8 are deployed as runtime `59a9c61550ca37586091c43f146cfd83023a455c`; main workflow [36602012728](https://github.com/prochattools/prochat/actions/runs/36602012728) succeeded and live `/api/version` matched `origin/main` at deployment. The closeout change is documentation-only, so `main` advances without a runtime redeployment. The correction raises sampling to 24fps / up to 240 frames at 384px and hands off only a complete cache. Fresh local Playwright QA against the merged implementation passed across eight public routes and seven target widths, including reduced motion, responsive navigation/form, and scroll/reversal checks. Mastermind source metadata/index remain stale; a supported dashboard Reindex endpoint exists but the configured local API is unavailable and no Mastermind connector/tool is exposed in this session. This is separate infrastructure follow-up, not a website-closeout blocker.
+Status: **website milestone complete**. Implementation, validation evidence, merge, deployment, live route checks, current-main source verification, fresh local browser QA, and safe cleanup of fully-contained branches/worktrees are complete. Feature commit `f09f92aab3327b3672df0d593e50040171cc1295` and renderer-correction PR #8 were deployed as runtime `59a9c61550ca37586091c43f146cfd83023a455c`; main workflow [36602012728](https://github.com/prochattools/prochat/actions/runs/36602012728) succeeded and live `/api/version` matched `origin/main` at deployment. Documentation-only PRs #9 and #10 advanced `main` without a runtime redeployment. PR #8 corrected measured scroll quantization: 24fps sampling, up to 240 cached frames at 384px, and complete-cache handoff. Fresh local Playwright QA against the merged implementation passed across eight public routes and seven target widths, including reduced motion, responsive navigation/form, and scroll/reversal checks. Mastermind source metadata/index remain stale; a supported dashboard Reindex endpoint exists but the configured local API is unavailable and no Mastermind connector/tool is exposed in this session. This is separate infrastructure follow-up, not a website-closeout blocker.
 
 Last reviewed: 2026-09-29.
 

diff --git a/docs/roadmap.md b/docs/roadmap.md
@@ -1,6 +1,6 @@
 # ProChat website roadmap
 
-Status: **PROCHAT WEBSITE QUALITY PASS / CINEMATIC SITE MILESTONE = COMPLETE.** Feature implementation commit `f09f92aab3327b3672df0d593e50040171cc1295` and the subsequent renderer-sampling correction were deployed; production runtime is `59a9c61550ca37586091c43f146cfd83023a455c` (it matched `origin/main` at deployment). Main workflow [36602012728](https://github.com/prochattools/prochat/actions/runs/36602012728) succeeded, including `build-and-deploy` and `Verify production deployment`. PR #8 corrected live-observed scroll quantization: the ~10.04-second source had only 120 cached frames (~12fps); production now caches up to 240 frames at 24fps and hands off only a complete cache. Production `/api/version` confirms the runtime revision, and all eight public routes returned HTTP 200 after deployment. The current closeout is documentation-only; it advances source `main` without requiring a runtime deployment. Local Playwright QA against the merged implementation covered all eight routes and widths 1440/1280/1024/768/430/390/360, reduced motion, scroll-driven media/chapter reversal, mobile navigation, and Contact controls; CI browser evidence passed. The protected dirty checkout and unique historical branches/worktrees remain preserved. Mastermind's persisted index and registered branch metadata are still stale. A supported dashboard Reindex endpoint exists, but the configured local API at `http://localhost:3000` is unavailable and no Mastermind connector/tool is exposed in this session, so this remains a separate infrastructure follow-up—not a ProChat website defect or a reason to hold this milestone open.
+Status: **PROCHAT WEBSITE QUALITY PASS / CINEMATIC SITE MILESTONE = COMPLETE.** Feature implementation commit `f09f92aab3327b3672df0d593e50040171cc1295` and renderer correction PR #8 were deployed as production runtime `59a9c61550ca37586091c43f146cfd83023a455c`, which matched `origin/main` at deployment. Main workflow [36602012728](https://github.com/prochattools/prochat/actions/runs/36602012728) succeeded, including `build-and-deploy` and `Verify production deployment`. PR #8 corrected measured scroll quantization: the ~10.04-second source had only 120 cached frames (~12fps); production now caches up to 240 frames at 24fps and hands off only a complete cache. Production `/api/version` confirms the runtime revision, and all eight public routes returned HTTP 200 after deployment. Subsequent PRs #9 and #10 were documentation-only and advanced `origin/main` without a runtime redeployment. Local Playwright QA against the merged implementation covered all eight routes and widths 1440/1280/1024/768/430/390/360, reduced motion, scroll-driven media/chapter reversal, mobile navigation, and Contact controls; CI browser evidence passed. The protected dirty checkout and unique historical branches/worktrees remain preserved. Mastermind's persisted index and registered branch metadata are still stale. A supported dashboard Reindex endpoint exists, but the configured local API at `http://localhost:3000` is unavailable and no Mastermind connector/tool is exposed in this session, so this remains a separate infrastructure follow-up—not a ProChat website defect or a reason to hold this milestone open.
 
 Last reviewed: 2026-09-29.
 
@@ -22,7 +22,7 @@ In scope:
 4. Verify prefers-reduced-motion, 1440/1280/1024/768/430/390/360 layouts, route content, menu and Contact interactions, browser errors, and manually inspected screenshots.
 5. LiquidGlass was tested in local Chrome 153 at 1440×900 on both selected surfaces, with the real scroll-rendered page canvas copied and invalidated on each source repaint. Baseline page RAF cadence was 16.62ms average / 16.8ms p95; the context-card and capability-panel prototypes measured 16.48ms / 16.8ms and 16.50ms / 16.8ms respectively. Package-reported rates were 61fps and 60fps; initialization was 66.0ms and 65.8ms; each run handled 96 changed source frames without console errors. The previous 11–15fps estimate was not reproduced and is superseded. Do not adopt the package: screenshots show an inset, doubled-glass seam on both existing CSS panels without a compelling visual gain. Retain the CSS fallback and avoid adding a WebGL context plus frame-copy/invalidation path. Detailed evidence and screenshots are in `docs/implementation-plan.md`.
 6. A pre-sampling-correction local Chrome 153 diagnostic reached the then-120-frame cache and presented 89 tiny-scroll canvas paints in 1.47s (59.99fps); 87 sampled outputs were distinct and the longest gap was 17.6ms. The follow-up 24fps/240-frame renderer was verified separately against the merged implementation; see `docs/implementation-plan.md`. These are local desktop diagnostics, not a cross-device field guarantee.
-7. **Complete (2026-09-29):** feature commit `f09f92a…` and the measured renderer-sampling correction were deployed; production runtime `59a9c61550ca37586091c43f146cfd83023a455c` matched `main` at deployment. PR #8 raised sampling to 24fps (up to 240 frames), kept the pixel budget approximately constant, and publishes only a complete cache. Main workflow [36602012728](https://github.com/prochattools/prochat/actions/runs/36602012728) passed, including `build-and-deploy` and `Verify production deployment`. `/api/version` matched main after deploy, and all eight canonical routes returned HTTP 200. Local Playwright visual/responsive QA against the merged implementation and CI browser evidence passed.
+7. **Complete (2026-09-29):** feature commit `f09f92a…` and renderer correction PR #8 were deployed; runtime `59a9c61550ca37586091c43f146cfd83023a455c` matched `main` at deployment. PR #8 raised sampling to 24fps (up to 240 frames), kept the pixel budget approximately constant, and publishes only a complete cache. Main workflow [36602012728](https://github.com/prochattools/prochat/actions/runs/36602012728) passed, including `build-and-deploy` and `Verify production deployment`. `/api/version` matched main after deploy, and all eight canonical routes returned HTTP 200. Local Playwright visual/responsive QA against the merged implementation and CI browser evidence passed. PRs #9 and #10 later updated only documentation and did not trigger production deployment.
 8. **Housekeeping completed with preserved exceptions:** deleted the fully-contained branches `feature/full-cinematic-marketing-experience-2026-09`, `fix/exact-cinematic-marketing-theme-2026-09`, `feature/homepage-cinematic-scroll-2026-09`, `fix/cinematic-marketing-shell-2026-09`, and `fix/public-refresh-evidence-2026-09`. Removed clean worktrees `prochat-cinematic-shell-fix-2026-09` and `prochat-exact-cinematic-2026-09` after archiving evidence at `/Users/Office/.codex/attachments/prochat-cinematic-housekeeping-evidence-2026-09-29.tar.gz` (303 entries). Unique-history branches/worktrees, the stale registered Mastermind branch pointer, and the protected dirty checkout remain preserved. The old blocked ProChat run `agent-bf55f97a-2222-41e9-b0d7-f3a722a89d97` is confirmed completed. The canonical Mastermind source worktree path is `/Users/Office/Repos/prochattools/web/prochat-mastermind-runtime`; its checkout tracks `origin/main` on `codex/prochat-main-runtime-2026-09`, while registered `branchName` still names `codex/mastermind-prochat-runtime-2026-09-22`. Its persisted index snapshot from 2026-09-28 remains at `00b6473ac23124c45ffa421dd4bff01120dde47d`. The dashboard defines `POST /api/agent/sources/reindex` → `POST /api/sources/reindex`, but the configured local API at `http://localhost:3000` is unavailable and no Mastermind connector/tool is exposed here. No Mastermind-owned state was changed; track source/index synchronization separately from this website milestone.
 
 ## Performance follow-up
@@ -43,4 +43,4 @@ The 2026-09-29 `npm audit --omit=dev` scan also reported 68 findings (4 critical
 
 ## Release gate
 
-The implementation/release and website-quality closeout gates are complete: CI, deployment, deployed-revision verification, route checks, and fresh local browser QA passed. Live checks returned HTTP 200 for `/`, `/evermind`, `/nevermind`, `/mastermind`, `/docs`, `/contact`, `/privacy`, `/terms`, and `/api/version`; deployed runtime is `59a9c61550ca37586091c43f146cfd83023a455c`. The documentation-only closeout merge advances source `main` without a new deployment. Mastermind source/index maintenance is a separate infrastructure follow-up. The next website goal is the LCP investigation below; do not start it as part of this closeout.
+The implementation/release and website-quality closeout gates are complete: CI, deployment, deployed-revision verification, route checks, and fresh local browser QA passed. Live checks returned HTTP 200 for `/`, `/evermind`, `/nevermind`, `/mastermind`, `/docs`, `/contact`, `/privacy`, `/terms`, and `/api/version`; deployed runtime is `59a9c61550ca37586091c43f146cfd83023a455c`. Documentation-only PRs #9 and #10 advanced source `main` without changing that runtime. Mastermind source/index maintenance is a separate infrastructure follow-up. The next website goal is the LCP investigation below; do not start it as part of this closeout.