Counter ASIC 2.0 status 07:03: PC 1 back, the 22:31Z quit source named (C35 closed), the Ember re-run on the project lead's word

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

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

@@ -114,7 +114,7 @@ CORRECTION at 23:08 UTC, from the shipper's own finding: the relay machine named
 
 1. Start PC 1's app (its engine quit at 22:31:06Z on 5 October and has no self-relaunch; the box has no relay agent): relaunch Igneum Miner, let it take 0.3.11 from the manifest, and confirm its STATUS line and the digest 0139ab9d...; then it reconnects. Expect PC 1 to show "0 peers" until it updates: N4 = N5 = 154,800 (epoch 43) lands at about 03:30 UTC on 6 October (DAA 139,1xx at 23:1x UTC at 1.002 DAA/s), so class v3 and proving v1 switch on while everyone sleeps; the Mac, the laptop and PC 2 cross it on 0.3.11, and a 0.3.10 node without the class v3 field in its digest is refused at its next handshake by every nine-field peer: the digest rule working as written, not a fault. Until the relaunch the devnet runs short PC 1's 141 MH/s.
 2. Then the 16:00Z check of C1 (7a): every prover on 0.3.11, else H = 210,000 is republished at tip + 86,400.
-3. The two open faults for a person at the machine: the source of PC 1's 22:31 quit and PC 2's 20:01 quit (the administrator-prompt class; the two-minute test of 4a), and the AMD clock and power sweep rows on the 9070 XT (owed; the card is present).
+3. The two open faults for a person at the machine: PC 1's 22:31 quit is CLOSED (07:03Z: the Ember playbook's second engine, version 0.3.9, ran the urgent updater and its per-user installer sent /api/quit to the installed app; fix e600e63 on ember-tune, a second engine never runs the updater); PC 2's 20:01 quit stays open (the administrator-prompt class; the two-minute test of 4a), and the AMD clock and power sweep rows on the 9070 XT (owed; the card is present).
 4. Not on the list any more: the eGPU reseat (the drops were readings of PC 2).
 
 ### 7d. The step-1 stall and what it moves (consequences C42, closed 23:39:49Z)

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

@@ -794,3 +794,7 @@ The consequences reviewer at 04:16Z: node 1's igneum_getProvingStatus.v1 reads a
 ## 05:59 VERDICT PASS; H re-cut to about 19:12 to 19:20Z
 
 The watcher's verdict at 05:21:48Z: PASS, class v3 after the crossing, 58.7 blocks per minute in the ten minutes before against 59.2 in the ninety after, no gap of ten minutes, DAA 160,148 and 114,611 blocks since the observer's pruning; epoch 44 (DAA 158,400) crossed clean. The reviewer's measured rate from the crossing to 05:57:38Z (DAA 162,295): 0.99 DAA/s, so H = 210,000 lands about 19:12 to 19:20Z, later than the 18:45 to 18:56 quoted overnight (the stalls pulled the earlier average forward); the 16:00Z C1 check keeps about 3.2 hours of margin and nothing in the order changes. The watcher exits on its own; the status file ends here.
+
+## 07:03 PC 1 is back; the source of its 22:31Z quit is named (C35 closed); the Ember re-run waits on the project lead
+
+PC 1's app came back at about 06:59Z (job pc1-morning-intake-1 ran 07:01:45Z); it takes 0.3.11 and the nine fields from the manifest at that start. The C35 source, from the second engine's own log (collect ember-c35-collect-1, the Ember agent, 06:59Z): the second engine the Ember playbook started reported version 0.3.9 (the branch's Cargo version), under the manifest's min_supported_version, so its updater treated 0.3.10 as urgent (the urgent rule beats the auto_update = false the playbook wrote into the copied settings), downloaded it at 22:31:02Z and ran the per-user installer at 22:31:05Z, whose PrepareToInstall sent POST /api/quit to the INSTALLED app (quit logged 22:31:06Z); the second engine then hung on the inherited pipe until the relay lane ended it. So PC 1's quit was the playbook's second engine through the installer, not an administrator prompt and not the host. Fix e600e63 on ember-tune: a second engine never runs the updater (Engine.no_ota from IGNEUM_APP_NO_OTA=1, implied by --sweep; the OTA tick skipped and Check now refused; logged at start), both playbooks set it, tools/ci/second-engine-check.sh demands it beside the file-not-pipe and tree-kill lines; 93 app tests pass. PC 2's 20:01Z quit is a different case (it came back as 0.3.9, so not an installer) and keeps the morning's prompt test. The Ember re-run (5090 baseline, the 9070 XT power ladder, no prompt) is built and held: PC 1 is the project lead's desk and he is at the machine, so it runs on his word through main, not on the night scheduler's; it needs the build of e600e63 and the two fetches republished after PC 1's update.