Record deterministic production E2E evidence
This commit is contained in:
parent
23776e296b
commit
bad9ca5b62
|
|
@ -3177,3 +3177,43 @@ promoted.
|
||||||
the exact mutation and cleanup scope. No production E2E run was executed,
|
the exact mutation and cleanup scope. No production E2E run was executed,
|
||||||
no production or frozen-test deployment was changed, and the public Git
|
no production or frozen-test deployment was changed, and the public Git
|
||||||
remote was not pushed.
|
remote was not pushed.
|
||||||
|
|
||||||
|
# 2026-08-14 deterministic-map production E2E replay
|
||||||
|
|
||||||
|
- The external OpenStreetMap boundary probe returned HTTP 200, `image/png`,
|
||||||
|
and a valid PNG payload. The browser flow then used the harness-owned
|
||||||
|
deterministic PNG response only for exact OpenStreetMap tile URLs, while
|
||||||
|
application requests and browser errors remained subject to the strict
|
||||||
|
failure policy. The focused browser-policy suite passed all five tests.
|
||||||
|
- Temporary production run `production-e2e-20260814-23776e2` passed all three
|
||||||
|
Chromium scenarios: activity approval/privacy/reporting, the complete
|
||||||
|
two-person medicine-help flow, and read-only staff visibility of run-scoped
|
||||||
|
support/legal fixtures. The isolated unit
|
||||||
|
`codex-heavy-wnh-prod-e2e-23776e2-20260814-041855-1873019.service` exited
|
||||||
|
successfully after 3 minutes 16.370 seconds with a 51.7 MiB memory peak.
|
||||||
|
- The browser console evidence contains no error or warning entry. Readiness
|
||||||
|
was `ready` before and after the browser flow. Exact manifest cleanup removed
|
||||||
|
all run-owned users, tokens, requests, assignments, chats, activity records,
|
||||||
|
reviews, reports, support/legal rows, notifications, audit events, tracking
|
||||||
|
state, and fourteen exact Oban jobs. Cleanup verification found zero
|
||||||
|
remaining run-prefix users and no recorded fixture relationship.
|
||||||
|
- Every tracked product-table total returned to its pre-run value. The global
|
||||||
|
Oban table contained one additional row after the run; its concurrent source
|
||||||
|
is unknown, while every run-scoped Oban job was individually recorded,
|
||||||
|
removed, and verified absent.
|
||||||
|
- The complete isolated quality/security gate for local revision `23776e2`
|
||||||
|
passed 480 ExUnit tests plus formatting, compilation, xref, Credo, Sobelow,
|
||||||
|
Dialyzer, dependency, secret, container, Compose, Helm, migration, release,
|
||||||
|
rollback, backup, and observability checks. The final Debian 13.6 runtime
|
||||||
|
scan reported zero detected vulnerabilities. Unit
|
||||||
|
`codex-heavy-wnh-quality-23776e2-20260814-042628-2092739.service` completed
|
||||||
|
after 4 minutes 44.774 seconds with a 313.6 MiB memory peak and no swap. Its
|
||||||
|
run-scoped containers, networks, volumes, and temporary images were absent
|
||||||
|
afterward.
|
||||||
|
- Read-only post-run inspection found production clean at revision
|
||||||
|
`f1947f2264a6a51da4eb8a6a11ff83b8161f1f64`, healthy with zero restarts and
|
||||||
|
public readiness `ready`. The frozen hackathon test remained clean at
|
||||||
|
`cf7bacdf61ffb171ebac85e32dfcf12bc6972d59`; its application, database and
|
||||||
|
Mailpit containers remained healthy and public readiness remained `ready`.
|
||||||
|
The remote repository, Caddy, production release, and frozen-test deployment
|
||||||
|
were unchanged.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue
Block a user