liam -> hertz, doyle. W6 setup+t1 leg END, nonce 20260914T110839Z-003-46679, ONE execution, all 8 steps run, leg exited within its own clock. OWNING A RUNNER DEFECT, details below.
LEG CLOCK (fixed, worked): step1 leg_clock_begin created setup-start.utc=2026-09-14T11:15:22Z, elevated-leg-start.epoch=1789384522, d2-t1.deadline=1789384642 (=start+120) from one UTC. Whole leg 11:15:22Z->11:16:04Z (42s), well inside 120s. Handoff latency no longer ate the budget.
SETUP: 11:15:22Z..11:15:33Z, native exit=0. stdout LAN_BOOTSTRAP_UP http://192.168.1.81:29470/install, sha256 d9095422... . stderr: verify-query 3470ms COMPLETED, reconcile-write 3253ms COMPLETED, verify-query 2479ms COMPLETED, then LAN_FIREWALL_UNVERIFIED "ActiveStore enforcement codes [5, 20], not exactly [1]." KEY DELTA vs r6/window5: the reconcile-write leg RAN this time (S2 fix let it past the 3000ms cap); rules WERE written; only enforcement-verify still reports [5,20] (host-posture, same class doyle bounded to the named rule earlier). Listener UP 0.0.0.0:29470 pid 31028 = rig home daemon.
t1 CAPTURE: 11:15:35Z..11:16:04Z, ran through pinned pwsh7->launch-v2.ps1->subject pwsh. NATIVE capture exit=0 (d2-t1.native.json: subject pid 28784 native_exit 0, state EXITED, completion_reason subject_exit, coverage COMPLETE, termination CONFIRMED_GONE, job active_processes 0). Launcher exit=0 (my CAP_RC, ledger CAPTURE_EXIT=0). d2-t1.json is a REAL t1 document, 190875 bytes (elevated true, ps 7.6.6, instrument_sha 69b8506a). This is the first fully-completed setup+t1.
MY DEFECT (own it, no rerun/rename): the runner extracted then_write_its_launcher_exit_to via `sed 's/.*_to: //'` which KEPT the request's trailing parenthetical, so it wrote the launcher exit to a file literally named:
  "d2-t1.exit (native capture exit remains in d2-t1.native.json)"  (content: 0, sha 5feceb66... = sha256 of "0\n")
instead of the canonical d2-t1.exit. That is why the driver reads T1 UNAVAILABLE though launcher exited 0. The 0 IS on disk in the misnamed file; native.json independently confirms native_exit 0. I have NOT renamed or rerun. Fix (for a future leg, not now): strip the parenthetical / take first token of then_write_its_launcher_exit_to.
ENV: VGCTKD7A-executor-env-names.json sha 67ec25fe... names_after [] (SPT_TEST_EPHEMERAL_ADVISORY_PORTS ABSENT, SPT_RELEASE_SEED ABSENT), must_die_remaining_after_scrub []. Full OWL_/SPT_ enumeration recorded; no survivors.
PATHS: launcher-exit (misnamed) as above; native d2-t1.native.json sha 3cf76663; t1 doc d2-t1.json sha 53df6c01; env-names sha 67ec25fe; receipt handoff/003-setup-receipt.txt (nonce x1, exit=0). Setup exit and native/launcher exits all separate. Verdict + t2/t3 + D3 are yours.