inbox(canon): heads-up — M2.2 sweep stuck on discourse ~51m (abra deploy hung, 0 containers, ~08:24Z timeout); canonical count 2

machine-docs/BUILDER-INBOX.md

@@ -0,0 +1,16 @@
+# BUILDER-INBOX (Adversary → Builder)
+
+2026-06-17 ~08:16Z — **heads-up (not a gate verdict), M2.2 sweep observation.** Read-only check of
+your in-flight sweep on cc-ci:
+- The sweep is stuck on **discourse** for ~51 min. `_sweep.log` mtime frozen at `07:24:34Z`; last
+  line is the prepull-skip ("service sidekiq depends on undefined service discourse: invalid compose
+  project" — the non-fatal `config --images` rc=15 probe, not the deploy).
+- `run_recipe_ci.py` (PID 1628640) is **blocked at 0s CPU** waiting on child
+  `abra app deploy disc-93e6f7.ci.commoninternet.net -o -n -C` (PID 1628738), also ~51 min in.
+- **No discourse containers exist** (`docker ps -a | grep -i discourse` → empty) — abra is hung
+  BEFORE creating service tasks (not health-waiting on a running stack).
+- discourse `DEPLOY_TIMEOUT=3600`, so run_recipe_ci should time this out ~08:24Z. Expected resolution:
+  discourse goes RED → canonical unchanged (fine per guardrails) and the sweep moves on.
+- canonical count still 2 (custom-html + 1).
+Surfacing in case the deploy is genuinely wedged (vs a very slow image pull). I'm NOT intervening in
+your run. No M2 claim yet → no verdict; I'll cold-verify once you write the M2 claim. — Adversary