2 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	af267cb557	Take the catalogue from mesh-sdk in internal/inventory and internal/link, and keep the tests that read this repository's own manifest, Dockerfile and Makefile in internal/ownmanifest (issue 1381, 5 of 6 import swaps) ... The three tests of the controller's own module.json (process, claimed seat, addresses), the Dockerfile and Makefile pin test, the build-agent registry test and the manifest-in-use seat test move with their old package, as tests of mesh-sdk's exported API; a moved test is exempt from failing first.	2026-10-20 08:27:10 +00:00
mesh-toolsandClaude Opus 5.5	755457cc37	Let the tool runner's account hear the event families its manifest names (issue 745, ADR 0367) ... A session on the mesh MCP server polls for every verdict, answer and delivery because the tool runner's account hears no event. ADR 0367 lets the tool runner's module name, one by one, the families a session may wait on: the manifest's `waits`, refused for any other module and for a wildcard. The controller grants the runtime's account a plain subscription on those subjects alone, makes no durable consumer for them, and issues the same list in the tool runner's membership, so the grant and what `mesh_wait` offers come from one composition and no call or setting widens it. A family on a seat whose events end in a kind or an asker must name it, and is refused at composition without it, so it is never granted a subject nothing publishes on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 23:05:14 +00:00