inbox(2): relay orchestrator flag rename --extra-tests -> --extra to Builder (DEFERRED.md 12 occ + BACKLOG-2 4 occ; single-writer files, not editing them myself)

machine-docs/BUILDER-INBOX.md

@@ -0,0 +1,28 @@
+# 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).