1.7 KiB
1.7 KiB
BACKLOG — phase ghost
Build backlog
- Re-inventory current PR/branch/comment/build state — PR#7 is the sole current upgrade PR; historical PR#4 is closed
- Trigger fresh post-proxy
!testmeon PR#7 (14575de6) — comment15814, Drone build #1332 - Watch build #1332 and collect tier/teardown evidence — success, level 5/5, all lifecycle tiers and lint passed
- Classify the fresh retry and update the operator-facing PR state — Gitea result comment
15815reports passed - Verify no Ghost resources leak after the retry — no
ghos-*/dev-ghoststacks, services, or volumes - M1 current evidence Adversary-verified — PASS @2026-09-07T21:29:58Z
- M2 current operator-ready outcome Adversary-verified — PASS @2026-09-07T21:29:58Z
Adversary findings
- [adversary] [A1] Build #585 must NOT be used as the "clean post-proxy pass" — it ran pre-proxy (03:59Z vs proxy fix at 05:38Z) and tested PR#5 (cfold probe), not PR#4. A genuine post-proxy !testme on PR#4 is required for M1. @2026-06-13T06:22Z — CLOSED: Builder used build #612 (post-proxy, 06:13Z), not #585. M1 PASS @06:38Z
- [adversary] [A2]
update_config.monitoris likely the root cause of upgrade timing failures — builds #557 and #578 both failed withUpdateStatus=paused, NOT VIP exhaustion. @2026-06-13T06:22Z — CLOSED: Build #612 passed post-proxy confirming infra-confound. Operator comment explains MySQL timing under load. M1+M2 PASS @06:38Z - [adversary] [A3] PR#5 (cfold probe) should be closed once PR#4 has its verdict — not the canonical upgrade. @2026-06-13T06:22Z — CLOSED: PR#5 closed (verified). M2 PASS @06:38Z