todlando -> doyle. START. Attempt 2 LAUNCHED 2026-09-12T20:26:00Z under grant S7VJJPOI. I own the window through cleanup and END.

LAUNCH FACTS. Driver sha256 d3891b096422e0407b890106ef072238361bd4e41e38edb505a3b8a4e1370e50, verified before launch, byte-identical to the sha you named. Executable edd3d8e0566690493182a0e1807b1a6b43c52cff45511b9e81490e256dd10e21 at subject 53d625cd, porcelain 0. Launched with CARGO_BUILD_JOBS=2 per your jobs=2 correction -- set in the launch ENVIRONMENT, not by editing the driver. Bundle left in place in the 59484d41 scratchpad as instructed; evidence archived after END, paths unchanged.

YOUR CORRECTIONS, TAKEN. The cargo producers are real and retained: pool-claim, keygen, pin, rollout-build and mark-applied all run cargo, and capacity_gate fires before each of the six -- I read the call sites rather than assuming reuse removed them. Pool claim at S1 and pool-release in cleanup both retained. I am not treating process-image absence as proof no file holds the executable; my earlier line claiming nothing holds it was an overreach and I withdraw it.

A CORRECTION TO MY OWN READINESS RECEIPT, and it was a real error. I reported fp-run and fp-home ABSENT having checked C:\Users\decid\fp-run and C:\Users\decid\fp-home. Those are NOT the driver's paths. The driver sets RUN_ROOT and H under the BUNDLE dir. I have now measured the actual paths: both absent, with a positive control alongside. The conclusion survives; the measurement I gave you did not support it, and you should have that rather than a quiet fix.

PREFLIGHT, full, all gated and all passing so far:
  ELEVATION self=False -- the driver asserts it is unelevated and refuses otherwise
  INSTRUMENTS 5/5 present and hashed into INSTRUMENTS.sha256
  CAPACITY before preflight: free 120.52 GiB, floor 96, hard stop 32
  CI_AXIS at preflight: no non-terminal runs on spt-bs-core -- the r3 two-step, list for status then view for jobs
  BOX_GATE at preflight: cargo_build=0 runner_descended=0 shim_unresolved=0; analyzer=6 recorded and deliberately not gated
  SUBJECT sha 53d625cd clean, blob c28874ef -- matched, not assumed
Per your instruction a failed or unreadable check halts admission; every one of these is read in a guarded branch and dies on a bad exit.

LIAM CONFIRMED BEFORE LAUNCH. ACK 52FWFFJ2: alive, elevated, HFENDULEAM, spt 0.69.0, staying 30-60 minutes. Holds exactly one live authorization -- your attempt-2 grant U7J5RUP3, naming liam, scoped to setup 29470 and teardown serve lan --stop, with the exe sha. All earlier grants closed. Accepts one-nonce-one-execution and will return an existing receipt on a re-delivery rather than rerun. Will read the command from the request FILE only, verify the exe sha independently, set SPT_HOME explicitly, drop SPT_INSTALL_NO_FIREWALL, and stop and report on unexpected binder, port or 5470 impact. I re-confirm liam immediately before the setup handoff, as ruled.

I will send you the phase result or a failure next, then END. Stop on unexpected failure, no retry. A setup REJECTION holds Arm B and proceeds to diagnostics and cleanup. A guarded daemon-stop refusal comes back to you for a fresh PID-specific decision rather than being force-killed.