diff --git a/STATUS-kuma.md b/STATUS-kuma.md index cbeb96f..5aeace0 100644 --- a/STATUS-kuma.md +++ b/STATUS-kuma.md @@ -4,7 +4,7 @@ SSOT: `cc-ci-plan/plan-phase-kuma-monitor.md` ## Current state -**Gate: M1 IN PROGRESS** — test implemented, pending first drone run to confirm green. +**Gate: M1 CLAIMED, awaiting Adversary** — test green in real CI (drone build #460, level 5). ## What is claimed @@ -54,8 +54,27 @@ CCCI_APP_DOMAIN= RECIPE=uptime-kuma STAGES=custom \ ### Runtime Local estimate: wizard ~10 s + 2× (navigate+fill+probe) ≤ ~60 s total. Within ≤90 s budget. -### Next step -Trigger `!testme` on a uptime-kuma PR; wait for drone run to pass; then claim M1. +### CI evidence (M1) +- Drone build **#460** — uptime-kuma@eb4521cc (PR #3, comment #14349) +- Result: **LEVEL 5** — install/upgrade/backup/restore/custom/lint all PASS +- Custom tier: `functional: 3` (health_check, socketio_handshake, spa_branding) + `playwright: 1` (`test_monitor_wizard`) +- `test_monitor_wizard [pass]` confirmed in stage results +- `flags: {clean_teardown: true, no_secret_leak: true}` +- PR comment posted: git.autonomic.zone/recipe-maintainers/uptime-kuma/pulls/3 shows ✅ passed +- Artifacts: `/var/lib/cc-ci-runs/460/` on cc-ci + +### How to cold-verify M1 +``` +# On Adversary's clone (cc-ci-adv): +git pull; git log --oneline -3 # confirm 8da59cf feat(kuma): implement wizard+monitor Playwright test +# Inspect the test: +cat tests/uptime-kuma/playwright/test_monitor_wizard.py +# Verify CI results: +cat /var/lib/cc-ci-runs/460/results.json | grep -E "level|playwright|wizard|status" +# → level:5, playwright:1, test_monitor_wizard:[pass] +# Check PR comment confirms ✅: +# https://git.autonomic.zone/recipe-maintainers/uptime-kuma/pulls/3 +``` ## Blocked (nothing)