Reconcile current launch evidence
This commit is contained in:
parent
bad9ca5b62
commit
8e5073a7a5
|
|
@ -52,13 +52,14 @@ support/legal browser replay passed in Chromium, Firefox, and WebKit and left
|
|||
no run-scoped container, network, or temporary image. Exact email-flow,
|
||||
migration, and cleanup evidence is recorded in `docs/verification.md`.
|
||||
|
||||
The latest application-code candidate `dd10e2d` subsequently passed the full
|
||||
isolated pipeline on 2026-08-13 with 479 ExUnit tests, every configured quality
|
||||
and security gate, and zero detected runtime-image vulnerabilities. Later local
|
||||
commits through `805a762` modify documentation only. Production remains on
|
||||
clean revision `dbfb01959816`; neither the frozen hackathon test deployment nor
|
||||
the remote repository was changed. Exact current-candidate and 2026-08-14
|
||||
operations evidence is recorded in `docs/verification.md`.
|
||||
The later production-E2E harness candidate `23776e2` passed the complete
|
||||
isolated pipeline on 2026-08-14 with 480 ExUnit tests, every configured quality
|
||||
and security gate, and zero detected runtime-image vulnerabilities. Production
|
||||
remains on clean application revision `f1947f2264a6`; the local commits after
|
||||
that revision change only the throwaway production-E2E verifier and its
|
||||
evidence. The frozen hackathon test deployment remained unchanged. Exact
|
||||
current-candidate and 2026-08-14 operations evidence is recorded in
|
||||
`docs/verification.md`.
|
||||
|
||||
## 2. Verify production configuration without exposing secrets
|
||||
|
||||
|
|
|
|||
|
|
@ -5,20 +5,20 @@ results from product limits and unknown production properties.
|
|||
|
||||
## Current local candidate and production operations recheck on 2026-08-14
|
||||
|
||||
- The latest application-code candidate `dd10e2d` passed the complete isolated
|
||||
`scripts/quality.sh` pipeline in user-systemd unit
|
||||
`codex-heavy-wnh-inbound-quality-final3-20260813-232623-1306876.service`.
|
||||
ExUnit reported 479 passing tests; every configured quality and security gate
|
||||
- The later production-E2E harness candidate `23776e2` passed the complete
|
||||
isolated `scripts/quality.sh` pipeline in user-systemd unit
|
||||
`codex-heavy-wnh-quality-23776e2-20260814-042628-2092739.service`. ExUnit
|
||||
reported 480 passing tests; every configured quality and security gate
|
||||
passed; and the final runtime-image scan reported zero detected
|
||||
vulnerabilities. The run completed successfully after 6 minutes 2.323
|
||||
seconds with a measured 371.6 MiB systemd-unit memory peak. Commits after
|
||||
`dd10e2d` and through local revision `805a762` change documentation only and
|
||||
do not change the tested application runtime.
|
||||
- Production remained on independent clean revision `dbfb01959816` and returned
|
||||
the expected ready payload from its private readiness endpoint. The production
|
||||
application container was healthy and used about 183.5 MiB at the read-only
|
||||
sample. This observation did not deploy the local candidate, restart a
|
||||
container, or modify the frozen hackathon test deployment.
|
||||
vulnerabilities. The run completed successfully after 4 minutes 44.774
|
||||
seconds with a measured 313.6 MiB systemd-unit memory peak and no swap.
|
||||
- Production remains on independent clean application revision
|
||||
`f1947f2264a6a51da4eb8a6a11ff83b8161f1f64`. The local commits after that
|
||||
revision change only the throwaway production-E2E verifier and its evidence;
|
||||
they do not change the deployed application runtime. The public readiness
|
||||
endpoint returned the expected `ready` payload and the application container
|
||||
was healthy at the 2026-08-14 recheck. No application release, frozen-test
|
||||
change, or Caddy change was performed by this recheck.
|
||||
- Protected production metrics reported an idle BEAM scheduler run queue of
|
||||
zero and 134,722,016 bytes of BEAM VM memory. Since the current production
|
||||
process started, the fixed-purpose email counter recorded eight successful
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user