From 418801fac2e1ae1ba218446f25fb9f905697dc7c Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Tue, 6 Oct 2026 19:54:13 +0000 Subject: [PATCH] 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) Co-Authored-By: Claude Fable 5.1 --- docs/plans/release-0.3.15.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/plans/release-0.3.15.md b/docs/plans/release-0.3.15.md index f3c24000a..cfc782182 100644 --- a/docs/plans/release-0.3.15.md +++ b/docs/plans/release-0.3.15.md @@ -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.