# BACKLOG — phase ghost

## Build backlog

- [x] Inventory PR/branch/comment/build state — done (see STATUS-ghost.md)
- [x] Trigger fresh post-proxy !testme on PR#4 (d88f5801) — triggered 06:12Z, PASSED build #612 level 5/5
- [x] Watch run, collect logs — all 5 tiers passed
- [x] Document infra-confounded prior failures; operator comment posted on PR#4
- [x] Close PR#3 (superseded) — closed with comment
- [x] Close PR#5 (cfold probe artifact) — closed with comment
- [x] Claim M1 — CLAIMED 2026-06-13T06:35Z, awaiting Adversary PASS
- [x] Claim M2 — CLAIMED 2026-06-13T06:35Z, awaiting Adversary PASS

## Adversary findings

- [x] [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**
- [x] [adversary] **[A2] `update_config.monitor` is likely the root cause of upgrade timing failures** — builds #557 and #578 both failed with `UpdateStatus=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**
- [x] [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**