RESEND of grant 73SY26E5 + your own last status (FR54KSHI), doyle 10:34Z. The old #304 W1 lane in your restored context is STALE — ignore it.
SETTLED (do not redo): L0/L1 group L (controls-out/20260913T100902Z-L) ACCEPTED — native direct-child identity established, msys anchors, L7 caught pid 53072 recycled at 24 s. r4 fp-driver-d2-r4.sh 5fb75766 READ-ACCEPTED as the successor design, UNEXERCISED. Historical gap permanent (64YIGUUN).
GRANT (one group, one return, no proposal round): group M, exercising the REAL fp-bin/launch_bounded.ps1 (c0050c3e) that r4 calls, on SHORT SELF-EXITING THROWAWAYS ONLY:
- M0 negative control: measure_termination over a launch whose subject certainly exited, ASSERT CONFIRMED_GONE — must FAIL exit 1 (r4 can only say ATTRIBUTION_INCOMPLETE + SUBJECT_STATE=GONE); positively exercises SUBJECT_STATE=GONE.
- M2=L2 (kind=subject names the subject exe at a real call site, native exit verbatim through the launch handle), M4=L4 (the :1239 shape: SPT_D2_HOME exported around the call, intended exe as direct child, measured by anchor), M6=L6 (ledger: coverage<COMPLETE cannot yield residual_state=CLEAR). No termination in these.
- M3 job containment + M5 breakaway: your job-containment-probe.ps1 + job-parent.ps1 — job with KILL_ON_JOB_CLOSE, IsProcessInJob READ for parent and child, close handle, re-query BOTH by pid+creation anchor; M5 = child spawned CREATE_BREAKAWAY_FROM_JOB so the proposal states whether a daemon-style detached spawn escapes, measured. Only processes the arm creates are ever touched.
- M8 read-only disposition of everything M registered, by anchor.
YOUR OWN STATE at signoff: the two instruments written, NOT parse-checked; group-m.sh NOT written; nothing has run.
NEXT ACTION: parse-check both instruments, write group-m.sh, run the one group, return the out dir + ONE doc = receipt + containment proposal carrying the M3/M5 measurements. I rule the termination controls from that in one pass.
WINDOW: no restriction. Todlando is building #300 in his own claimed pool (cargo, jobs=2) and a post-merge CI run may be on the runner — identity arms are not latency arms; run now. Still HELD: any termination of a process you did not create, field runs, signing, provisioning, apply.