release-0.3.21 plan: section 6, the node line staged at 96161037 with its suite lines and the two box-input rules

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-07 15:56:12 +00:00
parent 44abb3288c
commit 0e3156f137

View file

@ -64,3 +64,7 @@ sha256 279b1b690e854fc9, the string read back, pairing 8c728ca3 at byte 5. The d
**Three more in (16:2x BST):** update-return-21b a64c193f (the eGPU card kind from a USB4 or Thunderbolt router in the device's parent chain, the Power Helper's fault line and its stale-prefix fix; app 255 + 32 + 8, UI 76); first-block-21 at cc9141cb replacing 6e555d47 (main's "seen once": the first-block card waits until a window has shown it, POST api/card/seen, ladder.rs card_seen; app 255 + 32 + 8, UI 67); miner-reliability-21 at 018440ae (the register: MF-11 in the update-return lane's words, MF-12 the pool stall, MF-13 the Power Helper's stale count; code unchanged since 4a28eb59, CI success). UI tests on the merged tree 76 of 76; the app gate on build-2 at the merged tip below. GitHub refused pushes with "Internal Server Error" from about 15:25 to 16:18 BST, transient.
**The node order, final (16:3x BST):** on 55768f88: c631c64b first (the test-only fix of the two stale integration targets, 1026 → 1282; both green on build-2 at 15:34Z), then 52e96c94, f067f7c1, b0444f51, 437f0438, 2e32d5f6, f95178a1, a6864e36, d8bceca5; the tip's suite set runs the consensus crate whole (`-p kaspa-consensus` without `--lib`: the lib and both integration targets) beside consensus-core, the miner, kaspa-pow, the exec suite and the three checks (the suite rule from the 0.3.20 known-red finding). era-vdf-node 394a5902 is 0.3.22's.
## 6. The node line staged: release-0.3.21-node = 96161037 (the node lane, 16:5x BST)
On 55768f88 in the final order, each green and pushed with the exec suite between: c631c64b → 7ee808d6, 52e96c94 → 78f0e771, f067f7c1 → be60803a, b0444f51 → 4362119b, 437f0438 → 632437a0, 2e32d5f6 → f2caa145 (the DST_ADDRESS both-add resolved), f95178a1 cherry-picked → 31407f27 (a merge would have pulled the whole genesis-forward branch; the consensus lib 120), d8bceca5 → 96161037 (the exec suite 36). Byte 5, igneum-pow 8c728ca3. On the tip: consensus-core 126, the consensus crate whole green (the lib 120 and both integration targets). The tip's set stopped twice on the boxes' inputs, not the code: the 60x file test wanted the two new switches (pool split, peer directory) in the fast-time file (added as null); the miner's pool tests read the proto-cuda packs four directories above the crate, absent on the boxes and then the 6 October stream where the node pairs 8c728ca3's amended one (the amended packs placed on both boxes). Two rules for the plan: after every merge that touches OverrideParams the 60x file's field diff is re-run; the miner's pool tests want the packs of the paired igneum-pow's stream beside the fork on every box. The set re-runs from the miner suite (miner, kaspa-pow, the three checks), then the build on build-1 and the digest pair (the previous object eada4bda, the floor-moved 4bbbe816); the binary about 17:15 BST with the node lane's two gates from that minute and the fleet's set on the warm pods.