From e596af24d97144f4e98b13e9c70dfbb7413e7f83 Mon Sep 17 00:00:00 2001 From: SimpleTest Date: Tue, 25 Aug 2026 21:55:26 +0300 Subject: [PATCH] Record production release verification --- docs/verification.md | 48 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) diff --git a/docs/verification.md b/docs/verification.md index 4ed8ef3..d8b10ab 100644 --- a/docs/verification.md +++ b/docs/verification.md @@ -3461,6 +3461,54 @@ promoted. deployment, shared Caddy, and the public Git remote were not changed or pushed. +# 2026-08-25 app-only production release and post-release E2E + +- The read-only production release plan selected exact local commit + `14d14bf4a084adb2759af254d39ee12b6cdc9e7c`, classified the change as + `application_safe`, found no pending migrations, and excluded shared Caddy + and the frozen hackathon test deployment. The confirmed app-only release + built immutable image `who-need-help:production-14d14bf4a084`, created and + independently verified the pre-release PostgreSQL backup, and recreated only + the production application container. +- The release unit + `codex-heavy-wnh-production-release-14d14bf-20260825-213854-2163339.service` + completed successfully in 1 minute 17.6 seconds with a 103.2 MiB memory peak + and zero swap use. Its rollback manifest is stored on the production host at + `/srv/who_need_help-production/output/releases/20260825T183951944679341Z-14d14bf4a084/rollback-manifest.txt`; + it records previous commit `bb7eb58c8f14d8936cae0e968b50ae721516d213`, + target commit `14d14bf4a084adb2759af254d39ee12b6cdc9e7c`, and successful + `application_safe` completion. +- After release, production Google sign-in was exercised through the existing + authenticated browser session. Google returned the established + `simpletestxxx@gmail.com` account directly to the application, the signed-in + header appeared with the `Welcome back!` flash, and the browser console + contained no error or warning entry. A production landing-page screenshot is + retained at `output/playwright/prod-google-login-success.png`. +- The isolated post-release browser unit + `codex-heavy-wnh-production-e2e-postrelease-20260825-20260825-214429-2319815.service` + completed successfully in 7 minutes 16.824 seconds with a 51.8 MiB memory + peak and zero swap use. All three production scenarios passed: activity + approval/privacy/reporting/moderation; requester-helper medicine tracking, + realtime chat, handover and blind reviews; and the run-scoped support/legal + workflow. Evidence is retained under + `output/production-full-e2e/production-e2e-20260825-postrelease/`. +- Cleanup removed the exact run-owned fixture: six synthetic users, two help + requests, three assignments, two messages, one activity, its two + participants and two activity messages, four support requests, two content + removal notices, one report, two reviews, one tracking session, and the + associated notifications, jobs, audit events and tokens. Cleanup verification + succeeded, the run prefix count was zero before and after, and all monitored + application-table counts were identical before and after. Both readiness + samples returned the exact `{"status":"ready"}` payload. No disposable + post-release E2E image remained referenced locally. +- Final read-only host inspection observed production image + `who-need-help:production-14d14bf4a084` healthy with zero restarts. The frozen + test application remained on `who-need-help:test-cf7bacdf61ff`, and shared + Caddy remained on `who-need-help:caddy-production-a7412c65b51a`; neither was + recreated by the app-only release or E2E. Both public readiness endpoints + returned the exact ready payload. The public Git branch remained at + `921e04b3608007675e22e7e26e0beb3975dbba58`; no remote write was performed. + # 2026-08-25 Google Play Internal v4 and contact recheck - Read-only authenticated Play Console inspection showed **Internal testing**