Node agent: a switch never marks the new run's modules, a failed read or a bus pause keeps what runs, stale composer marks clear (issue 1126, group fix/1126-switch-safe) #155

Merged

mesh-tools merged 2 commits from fix/1126-switch-safe into main 2026-10-27 23:52:28 +00:00

Conversation 1 Commits 2 Files Changed 9

+357 -18

2 Commits

Author	SHA1	Message	Date
jschoubben	a6e53a4858	A composer's mark never covers another cause, and a run that ended marks and clears nothing (issue 1126, review of the switch, round 1) ... NotComposed marked from a read have whatever its phase: an apply that failed, naming the want's build and digest, became a composer's mark, which baseline then took for what runs, and never applied again. It now marks only a have that runs, says nothing, or is a composer's mark already. And its loop, whose reads can take seconds, checks the run's context at each module, so a run that ended writes no have.	2026-10-28 00:41:25 +01:00
jschoubben	4993f1b1d7	Make the switch between composers safe: a composer tells only its own run's agent, a pass whose run ended refuses nothing, a bus that pauses is tried again, a mark keeps what runs and clears at the next start; pin mesh-sdk 7359d18 (issue 1126) ... Live 2026-10-28: the own run's last pass, failing on its run's end, marked every module of the controller-mode agent that replaced it (ace 60, shanks 63), and the marks dropped the build and digest because the have read failed in the bus's reload pause. Now: the refusal hook is bound to the run's agent and ctx; a pass whose context ended returns nothing; JetStream not enabled or no responders are tried again after 1, 2 and 4 s before any mark; NotComposed reads the have again while the bus does not answer and marks nothing it cannot read; baseline takes a have a composer marked as what runs, so a mark it did not make clears; each run's shadow lives with the run.	2026-10-28 00:34:10 +01:00