Record current production E2E proof

docs/verification.md

@@ -3,6 +3,52 @@
 Observed through 2026-08-09 in the local workspace. This report separates observed
 results from product limits and unknown production properties.
 
+## Current production E2E and isolation proof on 2026-08-09
+
+- Read-only inspection observed the independent production checkout at
+  `f0cb936854343be12ce58284d872c68c701ad7f3`, Compose project
+  `who_need_help_production`, external database `who_need_help_production`, and
+  one healthy application container with zero restarts. Public readiness
+  returned the exact `{"status":"ready"}` response before and after the browser
+  verification.
+- Production E2E run `production-e2e-20260809-f0cb936-r3` passed both Chromium
+  scenarios: Activity approval/privacy/reporting and the two-person medicine
+  help flow with realtime chat, consent-based tracking, handover, completion,
+  and blind reviews. Playwright recorded two expected passes, zero unexpected
+  results, zero skipped tests, and zero flaky tests in 46.0 seconds. Evidence is
+  retained at
+  `output/production-full-e2e/production-e2e-20260809-f0cb936-r3/`.
+- The exact cleanup manifest records `cleanup_verified=true`. Its target and
+  deletion totals agree for all 26 relationship types, including six users,
+  six user tokens, two requests, three assignments, one Activity, two request
+  messages, two Activity messages, one tracking session, two reviews, one
+  report, one category proposal, six audit events, two abuse signals, eleven
+  notifications, and fourteen run-owned Oban jobs. A direct production query
+  found zero users with the run prefix after cleanup.
+- Every measured product-table count returned to its pre-run value. The global
+  `oban_jobs` total was one row higher in the after snapshot. A subsequent
+  read-only time-bounded query observed the production cron inserting
+  `WhoNeedHelp.Workers.ExpireRequests` maintenance jobs at 14:19, 14:20, and
+  14:21 UTC, including the 14:21 job between the browser completion and the
+  after snapshot. The run-owned fourteen job IDs were separately deleted and
+  verified absent by the cleanup manifest; the global count difference is
+  therefore concurrent maintenance activity rather than retained E2E data.
+- Both local verifier images, every verifier container, the remote temporary
+  evidence directory, and every run-scoped fixture record were absent after
+  cleanup. The immutable production application image remained present.
+- Independent read-only inspection observed the frozen hackathon-test checkout
+  still at `cf7bacdf61ffb171ebac85e32dfcf12bc6972d59`, with a clean worktree,
+  healthy application, PostGIS, and Mailpit containers, and public readiness
+  returning `ready`. The production E2E did not recreate or restart those
+  containers and did not push Git.
+- Evidence SHA-256 values are
+  `16287ae10349b509ecabd3de0021bcc7764c201748efb941c9647acc318dec9e`
+  for `browser/results.json`,
+  `54ad93cbe6e541e8f0cd3663e9e63155fd96b816ee4550f947af5f1d6ea2e55c`
+  for `fixture.json`, and
+  `b6513900d7b44aae5b1b79444df6a9de88fa0f78724f46fc81e2cbf47bf743f7`
+  for `fixture-cleanup.log`.
+
 ## Production application release on 2026-08-09
 
 - The reviewed application-only release advanced the detached production