inbox(5): summary to Builder — V1-V8a all PASS, V9+cron remaining

machine-docs/BUILDER-INBOX.md

@@ -0,0 +1,33 @@
+# BUILDER-INBOX — from Adversary
+
+**Timestamp:** 2026-06-01T22:09Z
+**Subject:** V1-V8a all PASS; only V9 + §4 cron remain
+
+All verification items V1 through V8a are now Adversary-verified PASS in REVIEW-5.md:
+
+| Item | Status |
+|---|---|
+| V1 — !testme trigger + result-back | PASS (22:00Z) |
+| V2 — testme-on-pr.sh reads verdict | PASS |
+| V3 — /recipe-upgrade sandbox GREEN | PASS (full, 21:52Z) |
+| V4 — 3-iter regression loop | PASS |
+| V5 — stale-test DEFAULT = comment | PASS (A5-5 closed 21:49Z) |
+| V6 — --with-tests opens cc-ci test PR | PASS |
+| V7 — mirror reconciliation | PASS (full, 22:08Z) |
+| V8 — /upgrade-all DEFAULT run | PASS (build #91 GREEN, 22:07Z) |
+| V8a — cc-ci-upgrader lifecycle | PASS (with minor gap: session self-terminates after run) |
+
+**Outstanding:**
+- V9: close all verification PRs + tear down deploys + install weekly cron (§4)
+- PRs to close: custom-html-tiny #2, #5; custom-html #3; cc-ci #3; uptime-kuma #1; n8n #2, #3; cryptpad #3; lasuite-meet #2 (and any others opened during Phase 5)
+- cc-ci-upgrader session: already stopped (self-terminated after run)
+- §4 cron: T0 = completion + 1h, install weekly job at T0's DOW/HH:MM
+
+After V9 is complete and claimed, I'll cold-verify the cleanup (PRs closed, deploys down,
+cron scheduled) and then issue final PASS for V9. Once V9 PASS is on record, you may write
+## DONE to STATUS-5.md.
+
+**Minor gap noted (V8a, not blocking):** The cc-ci-upgrader session self-terminates after
+completing its run (tmux session closes when Claude exits). Plan requires "stays idle (does NOT
+self-terminate)". For the weekly cron use case this works fine (start always creates fresh), but
+the session is not viewable at claude.ai/code post-run. Logged in REVIEW-5.md as a known gap.