review(5): close A5-1/A5-2 after cold retest

machine-docs/REVIEW-5.md

@@ -116,3 +116,36 @@ positive window before bridge deployment; clears once bridge posts real `cc-ci/t
 ## Adversary findings
 
 (Tracked in BACKLOG-5.md)
+
+---
+
+## Cold-verify follow-up — 2026-05-31T19:41:12Z
+
+No `Gate: <Mn> CLAIMED` in `STATUS-5.md`, so I used the idle slot for a fresh V2 poll-only probe.
+I did **not** read `JOURNAL-5.md` before this verdict update.
+
+### A5-1 re-test: CLOSED
+- Fresh evidence from the live system: my accidental `!testme` comment `#13818` on
+  `recipe-maintainers/custom-html-tiny` PR #2 immediately produced a new `cc-ci/testme` commit status
+  pointing at Drone build `#35`.
+- That only happens if `custom-html-tiny` is enrolled in the bridge poll path, so A5-1 is no longer
+  reproducible.
+
+### A5-2 re-test: CLOSED
+- `GET /repos/recipe-maintainers/custom-html-tiny/commits/156a49ac/status` now includes context
+  `cc-ci/testme` with build URL `https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/35`.
+- Correct poll-only invocation from a cold shell:
+  `POST=0 MAX_WAIT=15 INTERVAL=5 /srv/cc-ci/.claude/skills/recipe-upgrade/testme-on-pr.sh custom-html-tiny 2`
+  returned:
+  `VERDICT=GREEN`
+  `BUILD=https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/35`
+- PR comment count stayed unchanged across that call (`4 -> 4`), confirming `POST=0` polls without
+  re-triggering.
+
+### Heads-up to Builder
+- `STATUS-5.md` currently records the poll-only command as
+  ``testme-on-pr.sh custom-html-tiny 2 POST=0``.
+- That syntax is wrong: `POST=0` is an **environment variable**, not a positional argument. Running
+  it that way posted a fresh `!testme` comment (`#13818`) and kicked off build `#35`.
+- This is a STATUS/HOW issue, not a new code defect. I notified the Builder via `BUILDER-INBOX.md` so
+  the verification instructions can be corrected before the next claim.