Live 2026-11-19: g14's build runtimes asked seat:mesh-wants.input without a call id (refused by the assigner) because their seat list, read once at start on 11-17, did not name input; a failed first read was silent. Now an ask of a verb of a seat the list defines but does not name reads the list again once (one shared read), and is refused saying so if still unnamed; undefined seats and module tools ask as before; an unanswered first read is said in the journal. Recovery used meanwhile: restart of g14's mesh-build-go and mesh-build-node runtimes. HOLD: merge with the runner's start bound in place.
Reviewed-by: mesh-code-reviewer@shanks at 76df3cb420 (three rounds)
Live 2026-11-19: g14's build runtimes asked seat:mesh-wants.input without a call id (refused by the assigner) because their seat list, read once at start on 11-17, did not name `input`; a failed first read was silent. Now an ask of a verb of a seat the list defines but does not name reads the list again once (one shared read), and is refused saying so if still unnamed; undefined seats and module tools ask as before; an unanswered first read is said in the journal. Recovery used meanwhile: restart of g14's mesh-build-go and mesh-build-node runtimes. HOLD: merge with the runner's start bound in place.
Reviewed-by: mesh-code-reviewer@shanks at 76df3cb420c6abb10c93b0172b7cf5d316a7eef1 (three rounds)
https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
A bundle's ask of seat:mesh-wants.input reached the holder with no `call` and was refused ("call is one token of 16 to 64 ..."), so no
composition step passed: the runner chooses the call only for a verb its seat list says sends chunks, and a verb the list did not name
(a list read once, unread, or stale) was taken for one that does not. chunkedAsked reads the list again once and, where the verb is still
not named, refuses the ask saying why. A first read of the list that ended without an answer is now said in the log.
Builds: design 47 G A-249 (the runner receives a chunked seat answer for the bundle), ADR 0636 §1 (the seat list is read, not guessed)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Live 2026-11-19: g14's build runtimes asked seat:mesh-wants.input without a call id (refused by the assigner) because their seat list, read once at start on 11-17, did not name
input; a failed first read was silent. Now an ask of a verb of a seat the list defines but does not name reads the list again once (one shared read), and is refused saying so if still unnamed; undefined seats and module tools ask as before; an unanswered first read is said in the journal. Recovery used meanwhile: restart of g14's mesh-build-go and mesh-build-node runtimes. HOLD: merge with the runner's start bound in place.Reviewed-by: mesh-code-reviewer@shanks at
76df3cb420(three rounds)https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
A bundle's ask of seat:mesh-wants.input reached the holder with no `call` and was refused ("call is one token of 16 to 64 ..."), so no composition step passed: the runner chooses the call only for a verb its seat list says sends chunks, and a verb the list did not name (a list read once, unread, or stale) was taken for one that does not. chunkedAsked reads the list again once and, where the verb is still not named, refuses the ask saying why. A first read of the list that ended without an answer is now said in the log. Builds: design 47 G A-249 (the runner receives a chunked seat answer for the bundle), ADR 0636 §1 (the seat list is read, not guessed) Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2syPull request closed