Judge each machine on a plan's last send and resume a plan lost to silence with plans retry, so a resumed plan is not failed by its own old sends (issue 1886, ADR 0531)

+325 -32

2 Commits

Author	SHA1	Message	Date
jschoubben	4d4d51eb01	Pin the resume of a lost walk's refusals beside a newer or a related plan, and cite ADR 0360 §7 and ADR 0531 (issue 1886) mesh/merge-gate head 4d4d51eb017f merged into trunk 219fdcd7f00c — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; the ch… Details mesh/repo-check head 4d4d51eb017f merged into trunk 219fdcd7f00c — pass: its merge-check.sh passed Details mesh/delivery delivered Details mesh/check failed: integration: github.com/novox/mesh-controller/internal/identity.TestACertificateChainsToTheMeshsOwnAuthority: authority_test.go:45:…	2026-10-23 08:10:08 +02:00
jschoubben	b7d996878b	Judge a walk's machine on its last send, enter a resumed tier anew, and resume a walk lost to silence (issue 1886) R4e, resumed at tier 1 after a stop of five hours, named ace and shanks silent within seconds of tier 1's send: the walk judged each machine on every send it had made it, tier 0's of 00:23 too, held against tier 1's templates, and measured the bound from it. A send carries the whole declaration, so the last one is what a machine is judged on. The resume kept the tier's entry of before the stop, so the plan read waiting for 5h48m. And plans retry refused a walk failed only by the gate's silence, though its machines had since applied.	2026-10-23 08:02:11 +02:00

Judge each machine on a plan's last send and resume a plan lost to silence with plans retry, so a resumed plan is not failed by its own old sends (issue 1886, ADR 0531) #444