Merge ship-docs-0321 357d8842 into master (gate: green on 357d8842, recorded by tools/ci/pre-push.sh; the full gate runs in CI on this merge)

docs/plans/release-0.3.22.md

@@ -138,3 +138,13 @@ The 0.3.23 node's heights move Devnet 3's digest to ba75bf6f, and the one-box-at
 **0.3.23 Windows take 1 FAIL (22:07 BST), install-close-23's own gap:** the installer sent the engine api/quit, the window host (alive since 21:20 BST) never stopped because stop-igneum.ps1 sits only in [UninstallRun] and CloseApplications cannot close it with the message box suppressed; the running 0.3.21 engine does not read the new install-running flag (expected) and relaunched 45 s after the quit from the host; every file stayed 0.3.21. Two more: the installer came out named Igneum-Miner-Setup-0.3.0.exe (BUILD-INSTALLER.bat passes no version; the job now passes -Version from version.h and asserts the output name; the batch fix is a packaging commit), and the stale flag is removed by a one-file job. The fix (the update-return lane): the .iss install path runs the stop step itself (the host by path after the quit, then the unlock wait), packaging only, the crate unchanged at 7c7489ac, so it rides 0.3.23; the kit re-cuts from it, take 2 in the same shape, the smoke read the gate (the known-failed shape: an install over a running 0.3.21 host, read on PC 2). The test the lane wrote asserted the stop script's text, not the install path's execution.
 
 **PC 1 (22:2x BST):** the Power Helper task's process dies at once after each start since 22:08 BST (six "helper started" lines, no command processed, the task Running with no process; its last processed command 21:45, its idle exit at 22:05 clean; the app's tune idle), so the 5080 grids took unlocked rows only and the hash lane runs the lock-free jobs first (the 9070 XT G1 and ladder from 22:27 BST, then the family run and the v5 bench), the locked grids and the SM-sparse job returning when the helper answers; the helper's death is a 0.3.24 item for the update-return lane (the helper writes its reason before exiting, the engine shows "power control: helper not running (<reason>)"). The pool lane's 0.3.24 strings: fork pool-prepare-node 95ae3e50 on the v5 object tip (the pool-mode seed-change exit and the prepare deadline), daemon pool-finish-22 05f86a7f (the node connections reconnect by themselves after a node restart; the rejection counters), register MF-15 ff17216d; the split switch stays never. The 0.3.24 object pairs with the frozen class-v5 1c420786; the post-freeze fix 8ca66afa (AP-F4-1's weak-day redraw, the verified last resort; the pinned packs and fingerprint unchanged) is 0.3.25's.
+
+## 14. The 0.3.23 move closed, the 0.3.24 pin, the public alias (22:4x to 23:0x BST)
+
+**The 0.3.23 move closed 22:40:25 BST:** every one of the 34 Devnet 3 nodes reads igneumd/2.1.0-2720d8d2 on digest ba75bf6f, synced (20 by the puller at 22:30:25, build-1's three at 22:30:54, the 11 MINE=0 nodes by hand 22:39:04 to 22:40:25 after the puller's two faults; their nodes were down 22:34:31 to 22:39, the rescue script's own pkill matched its shell; the 18 hands miners back 22:34:16 to 22:35:46 once fb147dd1 entered the gate list). The chain rate: 0.03 chain blocks/s at 22:31, 0.18 at 22:34, 0.49 at 22:35, 0.44 at 22:48. **First lock on the new side: checkpoint 584, block cde51734, blue score 17,522, at 22:49:04 BST**, 93.1 percent of active and 85.8 percent of total signed. The puller's two fixes are in and redeployed on all 34 (MINER_ONLY never carried into a restart environment; every box holds move/env-last refreshed each minute so a MINE=0 box restarts too; the pack gate's pair list is the parameter PAIR_MINER_SHA16), their self-tests on the two known-failed shapes run on dn3-x1 before the next move file. dn3-j1 behind the dead proxy rejoins by the pull.
+
+**The public alias (main's rule: a public alias moves in the same publish as the manifest entry, checked post-deploy by index version == manifest version per platform):** dl/public/igneum-downloads.json had named Mac and Windows 0.3.20 while the manifest served 0.3.23. The --public arm had refused every publish since interface 1.0.1 ("the public igneum-app-latest.json would still carry the token": the signed interface entry's URL); fixed on release-0.3.24 (80a4cfb1: the public copy leaves the interface entry out, the apps read it from the token manifest); the signer rebuilt under the lock; the public Mac alias and the index moved to Igneum-Miner-0.3.23-2720d8d2.dmg 4ada2807 at 22:56:42 BST (the hive already 0.3.23; Windows stays 0.3.20 until its entry). The post-deploy assertion is a 0.3.24 tooling item.
+
+**The 0.3.24 node pin:** 774f16c9 on v5-object-0323 (the v5 object: program_class_v5_activation_daa 28,800 on igneum-devnet-3, byte 6 exact, the window 86,400, pairing igneum-pow class-v5 1c420786, chain id 4463 below the floor and 4464 from it, the uniqueness test over every object, the heights unchanged, the pool split out), cut on the fast-time lane's restart-step PASS (pair 4 c8f9b383); every gate green: build ed36f246 (22:29 BST, igneum-pow-v5 paths 8), core 155, miner 28, pow 19, p2p-flows 38, exec 46, consensus 126 at gate priority (22:44:24 BST; the first run's one red at 205 ms under box load 127, the known class), the canary set with digest 4a284b1d and the mixed-version refusal both ways against a 2720d8d2 node; release-0.3.24-node open on it at 22:45:19 BST. The floor at 28,800 is about 01:52 BST on 8 October at 1.0 DAA/s and holds for a publish minute up to 23:52 BST (DAA 21,600); past it the constant re-cuts to 32,400 (one script run, the same gates, about 25 minutes). **The testnet re-cut staging 47b9b229** (774f16c9 + 34892a36: 18 decimals, the 16-byte subsidy layout, the emission rescaled, the final 5 October message, the cache-rung field at 0, v5 at never on the testnet until the post-crossing re-cut, chain id 4462; testnet digest b2e856ed, genesis re-hashed; every gate green, Devnet 3's digest unchanged at 4a284b1d on its binary, a live testnet node on the old object refused) fast-forwards onto release-0.3.24-node after one Devnet 3 canary read on its own binary (rule 4a), and the pin is then 47b9b229, one cut carrying both. The 8ca66afa post-freeze fix is 0.3.25's pairing. **release-0.3.24 (the app side)** open at daa7427b: the version bump first (rule 15, six places green), dash-24 19ab2a87 (the .screen caps 1280 and 1440 px, Settings in two columns), pool-finish-22 05f86a7f (the daemon reconnects after a node restart; rejections by code), igneum-pow and proto-cuda/packs-ca3-v5 from 1c420786 (rule 7: the node, the pool daemon and the app's CPU re-check pair against the pinned igneum-pow; the Mac node pair build on 774f16c9 failed on StateStream until the tree carried it; the build-server lane's --ship seed class the same, its overlay re-pointed), power-helper-24 f1395775 (the helper's start facts and exit reasons; the engine names a helper that is not running), publish-public.sh's interface fix; app gate GREEN on build-1 (284 + 35 + 8), UI 87.
+
+**0.3.23 Windows take 2 (22:37 BST) FAIL before the install:** ISCC exit 2 on install-close-23's new [Code] (an unused Age: TDateTime var; Inno's Pascal has no TDateTime); fixed at 4ad6c199, release-0.3.23 = 710e1fea, take 3 in the same shape. **PC 1's helper reading (22:46 BST):** the exe on disk is the 0.3.20 engine (sha 0443ae17), an unelevated helper started by a job runs and answers, the scheduled elevated instance is refused (Last Result 0x800710E0) and invisible to an unelevated job, and the 0.3.20 engine's tune path wrote the legacy helper.ps1 and truncated cmd.txt (its "task not registered" branch, the prompt path); the locked grids on PC 1 wait for the 0.3.24 helper (f1395775 plus the S4U registration and the legacy branch deleted); the lock-free jobs run: the 9070 XT G1 14 of 14, the ladder flat at 18.8 to 19.2 MH/s (the watts owed), the family run next.