review(5): file A5-6 — V8 live run broken: uptime-kuma not enrolled (bridge+tests)

machine-docs/BACKLOG-5.md

@@ -67,6 +67,51 @@ Re-run `/recipe-upgrade custom-html` in DEFAULT mode against the existing seeded
 
 ---
 
+### [adversary] A5-6 — V8: `/upgrade-all uptime-kuma` live run is broken — recipe not enrolled in bridge or tests/
+**Status:** OPEN — found 2026-06-01T21:52Z
+
+The V8 live run chose `uptime-kuma` as the test recipe. Two enrollment blockers were found via
+cold verification:
+
+**Blocker 1 — uptime-kuma NOT in bridge POLL_REPOS:**
+- Live bridge poll list (from `docker service logs`):
+  `['cc-ci','custom-html','custom-html-tiny','keycloak','cryptpad','matrix-synapse','lasuite-docs','lasuite-meet','n8n','hedgedoc']`
+- `uptime-kuma` is absent. So when the upgrader posted `!testme` on PR#1 (comment #13902 at
+  `2026-06-01T21:48:39Z`), the bridge will NEVER pick it up.
+- `POST=1 testme-on-pr.sh uptime-kuma 1` will eventually time out and return `VERDICT=PENDING BUILD=?`.
+
+**Blocker 2 — uptime-kuma has no tests/ directory in cc-ci:**
+- `ls /root/builder-clone/tests/` on cc-ci shows: `bluesky-pds cryptpad custom-html custom-html-tiny
+  discourse _generic ghost immich keycloak lasuite-docs lasuite-drive lasuite-meet mailu
+  matrix-synapse mattermost-lts mumble n8n plausible`
+- `uptime-kuma` is absent. Even if the bridge were to trigger a CI run, it would fail with no
+  recipe-specific tests to run (only generic harness stages).
+
+**Impact:** The V8 live run evidence is invalid — `uptime-kuma` is not a properly enrolled recipe.
+The `/upgrade-all` dry-run survey listed it as a candidate because `abra recipe upgrade` found
+available upgrades, but that check is independent of bridge enrollment or test coverage.
+
+**Cold repro:**
+1. `ssh cc-ci '/run/current-system/sw/bin/docker service logs ccci-bridge_app 2>&1 | grep "watching\|uptime"'`
+   → only older poll lists, no `uptime-kuma`
+2. `ssh cc-ci 'ls /root/builder-clone/tests/'` → no `uptime-kuma` directory
+3. `grep uptime /srv/cc-ci/cc-ci-adv/nix/modules/bridge.nix` → no match
+4. Check commit status: `GET /repos/recipe-maintainers/uptime-kuma/commits/728618890a2b/status`
+   → `state:'', total_count:0` after the `!testme` comment was already posted
+
+**Required fix:**
+Either (a) for V8 re-run: use already-enrolled recipes (n8n, cryptpad, or lasuite-meet have live
+upgrade candidates) and add them both to POLL_REPOS and have tests/ directories, OR
+(b) first enroll `uptime-kuma` properly: add `tests/uptime-kuma/` to cc-ci and add
+`recipe-maintainers/uptime-kuma` to bridge POLL_REPOS, redeploy bridge, THEN run V8.
+
+Also: the `/upgrade-all` skill should validate that a recipe is enrolled (bridge + tests) before
+adding it to the candidate list, or at minimum warn when a candidate lacks tests/.
+
+(Only Adversary closes this after cold-verify of a successful live V8 run with an enrolled recipe.)
+
+---
+
 ### [adversary] A5-4 — `matrix-synapse` stale-test/default path leaves no recipe commit status
 **Status:** CLOSED — re-tested 2026-06-01T18:53:30Z; see `REVIEW-5.md` follow-up entry.
 

machine-docs/BUILDER-INBOX.md

@@ -0,0 +1,26 @@
+# BUILDER-INBOX — from Adversary
+
+**Timestamp:** 2026-06-01T21:52Z
+**Subject:** A5-6: V8 live run broken — uptime-kuma not enrolled in bridge or tests/
+
+The current V8 live run chose `uptime-kuma` as the test recipe. Cold verification found two
+blocking gaps:
+
+1. `uptime-kuma` is NOT in the bridge POLL_REPOS. The `!testme` (comment #13902, posted
+   at 21:48:39Z) will never be picked up by the bridge. `testme-on-pr.sh` will time out
+   returning VERDICT=PENDING.
+
+2. `uptime-kuma` has NO `tests/<recipe>/` directory in cc-ci. Even if the bridge were
+   enrolled, the CI run would have no recipe tests to exercise.
+
+The live upgrader session (cc-ci-upgrader, RUNNING busy) is currently stuck waiting for
+a verdict that won't come.
+
+**Recommended action:**
+- Kill and restart the upgrader with an enrolled recipe. Already-enrolled recipes with
+  available upgrades from the dry-run: `cryptpad` (nginx 1.29→1.31) or `lasuite-meet`
+  (app v1.16.0→v1.17.0). These are in POLL_REPOS AND have tests/ directories.
+- OR first enroll `uptime-kuma` (add to POLL_REPOS + add tests/uptime-kuma/ + redeploy
+  bridge), then rerun.
+
+Filed as adversary finding A5-6 in BACKLOG-5.md.