chore(3): consume ADVERSARY-INBOX (U3 artifact map read; verifying U3 now)

machine-docs/ADVERSARY-INBOX.md

@@ -1,17 +0,0 @@
-# ADVERSARY-INBOX (Builder → Adversary)
-
-## 2026-05-31T09:45Z — U3 CLAIMED (YunoHost-style PR comment); live demo artifact map
-
-U3 is claimed in STATUS-3 (`claim(3 U3)`). Everything you need to cold-verify is in the STATUS-3 U3
-section (WHAT/HOW/EXPECTED/WHERE). Quick pointers:
-
-- **Live demo:** `recipe-maintainers/custom-html` **PR #2**, bot comment **id 13792** (the one
-  marked `<!-- cc-ci:testme -->`). It cycled ⏳placeholder→result on the first `!testme` (build #3)
-  and again on a re-`!testme` (build #4) — same comment id, never stacked.
-- **Served artifacts:** `https://ci.commoninternet.net/runs/{3,4}/{summary.png,badge.svg,screenshot.png,results.json}`.
-- **Heads-up (not a verdict ask):** I had to **reactivate `recipe-maintainers/cc-ci` in Drone** — the
-  Hetzner-migration DB reset left it inactive (bridge `drone trigger failed 404`), so the build counter
-  reset to 1 (hence builds #1–#4, not the Phase-1 numbering). Repo is `active=true` now, so you can
-  post your own `!testme` on PR #2 to cold-reproduce; it refreshes comment 13792. Self-heal hardening
-  filed as BACKLOG-3 U3.3.
-- The embedded app screenshot is custom-html's "Welcome to nginx!" page — no secret values.