START. The authorized PREP-only attempt is LAUNCHED and running.

LAUNCH     2026-09-13T07:04:53.535Z, unelevated (driver's own S0a: ELEVATION self=False), exact packet command, no arguments.
DRIVER     2fd7d689... verified immediately before launch.
RUN ID     20260913T070453Z
EVIDENCE   .../bundle-r5/fp-run/20260913T070453Z
PREP DEADLINE 600s from process start = 2026-09-13T07:14:53Z. Not extended, and I will not extend it while awaiting you.
EXECUTOR CONDITION satisfied before launch: liam re-measured at 07:04:43Z - session 1212783f, host pid 52832 alive per tasklist same instant, admin probe yes. He has confirmed he will answer PREPARED only, run nothing, and will NOT answer the GO request.
HOME     fp-home-d2-a2 verified ABSENT at 07:04:45Z before launch; fp-home-d2 left PRESERVED, 8 entries, untouched.

GATE OUTCOMES SO FAR, all from the driver's own output:
  ELEVATION self=False (expected False).
  INSTRUMENTS hashed into INSTRUMENTS.sha256, 6 files.
  CI_AXIS ok at 'preflight': queued/in_progress/requested/waiting/pending each queried BY NAME, all zero on spt-bs-core - not merely zero among the recent.
  BOX_GATE ok at 'preflight': cargo_build=0 runner_descended=0 shim_unresolved=0; analyzer=6 recorded and not gated.
  SUBJECT sha=85f84d73 clean, blob=848a23fe.
  GUARD_BASELINE taken for port 5470 (read-only).
  EXECUTABLE sha256=72d30901... PINNED, equal to the r10 setup receipt's subject; no build ran.
  CI_AXIS ok at 'pre-diagnostic' and BOX_GATE ok at 'pre-diagnostic' - both axes refreshed.
  Currently at: the pre-setup absence census and then the PREPARED handoff. No gate has failed or read unreadable; nothing has been created, elevated or dispatched.

I will send the GO request nonce the moment the driver writes that request, together with the PREPARED receipt outcome. If any gate fails or reads unreadable the attempt ENDS - no retry, no bypass.

ACCOUNTING CORRECTION, without rerunning anything, from the saved .out (a read): my 49+10+10 was wrong arithmetic AND a wrong framing. Counted per section from the file: M=9 N=9 O=8 P=3 Q=6 R=5 S=5 T=9 = 54 retained arms, U=10 V=10 = 20 newly exercised, total 74. And you are right that "re-executed because they share the file" IS a rerun: the whole file ran, all 74 arms executed in that invocation. The honest scope is: one full re-run of go-and-silent-controls.sh, of which 20 arms were new or rewritten and 54 were unchanged. cleanup-controls 50/50 and declined-setup 16/16 were NOT run in that step.