simpletest/who_need_help
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Record current launch verification evidence

Browse Source
This commit is contained in:
SimpleTest 2026-08-14 00:38:05 +03:00
parent 805a762f89
commit d281db42a8
2 changed files with 51 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/public-launch-checklist.md
View File

@ -52,6 +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`.
## 2. Verify production configuration without exposing secrets
Run both checks against the single ignored production `.env`. The first reports

44
docs/verification.md
View File

@ -1,8 +1,50 @@
# Who Need Help — implementation verification
Observed through 2026-08-13 in the local workspace. This report separates observed
Observed through 2026-08-14 in the local workspace. This report separates observed
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
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.
- 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
`support_confirmation` deliveries and no failed or exceptional email series.
These process-local counters establish the purpose and adapter outcome of
those attempts; they do not prove inbox placement or receipt by a person.
- The scheduled encrypted off-server backup that began on 2026-08-14 at 00:00
EEST completed successfully after 5 minutes 13.266 seconds. It verified the
PostgreSQL custom-format catalog and checksum, created Restic snapshot
`563eb486ee2002fb0bc85b12afe5bd7ef8ada02ac3566c343ac6f83f51e73a1c`,
and passed the isolated restore drill. The independent BuyVM host held the
matching mode-`0600` restore-verified heartbeat and continued to report
readiness and aggregate metrics `up` on its minute schedule.
- Backup-freshness alerting remains deliberately disabled because no operator
maximum acceptable backup age has been selected. The successful daily
execution is therefore evidence of the mechanism, not an approved RPO or
alert threshold.
- The Google Play foreground-service declaration remains saved with the
user-initiated location-sharing task and the retained unlisted demonstration
video. The operator reviewed the video on 2026-08-14 and confirmed that it
visibly covers starting location sharing, the system permission, the active
foreground-sharing state, and stopping sharing. This is submission material,
not evidence of Google approval.
- No remote repository, production release, Play listing contact, shared Caddy
configuration, or frozen-test state changed during this recheck.
## Current local candidate and operations recheck on 2026-08-13
- Application source candidate `02ccebb5b9b0720bf7c40b5be736d4c1a1e9e656` passed the