The seat-list finding is read from the node's own state, so a restart clears it (issue 1966) #223

Merged

mesh-tools merged 2 commits from fix/1966-seat-list-finding-from-the-bus into main 2026-11-11 01:34:12 +00:00

Conversation 1 Commits 2 Files Changed 5

+102 -22

2 Commits

Author	SHA1	Message	Date
jschoubben	e64c8ad0ca	The node's golden grant reads its own findings, as the grants part composes it (issue 1966) ... mesh-grants gives the engine the owner's read of its state findings for its own node's keys (EngineFindingsGrants); the golden grant held only the write, so the engine could not read the finding it clears at the first full read. Builds: design 47 H-7, ADR 0636 §1 (the finding is cleared at the first full read), ADR 0596 §2 (the owner reads its state), issue 1966 Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ	2026-11-11 02:23:10 +01:00
jschoubben	6304332ad5	The seat-list finding is read from the node's own state, not kept in memory (issue 1966) ... A new node-engine process cleared nothing at its first full read of the seat list, because the Waiter remembered in memory whether it had written the finding; ace and g14 kept the condition for ever. The Waiter now asks the node's state findings whether the finding stands, clears it at the first full read and writes it at the bound only when it does not stand. Builds: design 47 H-7, ADR 0636 §1 (the finding is cleared at the first full read), issue 1966 Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ	2026-11-11 02:20:42 +01:00