review(2): F2-10 CLOSED via DEFERRED.md route — accept new operator-confirmed framing; F2-9 effectively migrates too (Phase-4 review)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

machine-docs/BACKLOG-2.md

@@ -122,8 +122,28 @@ Phase plan: `/srv/cc-ci/cc-ci-plan/plan-phase2-recipe-tests.md`
       recipe enrollment that requires Socket.IO client primitives in the harness." Original entry
       below for the audit trail.
 
-- [ ] **F2-10 [adversary] — uptime-kuma (Q4.8) bypasses plan §4.3 create-and-read-back floor**
-      (same class as F2-4 n8n, F2-8 bluesky-pds). Plan §4.3: "create a monitor + list it."
+- [x] **F2-10 [adversary] — CLOSED @2026-05-28** via DEFERRED.md route (Builder commit
+      `8bafbd4` references the deferral entry in `machine-docs/DEFERRED.md` §"2026-05-28 —
+      uptime-kuma create-monitor + list-it (§4.3 prescribed)"). Re-entry trigger: the
+      `--extra-tests` opt-in flag OR another recipe needing Socket.IO client primitives in
+      the harness — whichever comes first. Per the orchestrator's open-ended DEFERRED.md
+      convention (items can sit indefinitely; closure is operator-driven; Phase-4 surfaces
+      the list), this is the legitimate path for a §7.1 floor-gap that the Builder chooses
+      not to implement now. The shipped tests (parity health + Socket.IO handshake + SPA
+      branding) cover Socket.IO + bundle surface non-vacuously; the gap is the create-monitor
+      lifecycle.
+
+      **Observation, NOT a new finding:** the Builder has consistently applied this pattern
+      now — ghost create-a-post (Q4.4), uptime-kuma create-monitor (Q4.8), matrix-synapse 4
+      ops/operational tests (Q4.1), lasuite-docs OIDC parity ports + create-a-doc (Q3.1),
+      cryptpad create-pad-deeper (Q3.4) are all filed in DEFERRED.md with re-entry triggers.
+      F2-9 (cryptpad CONDITIONAL sign-off) effectively migrates to the DEFERRED.md route too
+      — Q5 cold-sample condition becomes "review DEFERRED.md's cryptpad entry" rather than
+      an independent BACKLOG item. Acceptable per the new framing; Phase-4 reviews all.
+
+      **Original F2-10 FAIL detail retained for audit (now CLOSED via DEFERRED.md above):**
+      uptime-kuma (Q4.8) bypasses plan §4.3 create-and-read-back floor (same class as F2-4
+      n8n, F2-8 bluesky-pds). Plan §4.3: "create a monitor + list it."
       Builder's PARITY.md defers it:
       > "Requires completing the initial setup flow via Socket.IO emit then logging in to
       > obtain a session token; substantial work that adds Socket.IO client to the harness."