docs: record ProChat cinematic release closeout

docs/implementation-plan.md

@@ -1,6 +1,6 @@
 # ProChat website implementation plan
 
-Status: cinematic renderer, utility shell, and local validation complete; commit/push and production release remain pending.
+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.
 
 Last reviewed: 2026-09-29.
 
@@ -38,16 +38,16 @@ Local Chrome 153 recorded 89 visible canvas paints in 1.47s (59.99fps), with 87
 
 ### C. Validation and release
 
-Run the repository-supported env/doc integrity, TypeScript, ESLint, design lint, asset validation, production build, security, and relevant browser evidence. Review a diff-based safety pass; stage exact files only; commit and push the continuation branch without rewriting history. Integrate through the repository's normal `main` workflow. Verify workflow and deployment success, `/api/version` full SHA, all eight public routes, media and browser health. Then verify the authoritative worktree is clean and the protected checkout's branch, HEAD, status, and diff fingerprint are unchanged. Commit/push/deployment gates for this release are still pending.
+**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.
 
 ## Known implementation/build debt
 
 `Dockerfile` currently sets placeholder `STRIPE_SECRET_KEY_LIVE` and `STRIPE_WEBHOOK_SECRET_LIVE` values as builder-stage environment variables so retired Stripe module evaluation can pass. They are not real secrets, but they trigger build security warnings. Track a separate narrowly tested refactor to remove this build-time configuration dependency. Never place live credentials in Docker build args or image layers.
 
 ## Next performance gate
 
-The 2026-09-29 single-run local Lighthouse diagnostic measured LCP at `/` 2.91s, `/evermind` 2.86s, `/nevermind` 2.86s, `/mastermind` 2.86s, `/docs` 4.05s, and `/contact` 4.21s. All exceed the ≤2.5s target; CLS was 0 and TBT 0ms. This is a diagnostic sample, not production field data. Next roadmap item: bring canonical public-route LCP under 2.5 seconds without reducing the cinematic experience; investigate the utility-route LCP increase separately.
+In the release workflow's mobile-simulated canonical performance evidence (2026-09-29, run [36573913919](https://github.com/prochattools/prochat/actions/runs/36573913919)), all 8 routes completed and 0/8 met the ≤2.5s LCP threshold. Median LCP: `/` 3.78s, `/evermind` 3.77s, `/nevermind` 3.77s, `/mastermind` 3.77s, `/docs` 4.90s, `/contact` 5.12s, `/privacy` 4.82s, `/terms` 3.85s. CLS was 0 and FCP 1.21–1.22s. Trace attribution marked text as LCP and reported FCP-to-LCP of 0ms (navigation-to-FCP/LCP 107–155ms), so investigate the simulation/metric discrepancy before changing rendering. This evidence step is advisory and did not block CI/deployment; it is not production field data. Next roadmap item: investigate and bring canonical public-route LCP under 2.5s without reducing the cinematic experience.
 
 ## 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. Do not call the work complete on a green local build or successful push alone.
+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.

docs/roadmap.md

@@ -1,6 +1,6 @@
 # ProChat website roadmap
 
-Status: implementation and local release gates pass; current source is based on `main` at `c6731140191791e407a2fb6eb27ac96711883e32`. Production publication of this quality pass is pending the normal `main` release workflow and `/api/version` verification.
+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.
 
 Last reviewed: 2026-09-29.
 
@@ -22,12 +22,12 @@ 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. 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. Update active implementation docs, validate, review, commit, push, merge through the normal `main` workflow, then verify the live revision and routes. Publication is not complete until that verification passes.
-8. Preserve the protected checkout and unrelated repositories/worktrees. After confirmed production success only, reconcile Mastermind source continuity, indexes, and safely removable branches/worktrees; do not delete unique or unverified work.
+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.
 
 ## Performance follow-up
 
-The canonical mobile LCP target is at most 2.5 seconds. A single-run local production-artifact diagnostic on 2026-09-29 (Lighthouse 12.4, Moto G Power 2022 simulation, 4× CPU, slow 4G; diagnostic mode) measured: `/` 2.91s, `/evermind` 2.86s, `/nevermind` 2.86s, `/mastermind` 2.86s, `/docs` 4.05s, `/contact` 4.21s. All six exceeded target; CLS was 0 and TBT was 0ms. Utility-page LCP needs follow-up investigation. These are local lab measurements, not production field data; one run per route is directional rather than a stable baseline. The next website goal is: **Bring canonical public-route LCP under 2.5 seconds without reducing cinematic fidelity.** Do not trade away the requested scroll-driven visuals to satisfy the metric.
+The canonical mobile LCP target is at most 2.5 seconds. The release workflow's mobile-simulated canonical evidence (2026-09-29; run [36573913919](https://github.com/prochattools/prochat/actions/runs/36573913919)) completed all 8/8 routes but met all thresholds on 0/8. Median LCPs were: `/` 3.78s, `/evermind` 3.77s, `/nevermind` 3.77s, `/mastermind` 3.77s, `/docs` 4.90s, `/contact` 5.12s, `/privacy` 4.82s, `/terms` 3.85s. CLS was 0.000 and FCP was 1.21–1.22s. Trace attribution identified text as LCP, with navigation-to-FCP/LCP around 107–155ms and FCP-to-LCP 0ms; the reported LCP values therefore appear dominated by the mobile-simulation timing/measurement context rather than late content rendering and need investigation before optimization. This evidence step is advisory (`continue-on-error`) and did not fail CI or deployment. A prior local Lighthouse run is retained only as historical diagnostic data; these results are not production field data. The next website goal is: **Investigate and bring canonical public-route LCP under 2.5 seconds without reducing cinematic fidelity.** Do not trade away the requested scroll-driven visuals to satisfy the metric.
 
 ## Tracked build hardening
 
@@ -43,4 +43,4 @@ The 2026-09-29 `npm audit --omit=dev` scan also reported 68 findings (4 critical
 
 ## Release gate
 
-Completion requires current-source evidence, clean TypeScript/ESLint/design/asset checks, the production build, relevant security and browser suites, manual desktop/tablet/mobile/reduced-motion review, exact reviewed-file staging, normal GitHub integration and deployment, production `/api/version` equality, route checks, and a clean authoritative implementation worktree. 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. 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.