Counter ASIC 2.0: C32's premise withdrawn, the rule reworded; status 23:10

docs/plans/counter-asic-2-rollout.md

@@ -40,7 +40,7 @@ The same nine-field object goes verbatim into the override files of Mac node 1,
 ### 4a. Two rules for the publish and every PC job (C32)
 
 - The 0.3.11 update-now goes to PC 2 only after the prover-floor agent's server build (floor-build-3, under /opt/igneum-floor in WSL2, published 22:27 UTC, 25 to 90 minutes) has closed: an app restart ends the running job. The update-now takes a machine list (as 0.3.10's did): the Mac, the laptop and PC 1 first, PC 2 last.
-- Re-fetch after every app update: an app update clears the jobs folder (the 0.3.10 install at 21:49 UTC took PC 1's AMD kit with it), so every fetch-then-run pair re-publishes its fetch after an update, and every run playbook opens with a presence check of its kit that fails with "kit missing: republish the fetch after the app update".
+- A run job tests its kit before use, and jobs are sequenced around an update: an app restart (an update, a relaunch) aborts every running job, so the update-now follows the jobs that must not die; the kit presence check at the top of every run playbook (tools/ci/kit-path-check.sh) is hygiene ("a kit may be missing; test before use"), not a class fix. The earlier premise, "an update clears the jobs folder" (the bench-log line 39f02ff on the AMD agent's branch), is WITHDRAWN: that reading came from relay probe #230 on PC 2, where the kit had never been fetched, and the code clears no jobs folder on an update (the remove_dir_all calls in app/igneum-app/src/jobs.rs are unit tests; ota.rs and ota-apply.ps1 name no jobs path; the installer deletes only {app} on uninstall).
 
 - No PC job raises an elevation prompt on either PC for the rest of the night (C35): both unexplained app quits tonight came 20 to 41 s after an administrator prompt beside the running installed app (PC 2 20:00:49 to 20:01:09Z, PC 1 22:30:25 to 22:31:06Z), the engine has no self-relaunch after a quit, and nobody is at a keyboard; the two-minute test of that class (raise one prompt from a job while the app mines, cancel it, read the quit line, which ember-tune b671c8b stamps with its source) runs in the morning with Josh present, or tonight only after the relay relaunch path is proven and the rollout is done. The sweeps and Ember's run stay held; the floor, aggregation-cost and M16 jobs raise no prompt.
 

docs/plans/counter-asic-2-status.md

@@ -641,3 +641,5 @@ The shipper found it from the intake: PC 2 has two new engine runs (win-1ccfe586
 23:09. The ledger-pc2 M16 kit is on the dl folder (igneum-inline-bench-kit.zip, 202,138 bytes, sha256 80ce0290a456b5c221ffde02bb35f74a25e48394e4cbccf53335a83e8aeb08ce; the Mac's three bit-exact checks PASS on the real kernel texts): one run job, two passes (block-warps 1 and 8) over the honest 1 GiB kernel and the inline kernel at 256, 64 and 32 MiB, 15 s a setting, the miners paused and the prover off by the script and restored in its finally; its go after PC 2's 0.3.11 update. The morning's hands list is in the rollout plan 7c (start PC 1's app first, then the 16:00Z check).
 
 23:09. PC 2 order, final for the night (one job at a time, each on the previous release): the shipper's combined suites-and-exes job; the aggregation-cost restore (20 s, queued behind it: the prover back on); the prover-floor build 4 (5 min) and sweep 2 (4 min); the aggregation-cost re-run (20 min); "PC 2 clear" and the 0.3.11 update-now; the ledger-pc2 M16 job (4 min); the repro benchmark (14 min: the 5090 CUDA and OpenCL, the gfx1036, the proving step, the 2^21 against 2^24 job-size bench). PC 1: nothing (its app down; the morning's first item).
+
+23:10. C32's premise withdrawn (the reviewer, from the code and the relay finding): an app update does not clear the jobs folder (the "AMD kit gone" read was PC 2, where it was never fetched); what stands is that an app restart aborts every running job, so the update-now is sequenced after the jobs that must not die, and the kit presence check is hygiene; rollout plan 4a reworded; the bench-log line 39f02ff on the stopped AMD agent's branch is corrected by this note (its owner is stopped).