inbox(2): consume BUILDER-INBOX (flag rename relay) + finish --extra rename in BACKLOG-2 Adversary-section lines 241/248/292 (Adversary explicitly delegated)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-05-29 10:40:49 +01:00
parent a22ba9c9cc
commit e0a80124bc
2 changed files with 3 additions and 31 deletions

View File

@ -238,14 +238,14 @@ Phase plan: `/srv/cc-ci/cc-ci-plan/plan-phase2-recipe-tests.md`
- [x] **F2-10 [adversary] — CLOSED @2026-05-28 via Builder route 2** (file in DEFERRED.md per the - [x] **F2-10 [adversary] — CLOSED @2026-05-28 via Builder route 2** (file in DEFERRED.md per the
new orchestrator-confirmed convention). The uptime-kuma create-a-monitor entry is in new orchestrator-confirmed convention). The uptime-kuma create-a-monitor entry is in
`machine-docs/DEFERRED.md` (commit `650ab47` migrated + `44e88f3` relocated under Open `machine-docs/DEFERRED.md` (commit `650ab47` migrated + `44e88f3` relocated under Open
deferrals) with re-entry trigger "the `--extra-tests` opt-in flag (IDEAS.md) OR another deferrals) with re-entry trigger "the `--extra` opt-in flag (IDEAS.md) OR another
recipe enrollment that requires Socket.IO client primitives in the harness." Original entry recipe enrollment that requires Socket.IO client primitives in the harness." Original entry
below for the audit trail. below for the audit trail.
- [x] **F2-10 [adversary] — CLOSED @2026-05-28** via DEFERRED.md route (Builder commit - [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 — `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 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 `--extra` 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 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 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 the list), this is the legitimate path for a §7.1 floor-gap that the Builder chooses
@ -289,7 +289,7 @@ Phase plan: `/srv/cc-ci/cc-ci-plan/plan-phase2-recipe-tests.md`
recipe. recipe.
2. **File in DEFERRED.md per the new operator-confirmed convention:** open-ended 2. **File in DEFERRED.md per the new operator-confirmed convention:** open-ended
deferral with the operator-clear re-entry trigger ("when Socket.IO client wrapper deferral with the operator-clear re-entry trigger ("when Socket.IO client wrapper
lands in harness, OR when `--extra-tests` flag IDEA materializes"). The orchestrator's lands in harness, OR when `--extra` flag IDEA materializes"). The orchestrator's
DEFERRED.md framing explicitly allows indefinite deferrals — but they must be in DEFERRED.md framing explicitly allows indefinite deferrals — but they must be in
DEFERRED.md, not buried in PARITY.md. Builder's PARITY.md "Deferred (Q4 follow-up)" DEFERRED.md, not buried in PARITY.md. Builder's PARITY.md "Deferred (Q4 follow-up)"
section duplicates what DEFERRED.md is now meant to centralize. section duplicates what DEFERRED.md is now meant to centralize.

View File

@ -1,28 +0,0 @@
# BUILDER-INBOX (from Adversary)
## @2026-05-29 — Orchestrator flag rename `--extra-tests` → `--extra` (routing to you, single writer)
Operator/orchestrator note (2026-05-29): the opt-in heavy-tests flag is renamed
**`--extra-tests``--extra`** (trigger surface stays `!testme --extra` / build param; name the flag
`--extra` when implemented). Orchestrator says it already updated IDEAS.md + plan-sso-dep-testing.md.
I'm routing the machine-docs edits to **you** rather than editing them myself because they live in your
single-writer files (DEFERRED.md is the Builder-owned deferral registry — consistent with my standing
REVIEW position that its edits are yours), and to avoid a clobber if you got the same broadcast.
**Authoritative scope (grep in my clone, current HEAD):**
- `machine-docs/DEFERRED.md`**12 occurrences** of `--extra-tests`, lines
**49, 51, 59, 60, 69, 71, 121, 122, 124, 136, 138, 140** (re-entry triggers + linked-IDEA refs on
the matrix-synapse / uptime-kuma / ghost / etc. deferred entries).
- `machine-docs/BACKLOG-2.md`**4 occurrences**, lines **136, 241, 248, 292**.
- My own REVIEW-2/2w/2pc — 0 occurrences.
- Code (`runner/`, `bridge/`) — flag not yet implemented; name it `--extra` when you build it.
A global rename is safe (every hit is the flag name, no `--extra-tests` substring collisions):
```
sed -i 's/--extra-tests/--extra/g' machine-docs/DEFERRED.md machine-docs/BACKLOG-2.md
```
(My earlier draft of this note said "4 occ / BACKLOG none" — that was from a glitched read this tick;
these grep'd counts (12 / 4) are correct.)
No verdict / not a gate — pure coordination relay. Delete this file when consumed (the usual signal).