docs: record ProChat closeout blockers

docs/implementation-plan.md

@@ -1,6 +1,6 @@
 # ProChat website implementation plan
 
-Status: cinematic renderer, utility shell, validation, merge, deployment, and live route checks complete. Feature commit `f09f92aab3327b3672df0d593e50040171cc1295` was merged to `main` as `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`; workflow [36573913919](https://github.com/prochattools/prochat/actions/runs/36573913919) succeeded. Post-deploy source/index continuity and safe repository cleanup remain pending.
+Status: implementation, validation evidence, merge, deployment, live route checks, and safe cleanup of fully-contained branches/worktrees are complete. Feature commit `f09f92aab3327b3672df0d593e50040171cc1295` was merged to production as `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`; workflow [36573913919](https://github.com/prochattools/prochat/actions/runs/36573913919) succeeded and live `/api/version` continues to report that runtime revision. Current `origin/main` is `e569db01e3512575a580fd8425f10fa33b3092f7`. Fresh browser QA is approval-gated on a one-time local gstack utility build. Mastermind's canonical source worktree is now clean and on current main, but its registered branch metadata and persisted index remain stale; no supported refresh/reindex operation was exposed. These are the remaining closeout blockers.
 
 Last reviewed: 2026-09-29.
 
@@ -38,7 +38,7 @@ Local Chrome 153 recorded 89 visible canvas paints in 1.47s (59.99fps), with 87
 
 ### C. Validation and release
 
-**Release complete (2026-09-29):** feature commit `f09f92aab3327b3672df0d593e50040171cc1295` was reviewed and merged through PR #3 to `main` at `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`. Push workflow [36573913919](https://github.com/prochattools/prochat/actions/runs/36573913919) succeeded: CI and docs-integrity passed; browser evidence and API security passed; `build-and-deploy` and `Verify production deployment` passed. Production `/api/version` reports revision/image SHA `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`; `/`, `/evermind`, `/nevermind`, `/mastermind`, `/contact`, `/docs`, `/privacy`, and `/terms` returned HTTP 200. The authoritative feature worktree was clean after merge, and the protected dirty checkout was verified unchanged. Mastermind source/index continuity and final worktree/branch cleanup remain unverified and must use only an authorized, supported mechanism.
+**Release complete (2026-09-29):** feature commit `f09f92aab3327b3672df0d593e50040171cc1295` was reviewed and merged through PR #3 to production `main` at `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`. Workflow [36573913919](https://github.com/prochattools/prochat/actions/runs/36573913919) succeeded: CI, docs-integrity, browser evidence, API security, `build-and-deploy`, and `Verify production deployment` passed. Production `/api/version` reports revision/image SHA `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`; live checks on 2026-09-29 returned HTTP 200 for `/`, `/evermind`, `/nevermind`, `/mastermind`, `/contact`, `/docs`, `/privacy`, `/terms`, and `/api/version`. Current `origin/main` is `e569db01e3512575a580fd8425f10fa33b3092f7` (docs-only follow-up commits). Five fully-contained branches and two clean worktrees were removed; their test/evidence files are preserved in `/Users/Office/.codex/attachments/prochat-cinematic-housekeeping-evidence-2026-09-29.tar.gz` (303 entries). Unique/unverified worktrees and branches were retained. The protected dirty checkout was verified unchanged. Mastermind's `prochat` worktree now tracks current main cleanly at `e569db01`, and the old blocked run is closed, but registered `branchName` and persisted index (`00b6473ac23124c45ffa421dd4bff01120dde47d`) remain stale. Fresh browser QA still awaits approval for its one-time local gstack utility build. No unsupported Mastermind-owned state was edited.
 
 ## Known implementation/build debt
 
@@ -50,4 +50,4 @@ In the release workflow's mobile-simulated canonical performance evidence (2026-
 
 ## Completion evidence
 
-Record test commands/results, screenshot review, measured LiquidGlass comparison, measured LCP, feature and production commits, workflow/deployment result, live version and route checks, final branch/worktree state, preserved-checkout fingerprint, and any remaining warnings. Release evidence is now recorded above; source/index continuity and repository cleanup are still open. Do not call the entire closeout complete until those items are safely resolved or explicitly reported as blocked.
+Release and cleanup evidence is recorded above. Before calling the closeout complete, obtain authorization for the one-time browser utility build, complete fresh browser QA, and use the supported Mastermind source-management operation to refresh registered branch metadata and the persisted index. Final audit must again confirm the protected checkout fingerprint and production revision. Then read this roadmap top-to-bottom and hand off its named next goal: investigate and bring canonical public-route LCP under 2.5 seconds without reducing cinematic fidelity.

docs/repo-status.md

@@ -1,6 +1,6 @@
 # Repository status
 
-Status: the cinematic and utility-page implementation is published and live-verified. Current `origin/main` is `e5d750f471875ad392afe68c4380b42967a0d3fd` (a docs-only release-record follow-up); the currently deployed runtime revision is `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`, confirmed by `/api/version`. The cinematic implementation commit `f09f92aab3327b3672df0d593e50040171cc1295` was merged through PR #3, and the docs correction through PR #4. Mastermind source/index continuity and safe branch/worktree cleanup remain open.
+Status: the cinematic and utility-page implementation is published and live-verified. Current `origin/main` is `e569db01e3512575a580fd8425f10fa33b3092f7`; deployed runtime revision is `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`, confirmed by `/api/version`. The implementation was merged through PR #3; release-record corrections were merged through PRs #4 and #5. Five fully-contained local/remote branches and two clean worktrees were safely removed after preserving their test evidence. Remaining closeout blockers: fresh browser QA needs approval for its one-time local utility build, and Mastermind's persisted `prochat` index/config metadata still names an older revision/branch despite its clean source worktree now tracking current `origin/main`.
 
 Last reviewed: 2026-09-29.
 
@@ -28,3 +28,4 @@ Renderer continuity tests, responsive/reduced-motion and interaction evidence, m
 
 - Canonical mobile LCP target: ≤2.5s; capture actual route measurements before setting the next goal.
 - Docker builder still declares placeholder `STRIPE_SECRET_KEY_LIVE` and `STRIPE_WEBHOOK_SECRET_LIVE` values via `ENV`; these are not credentials, but trigger container-build security warnings. Remove the obsolete build-time dependency in a separately validated change, without passing real secrets to the builder.
+- The canonical Mastermind `prochat` source worktree is `/Users/Office/Repos/prochattools/web/prochat-mastermind-runtime`, clean on `codex/prochat-main-runtime-2026-09` at `e569db01e3512575a580fd8425f10fa33b3092f7`. A bounded exact read observes that revision, but registered branch metadata still says `codex/mastermind-prochat-runtime-2026-09-22` and the persisted index remains at `00b6473ac23124c45ffa421dd4bff01120dde47d`. Refresh/reindex only through a supported Mastermind source-management operation; none was available in this session. The obsolete blocked run was closed. The historical dirty checkout remains unchanged at HEAD `a28ab34eae077f1b2de6dfa072800c1398e4c815`, with diff fingerprint `88d4d903c3a89000ca394da41c3359ff51fa8904eb58611404655182afeb2345`.

docs/roadmap.md

@@ -1,6 +1,6 @@
 # ProChat website roadmap
 
-Status: cinematic/site quality pass is merged and deployed. Feature implementation commit `f09f92aab3327b3672df0d593e50040171cc1295` was merged to `main` as `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`; workflow [36573913919](https://github.com/prochattools/prochat/actions/runs/36573913919) completed successfully, and production `/api/version` reports the deployed `f63dd337…` revision. Post-deploy source/index continuity and safe worktree cleanup remain open.
+Status: cinematic/site quality pass is merged and deployed. Feature implementation commit `f09f92aab3327b3672df0d593e50040171cc1295` was merged to `main` as `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`; workflow [36573913919](https://github.com/prochattools/prochat/actions/runs/36573913919) succeeded, and live `/api/version` still reports `f63dd337…`. Repository cleanup removed five fully-contained local/remote branches and two clean worktrees after archiving their test evidence. The Mastermind `prochat` worktree now tracks clean `origin/main` at `e569db01`, but registered branch metadata and persisted index revision remain stale; refresh/reindex is blocked on an exposed supported source-management operation. Fresh browser QA also awaits explicit approval for the required one-time local gstack browser utility build. Do not treat the overall closeout as complete until those are resolved or explicitly handed off.
 
 Last reviewed: 2026-09-29.
 
@@ -12,7 +12,7 @@ The first four routes share a two-section cinematic page, one full-width navigat
 
 ## Current release goal — ProChat cinematic/site quality pass
 
-The release source of truth is `feature/prochat-cinematic-finalization-2026-09`; local validation was performed in the managed `prochat-quality-final` worktree. Do not modify the protected dirty checkout at `/Users/Office/Repos/prochattools/web/prochat`.
+The production source of truth is `main` at `e569db01e3512575a580fd8425f10fa33b3092f7`; deployed runtime remains `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`. Local validation evidence is recorded in the managed `prochat-quality-final` worktree and in this document. Do not modify the protected dirty checkout at `/Users/Office/Repos/prochattools/web/prochat`.
 
 In scope:
 
@@ -23,7 +23,7 @@ In scope:
 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. Current local Chrome 153 diagnostics reached the 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. Slow and rapid down/up scrolling plus repeated reversals on all four core routes produced over 500 distinct sampled outputs per route, zero transparent visible-canvas samples, and no console errors. The focused browser suite passed 10/10 in system Chrome with H.264 enabled. This is a local desktop diagnostic, not a cross-device field guarantee.
 7. **Complete (2026-09-29):** feature commit `f09f92a…` was reviewed and merged to `main` as `f63dd337…`; the release record was corrected after deployment. Workflow [36573913919](https://github.com/prochattools/prochat/actions/runs/36573913919) passed, including `build-and-deploy` and `Verify production deployment`. Production `/api/version` matches `f63dd337…`; the eight canonical routes returned HTTP 200. Release evidence and remaining performance gaps are recorded below and in `docs/implementation-plan.md`.
-8. Preserve the protected checkout and unrelated repositories/worktrees. Reconcile Mastermind source continuity/indexes only through a supported, authorized mechanism; the available source connector was unauthorized, so no source mutation was made. Keep branches/worktrees with unique or unverified work; post-deploy cleanup is still pending a safe per-branch audit.
+8. **Housekeeping completed with preserved exceptions:** deleted the fully-contained local and remote 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 the two clean worktrees `prochat-cinematic-shell-fix-2026-09` and `prochat-exact-cinematic-2026-09` after archiving their test/evidence at `/Users/Office/.codex/attachments/prochat-cinematic-housekeeping-evidence-2026-09-29.tar.gz` (303 archive entries). Unique/unverified branches and worktrees remain preserved. The protected dirty checkout is unchanged. The old blocked Mastermind run `agent-bf55f97a-2222-41e9-b0d7-f3a722a89d97` is closed. The canonical Mastermind source worktree is clean on `codex/prochat-main-runtime-2026-09` at current `origin/main` `e569db01`; however, its registered `branchName` still names the obsolete `codex/mastermind-prochat-runtime-2026-09-22` branch, and the persisted index is still at `00b6473ac23124c45ffa421dd4bff01120dde47d` although bounded exact reads observe `e569db01`. No supported source configuration/reindex operation is exposed in this session, so this remains blocked and must not be “fixed” by directly editing Mastermind-owned state.
 
 ## 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 gate is complete: CI, deployment, production revision equality, and route checks passed. Remaining closeout is the post-deploy continuity/branch audit noted above; the separate LCP target remains open. A successful local build or push alone is not release completion.
+The implementation/release gate is complete: CI, deployment, production revision equality, and route checks passed. On 2026-09-29, live checks again returned HTTP 200 for `/`, `/evermind`, `/nevermind`, `/mastermind`, `/docs`, `/contact`, `/privacy`, `/terms`, and `/api/version`; deployed revision remains `f63dd3374c2acd4ecfbc837bfe899569eb4a3a23`. Remaining closeout blockers are the approval-gated fresh browser QA and supported Mastermind source/index refresh described above. The separate LCP target remains open and is the next website roadmap goal once closeout is resolved. A successful local build or push alone is not release completion.