Record current production browser E2E

docs/verification.md

@@ -3875,3 +3875,33 @@ promoted.
   passed as recorded above.
 - These checks did not change the frozen hackathon test deployment, shared
   Caddy, production application, Play Console, or public Git remote.
+
+# 2026-08-26 production full-browser E2E replay
+
+- The read-only plan identified the compact production target at commit
+  `305bdebdd1912384e9774ef577b8e56c89713bee`, database
+  `who_need_help_production`, healthy container
+  `who_need_help_production-app-1`, zero restarts, and zero existing users with
+  the selected run prefix. Operator-email mode was disabled.
+- The explicitly scoped run
+  `production-e2e-20260826-final` executed in isolated user-systemd scope
+  `codex-heavy-wnh-prod-e2e-run-20260826-20260826-005056-3014046.scope`.
+  Chromium passed all three scenarios in 1.1 minutes: activity approval and
+  moderation, the two-party medicine request including chat, tracking,
+  handover and blind reviews, and staff visibility of run-scoped support and
+  legal records.
+- Readiness returned the exact ready payload before and after the browser run.
+  Every monitored application-table count in `database-before.json` and
+  `database-after.json` matched, `fixture_prefix_count` was zero after cleanup,
+  and the run manifest recorded `cleanup_verified=true`. The transient tools
+  and browser images were absent after the run, and the isolated scope ended
+  with `Result=success`.
+- Final host inspection found production healthy on image
+  `who-need-help:production-305bdebdd191`. Frozen test remained healthy on
+  `who-need-help:test-cf7bacdf61ff`, shared Caddy remained on
+  `who-need-help:caddy-production-a7412c65b51a`, and the public Git main branch
+  remained `921e04b3608007675e22e7e26e0beb3975dbba58`.
+- Evidence is retained under
+  `output/production-full-e2e/production-e2e-20260826-final`. No email was sent,
+  no real-user status or role was changed, and no test, Caddy, Play, or public
+  Git mutation was performed.