Counter ASIC 2.0 status 00:18: 0.3.11 shipped, master fa8193b and 7d779c7, the sweep closed

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

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

@@ -685,3 +685,7 @@ Step 2a reading (the shipper, 23:55:42Z): tip DAA 140,706, floor 14,094 against
 ## 00:09 publish 2 is on the nodes: the hand nodes, the seed and PC 2 at 0139ab9d; the nine-field manifest live
 
 The shipper: the observer, node 1 and the seed restarted with the nine-field override at 23:56:59Z, 23:57:12Z and 23:57:30Z, each at digest 0139ab9d; the live manifest carries the nine-field object since 23:57:49Z. PC 2: the switch job update-now-0311-switch-1ccfe586 ran 00:01:10Z, its node restarted with the nine-field file 00:01:42Z, STATUS at 00:06:31Z: 106.48 MH/s, node 141,351 blocks, 1 peer, synced, 830 accepted this run, 0 faults. The expected gap of the two-publish order: PC 2 (still on 4d8f8bb6) refused the seed between 23:57:42Z and 23:58:12Z, closed by the switch. One finding for the next cut (the miner): the Mac's miner lost node 1 at its 23:57:12Z restart and never reconnected (5,300 "Not connected to server" submit errors, templates frozen at 2,350, hash burned at 26 MH/s); the shipper published restart-miners-0311-d937c69d at 00:08:01Z for the Mac only; the gRPC subscription does not resubscribe after the node restarts. Still open on the ship: the laptop's return (silent since 23:28:28Z), the digest sweep, the merge to master and the push, the shipper's report. PC 2 now: floor-build-5 (the go at 00:09; patch v3 3604c25: the key's buffer stays preprocessed-sized at Setup and main_tracegen grows it on first use; a short bound aborts loudly instead of leaving the client on the socket), then floor-sweep-3 (9 points, 4 to 6 min), then the aggregation-cost re-run, M16, the repro job, the ledger-fixes-0311 suites (fork tip fbb0082a, published with the ledger-rebase worktree's tools/build-job.mjs; the Mac run of the same suites is in flight under the build lock).
+
+## 00:18 0.3.11 SHIPPED: master 30cd292 then 630da6b pushed; every live node at 0139ab9d
+
+The shipper's close: release-0.3.11 (7ab72f3) merged onto master 063baf6 without conflict as 30cd292, then 630da6b (the plan's merge section), pushed 00:13:04Z and 00:15Z; CI on master in progress (37392831312 ci, 37392831184 windows-ci). The live site deployed from 30cd292 at about 00:13:45Z with every corrected sentence (24 GB proves, the schedule as the gate 1 proposal, no bounty words, no 12 GB clause). The digest sweep closed for every live node: the observer 23:56:59Z, node 1 23:57:12Z, the seed 23:57:30Z, PC 2 00:01:42Z, the Mac through node 1; all 0139ab9dc2992d449ec787d8f021974933631eb55740ab4b6ce9d5c226e72888; tip DAA 141,715 at 00:12:36Z; PC 2 105 to 116 MH/s; the Mac 25.7 MH/s with 55 accepted since its miner restart at 00:08:33Z. Pending their relaunch by hand: PC 1 (down since 22:31:06Z, on 0.3.10), the laptop 37ba0461 (silent since 23:28:28Z, off the console), Sam's Mac (0.3.9, quit 20:47Z); each takes 0.3.11 and the nine-field object through the manifest, with one possible old-node death inside the update (C39's shape) to read in the morning intake. No release tag was cut (0.3.9 and 0.3.10 have none; a convention needs the project lead's word). The shipper's plan: docs/plans/release-0.3.11.md sections 8 (step 2 times), 9 (the sweep), 11 (open items: the miner's dead gRPC channel, the HiveOS override, the prepared pack near the hour, PC 2's first-shard socket error at 23:52:14Z, the relay naming, the job queue, the edge index, C1 at 16:00Z), 12 (the merge). The activation: program_class_v3 and proving v1 at N4 = N5 = 154,800 (epoch 43), about 03:40Z on 6 October at the new side's rate; H = 210,000 about 18:56Z. The shipper is done with PC 2 for the night. Still running on PC 2 under my schedule: floor-sweep-3 (the 12 GB tier under patch v3), then the aggregation-cost re-run, M16, the repro job, the ledger-fixes-0311 suites.