7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	809288da69	E-5 marked waits: a wait on a marked event runs only on the operator's warrant for that one wait ... mesh_wait goes through the runner's approval gate (node-tools/internal/approval, Gate.Waited): a wait whose subjects overlap a marked subject of any module the catalog half lists (the newest entry of every followed branch, with the served entry of each module this runner serves) is an act of the runner's own module and build (MESH_FINGERPRINT at its start), asked once on operator-channel as "Wait on <names> on <node>?", and held, subscribing nothing but its ask's decided, until its timeout, its caller's going or the choice. On a warrant it subscribes, its timeout running from then, and answers {answer, approval}. Before the marks are read nothing is asked; a wait from a seat is never marked. The state fixture moves to meshtest so the console's table can hold a gate. Builds: design 34 every-event §34, §35, §36, §37; design 47 G lead answer A-168 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h	2026-11-12 05:41:53 +01:00
jschoubben	4116809162	Merge branch 'feat/47-G-fix11-a2' into feat/47-G-fix11-a3 ... # Conflicts: # node-tools/internal/console/wait_test.go	2026-11-12 05:27:26 +01:00
jschoubben	6851ee1657	A-7 tools: mesh_approvals reads and steers what was asked; mesh_describe says a mark and its source ... The mesh MCP server gains mesh_approvals: with no argument the calls asked on the machine in the last day, newest first, with state and fingerprint, the marks the gate applies with their sources and the catalog revision, and the state's fill against its cap (every machine's keys together); an ask read whole with the act's digest; record asking the hand-act again, and cancel taking an open ask back, each recorded in the hand-act log first and refused when it cannot be. mesh_describe answers needs-approval with its source, and a marked call that reached no one names withheld and mesh-grants.grants_user_list. Builds: design 46 7-approval-mark §18, §6 (the mesh MCP server's withheld answer), §22 (eight tools) Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h	2026-11-12 05:24:41 +01:00
jschoubben	0b0f879e86	E-4: a misspelt event name is refused, not waited on for ever (issue 1966) ... Before it subscribes, mesh_wait checks each name's emitter against the catalog half the tool runner holds (its seats' definitions and its modules' entries), refusing one neither knows and naming the half and its revisions; a known emitter's undeclared event is waited on and its timed-out answer says so; while the half is not yet read the answer says the names were unchecked. The first views answer the halves by branch for it. Builds: design 34 every-event §14, §19 (rows of the table of refusals) Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h	2026-11-12 05:11:52 +01:00
jschoubben	662ab2a3b1	E-3: mesh_wait takes any event name (issue 1966) ... waitAnswer no longer reads the membership: each name becomes its subjects through buscompose.EventSubjects, optionally narrowed by from (seat, module or stream), at most 16 names, a subject once; the heard event is named by buscompose.EventName with its namespace and its own time, and a decided event says the operator's answer is read only with claude_code_answer. WaitIssued and Membership.Waits go; the refusals are one table. Builds: design 34 every-event §13, §15, §17, §19, §26 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h	2026-11-12 05:06:36 +01:00
jschoubben	31247dff6b	TLS-5, TLS-6: the tool runner holds the indexer's manifests and modules and the assigner's placement and seat-holders from their first views and views events, never their state, and the console gains mesh_first_views and mesh_first_view_again (ADR 0615, ADR 0621, issue 1966) ... Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig	2026-11-04 12:06:20 +01:00
mesh-toolsandClaude Opus 5.5	21d038d339	End every wait in flight when the tool runner stops (issue 745) ... Closing the console shut its server down with a context that never ends, so a stop or restart of the tool runner waited on any mesh_wait in flight for up to ten minutes. The server's base context is now cancelled first, ending every wait at once, with a five-second shutdown as a backstop (second review of issue 745). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 00:47:59 +00:00