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

Record final candidate verification evidence

Browse Source
This commit is contained in:
SimpleTest 2026-08-13 07:54:50 +03:00
parent df6396df8a
commit 3c8c0b3cf7
1 changed files with 17 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
docs/verification.md
View File

@ -5,32 +5,34 @@ results from product limits and unknown production properties.
## Current local candidate and operations recheck on 2026-08-13
- Application source candidate `67fd3feba7861cb8a02217c8561d59a1348bb79c` passed the
- Application source candidate `df6396df8adbac982c145d5e0629feaacedcd304` passed the
complete isolated `scripts/quality.sh` pipeline in user-systemd unit
`codex-heavy-wnh-full-quality-67fd3fe-20260813-055440-3469820.service`.
ExUnit reported 470 passing tests with seed `370513`; the fourteen browser
`codex-heavy-wnh-final-quality-df6396d-20260813-074825-2662087.service`.
ExUnit reported 470 passing tests with seed `358182`; the fourteen browser
map tests passed; every configured quality and security gate passed; and the
final Debian 13.6 runtime-image scan reported zero detected
vulnerabilities. The unit exited successfully after 3 minutes 56.093
seconds with a measured 319.5 MiB systemd-unit memory peak. Exact-name
vulnerabilities. The unit exited successfully after 2 minutes 24.548
seconds with a measured 212.7 MiB systemd-unit memory peak. Exact-name
inspection after the run found no remaining run-scoped container, network,
volume, or temporary quality/security image.
- The same candidate passed the complete isolated browser E2E suite in
Chromium, Firefox, and WebKit: 63 expected tests passed, with zero skipped,
unexpected, or flaky results, in 318.724 seconds. The run covered desktop
Chromium, Firefox, and WebKit: 63 expected tests passed, with zero
unexpected or flaky results, in 324.826 seconds. Three production-only staff
queue checks were intentionally skipped because their run-scoped production
fixtures do not exist in the local E2E environment. The run covered desktop
and phone accessibility, registration and account settings, request and
activity workflows, private chat, consent-based tracking, handover and blind
reviews, notifications, viewport discovery and clustering, staff queues,
localization, and active-node failure recovery. The isolated user-systemd
unit
`codex-heavy-wnh-full-e2e-67fd3fe-20260813-061049-3960219.service`
completed successfully after 6 minutes 19.128 seconds with a 65.6 MiB
unit-level memory peak. Its structured result is retained at
`output/e2e/20260813031050-3960590/results.json`; exact-name inspection found
no remaining run-scoped container, network, volume, or temporary image.
localization, and active-node failure recovery. The structured result is retained at
`output/e2e/20260813041912-1796685/results.json`; exact-name inspection found
no remaining run-scoped container, network, volume, or temporary image. A
focused local replay of the three personal-data support workflows passed in
27.323 seconds with no skips, unexpected results, or flakes; its structured
result is retained at
`output/e2e/20260813033312-437829/results.json`.
- A fresh read-only production release plan compared this candidate with
production revision `dafcdb36cbe221af0c880fd05da3321e181ddd2c`. It observed
twenty-seven pending
thirty-one pending
commits, one reviewed `application_safe` migration
(`20260812120611_allow_inbox_only_nearby_subscriptions.exs`), external
PostgreSQL 18.4, unchanged shared-edge routing, and all twelve environment