release 0.3.22: the attack-pass record lines (F9 and F1 PASS on the full 10^5), PC 1 overnight

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

docs/plans/release-0.3.22.md

@@ -190,3 +190,5 @@ The 0.3.23 node's heights move Devnet 3's digest to ba75bf6f, and the one-box-at
 Main's word on route (A) or (B) did not come (asked 01:41, 01:50, 01:53, 01:56 BST), so nothing applied, nothing placed, no minute: build-1's /fleet/move.json still serves the 22:30 BST 2720d8d2 move (m2720-1); every Devnet 3 node is on the 0.3.23 pin 2720d8d2, digest ba75bf6f (dn3-j1 behind its dead proxy unverified since 22:30); the 0.3.24 Mac entry stands staged (DMG 1aa301cc, both token folders) and unpublished; the live manifest is 0.3.23 (Mac and HiveOS), the 0.3.23 and 0.3.24 Windows entries and the Discord card unpublished; the shipper's stand-down at 02:15 held by default (its line was not sent at 02:15, the shipper's miss; the state was unchanged). **Finding:** build-1's Devnet 3 seed (the --go process on 26631 with JSON RPC 27632, the node lane's DAA reader) is DOWN at 02:56 BST (no process with --appdir=/home/build/dn3seed; node1-dn3 26671 and the observer 26651 run on 2720d8d2; the node lane's 0.3.24 reader on 28690 runs); the last DAA read held is 25,169 at 00:52:38 BST, and at 1.0 DAA/s the chain passed 32,400 at about 02:53 BST, so the 39,600 floor is lost and the fourth re-cut is from a morning minute main names (before 12:50 BST, or the three heights move with the floor in the same commit); the fleet's nodes dial 26631, so the seed's restart on the pin is part of the morning's move. **The morning's shape on main's word:** the fleet lane and the build-server lane respawned (the puller and the gate script r0324/move/pair-gate-aa8c2978.py ready; 33 of 35 boxes reachable at 01:55); build-1's seed restarted on the pin; the pin re-cut from the minute; the pairs and the hive with the v5 kit e6c088bb; the one-minute move with the gate line first; the Mac entry at the minute; the Windows chain (the 0.3.24 host on PC 1, the installer and smoke on PC 2 in the simplest shape, 0.3.23's take 3 first) and the card after; the attack-pass record lines (F9's full 10^5, F1's census) as they land. The night's clean lines: the interim zeros at 01:55 (71,292 seeds, 0 exhausted, 0 panics, max attempt 30); the kit's fingerprint equal on four platforms; PC 1's lock-free queue (the 9070 XT G1 14 of 14 and its v5 fingerprint, the family rows, the 5080 grid through the cleared helper, the CA4 rows); dfbd1e10 fully gated with the fast-time PASS. Three rules from the night for release-rules: a digest-moving release's minute is named from the pairs on the boxes, never from a clock the pairs have not met (the three lost floors); a lane that owns a gate in the critical path answers within ten minutes or its work is reassigned by main, not waited on (the two dark lanes); the move file carries the pair's miner sha into the pack gate (the puller rule above).
 
 **build-1's seed, the reading and the repair (03:0x BST):** /home/build/dn3seed.log ends at 02:09:05 BST at DAA 29,732 mid-stream with no stop, shutdown or panic line (an igneumd stop writes "igneumd has stopped"), so it was killed abruptly; it ran under nohup from a shell, so no journal names the killer, and the OOM record needs sudo (the morning's build-server lane reads it); the datadir intact (13 GB). The node lane's DAA reads 25,169 (00:52:38) and 28,906 (01:55:09 BST) came from it while it lived; the chain read 32,659 at 02:57:50 BST from node1-dn3's JSON on 28670 (the observer 32,660), past 32,400 at about 02:53 as computed. Restarted on the shipper's word at 03:00:09 BST on the kept datadir with the 2720d8d2 hands pair (igneumd f2cf6a87; the same flags; setsid nohup with stdout appended behind a dated banner, the stop line in its own log; the restart script at /tmp/dn3seed-restart.sh for the morning's move): digest ba75bf6f, object version 7, the N15 lines (resumed from the exec snapshot at tip 11,901, the records continuous), DAA 32,905 in step with node1-dn3, 22 peers at 03:02 (20 inbound, the fleet's dials returning; 38 before the kill). A repair of the hub the fleet dials, not a release change; the DAA reads come from 27632 again. dn3-floor-cut.sh (the fourth re-cut from a named minute: the DAA from 28670, the floor = the publish DAA plus 7,200 to the next 3,600, the commit, both mirrors, the gate set, about 20 minutes plus the fast-time pair's 14; the latest minute before the heights move is about 12:50 BST) stands ready for main's minute.
+
+**The attack-pass record lines on the frozen class v5 1c420786 (pairing e5a4ac5978462156), both PASS on the full 10^5:** F9 exhaustion (the last chunk 03:34:54 BST): 100,000 of 100,000 seeds through the chain path, 0 exhausted, 0 panics, 0 past attempt 31, max attempt 30, first-draw acceptance 0.3145, mean attempt index 2.185 (3.185 draws per seed); F1 redundancy (census.csv 05:20 BST): 100,000 of 100,000 programs, saved max 4.688 percent (0 over 5, 0 over 10), differential mismatches 0, verifier mismatches 0, 0 panics. Nothing from the attack lane holds the 0.3.24 move; the interim at 01:55 BST was the gate as main set it. **PC 1 overnight (the hash lane, 03:4x to 05:1x BST):** the 5090 floor2 pass ended by its 45 min cap with the rows to 400 MHz (every fingerprint matched; the card left at the 400 lock until the restore job at 03:46 BST brought it back to 2,880 MHz); the CA4 sparse runs read base rows (the research lane's second exe ran base on every variant, its third failed NVRTC on the card, "identifier d is undefined"; the finding with that lane); the microbench exe exited at once (rerun as -b after the packs); the packs job fell on a read-only $pid (fixed, rerun as -b from 05:12 BST); the 5080 Ember tune, the 9070 XT tune pass and the hot table follow; PC 2 held all night for main's word ("PC 2 clear" never given, take 3 never ran).