4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	e3ce4b095c	Count mesh-sdk's kept RuntimeModule as the tool runner while node-tools' trunk manifest leaves tool-runner out ... The running indexer refuses the tool-runner word, so node-tools' trunk manifest takes it out again (mesh-tools fix/l3-words-after-judge); trunk's judge then refuses node-tools twice (its waits, its runtime bundle) and mesh-grants would compose its node users as plain modules. One helper, sdk/toolrunner.Is, counts a manifest as the tool runner when it says tool-runner or its module is the SDK's deprecated catalogue.RuntimeModule; the judge's waits and undelivered-bundle rules and mesh-grants' declared records ask it. It goes once tool-runner is back on node-tools' trunk manifest (issue 774, issue 1585 note 42). Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-03 21:36:26 +01:00
jschoubben	b96a4f1d99	Pin mesh-sdk b7abe203a929, the group's head of feat/l3b-bus: it keeps, deprecated, the exported names the running parts still use ... Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-03 18:50:12 +01:00
jschoubben	1387b10e78	Take a missing graph state as no graph yet and a Publisher's directory as the nearest module above it ... The indexer's recompute and merge failed on listing a graph bucket not yet on the bus, and a package published from inside a module's directory had no publisher, so the dependents of a build module missed what imports its packages (review findings 3 and 4 of L3). Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-03 17:21:01 +01:00
jschoubben	3411b91571	The module graph is mesh-delivery's own: a Go module sdk/ with package graph, used by path by the indexer, the view and the checker, and the seat mesh-catalog's answers built from mesh-sdk's contract types (the operator, 2026-11-03: no graph-related code in mesh-sdk, only contracts; research 081 D11, D13)	2026-11-03 16:56:37 +01:00