From 0bac8bdbca8993c4599104c8f57db4f67942c30e Mon Sep 17 00:00:00 2001 From: SimpleTest Date: Mon, 20 Jul 2026 19:15:33 +0300 Subject: [PATCH] docs: record final pre-production audit evidence --- docs/verification.md | 63 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+) diff --git a/docs/verification.md b/docs/verification.md index e7e8092..502957f 100644 --- a/docs/verification.md +++ b/docs/verification.md @@ -858,6 +858,69 @@ lint, observability configuration, rendered-manifest scanning, and all configured runtime image scans. Every reported HIGH/CRITICAL vulnerability count was zero. +## Final pre-production audit replay on 2026-07-20 + +The final manual code pass fixed LiveView form metadata leaking into dynamic +category data, stale review state across replicas, forms retaining submitted +report/proposal/chat content, an invalid leave action on completed activities, +and blocked-organizer metadata remaining visible in a participant's activity +history. Regression coverage now includes all of those cases. + +- `./scripts/quality.sh` passed on the final source state with 243/243 ExUnit + tests, format and warnings-as-errors compilation, xref, Credo, Sobelow, + Dialyzer, Hex/npm audits, Compose and Helm rendering, observability + validation, source secret/misconfiguration scanning, and every configured + production and infrastructure image scan. The reported configured-threshold + vulnerability count was zero. +- The final isolated 50,000-row database replay measured public help discovery + at 0.144 ms and the blocked participant-activity page at 22.837 ms for 25 + returned rows on this workstation. The aggregate leaderboard and helper + reputation queries measured 45.006 ms and 38.443 ms respectively. These are + observations, not production resource requirements. Evidence is + `output/db-scale/20260720154617-630777`. +- The 30-second isolated load run used 3 web and 2 worker replicas. It completed + 38,936 HTTP requests and 2,060 WebSocket sessions with zero HTTP failures; + overall HTTP p95 was 5.321 ms. It also completed 1,820 authenticated + LiveView/chat/tracking cycles. Peak sampled container memory was 296-324 MB + per web replica, 205-219 MB per worker, 121 MB for PostgreSQL, and about + 1.54 GiB when summing the seven measured runtime-container maxima. Database + sampling observed no deadlocks, lock waits, temporary files, or rollbacks + during the run. Evidence is + `output/performance/final-current-20260720`. +- The subsequent replacement drill recorded 650/650 successful readiness + samples, a five-node BEAM cluster, cross-node PubSub, healthy web/worker + recovery, and an Oban probe completing on attempt 2 after its intentional + first failure. Evidence is + `output/resilience/final-current-resilience-20260720`. +- A visible-browser replay on `https://whoneedhelp.imalto.site` covered + registration and magic login, account/profile/privacy controls, social-link + semantics, medicine request creation and matching, private realtime chat, + optional live tracking UI and cleanup, handover, double confirmation, + double-blind reviews, activity creation/join approval/exact-location privacy, + group chat and completion, reports/moderation/audit evidence, category + proposal/voting/moderation, and blocking in both directions. The final fresh + post-deployment tab reported zero console errors and zero warnings. +- The first public automation replay exposed two verification defects after the + UI fixes: duplicate valid review status text made a broad locator ambiguous, + and a committed password change lost only its redirect GET to + `ERR_NETWORK_CHANGED`. Commit `9463009` scopes the review assertion to the + persistent status and submits the password mutation only once before + recovering through an idempotent settings GET. The clean replay passed 3/3. + Evidence is `output/staging-full-e2e/20260720160445-1004343`. +- The final HTTPS PWA replay passed 1/1, Android/browser chat and tracking + passed twice, and the packaged native staging APK passed its Android 37 + public-origin smoke. Evidence is + `output/staging-pwa-e2e/20260720160533-1019120`, + `output/android-browser-staging-e2e/20260720160544-1022997`, and + `output/android-staging-smoke/20260720160743-1061722`. + +The manually created browser-audit user, request, assignment, activity, +messages, tracking session, reviews, reports, category proposals, vote, abuse +signals, audit events, and Mailpit messages were removed by exact identifiers. +The existing helper account was restored to role `user`, no password, and no +blocks. Post-cleanup counts retained two users plus one unrelated request and +assignment; those unrelated rows were not changed. + ## Known work before a public production launch - Replace the temporary staging origin with the production-owned domain and