igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

Plan 0.3.15: owed rows for 0.3.16 (the lanes' merge rule, the manifest's urgent flag, the node cut's gate line)

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 19:54:13 +00:00
parent 0aef24f747
commit 418801fac2
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/plans/release-0.3.15.md
View file

@ -99,3 +99,6 @@ The fix (node lane): the signal stamp and the signal read gated on publish 2's o
- The prover thread drops its cached tool paths when a stale binary is named (0.3.16).
- The relaunch helper fixed with a watcher, or `restart --what app` stays retired.
- Env-only defaults for the eight scripts that name the shared checkout by absolute path.
- 0.3.16's app merge, as the lanes handed it: app/igneum-app/ui/ whole from miner-ui-4 e31acab (the UI pinned to the 0.3.16 engine fields); src/live.rs and the /api/live route from ember-tune b55bc1f (the engine's node source in the site's row shape), not miner-ui-4's 0.3.15 file; Ember's 995530b and aa73005 fields (watts_total, pounds_per_day, balance_wei, price null with the manifest rule, tune_floor, the finality pause rule fd03f35).
- The publish side owes a way to set the manifest's top-level "urgent": true for an emergency rollout through a finality pause (fd03f35 reads it; igneum-ota-sign passes the document through): a publish-manifest.sh flag.
- The gate line for every node cut from here (main writes it into CLAUDE.md): a mining new node beside an old node on the live file for ten minutes, the old node's reject count read before and after, and one new node restarted mid-window re-syncing from an old peer.