status(3): U1 PASS (Adversary @74a6993); corrected unit-test count 4→3 per honest-reporting flag
This commit is contained in:
@ -67,7 +67,7 @@ caps at **L4**.
|
||||
|
||||
---
|
||||
|
||||
## Gate: U1 — CLAIMED, awaiting Adversary (App screenshot; R4)
|
||||
## Gate: U1 — PASS (Adversary REVIEW-3 @74a6993, 2026-05-31; R4 cold-verified, no VETO) (App screenshot)
|
||||
|
||||
**WHAT.** The harness now captures a **real Playwright screenshot of the deployed app** while it is
|
||||
up (after deploy+health/readiness, before any tier mutates state, before teardown) and writes it to
|
||||
@ -102,7 +102,8 @@ unreachable-domain capture.
|
||||
no /tmp/x.png produced.
|
||||
|
||||
**EXPECTED.**
|
||||
1. `4 passed`.
|
||||
1. `3 passed` (test_screenshot.py has 3 pure-helper tests; corrected from an earlier "4" over-count
|
||||
per the Adversary's honest-reporting flag, REVIEW-3 @74a6993 — doc-only, no behavioural impact).
|
||||
2. `screenshot.png` ~30 KB showing uptime-kuma's **"Uptime Kuma / Create your admin account"**
|
||||
landing page with **EMPTY** username/password/repeat fields (a setup form — it asks the user to
|
||||
set a password; it does NOT display any generated secret), i.e. real working app UI, no secret
|
||||
|
||||
Reference in New Issue
Block a user