5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	03b7fcd7bb	The sandbox fails a node whose change refuses a module the node-engine did not hold, in that module's words, instead of passing it with the rest composed (issue 774, review of the sandbox input)	2026-11-03 13:28:44 +01:00
jschoubben	7b8f5e7805	The sandbox composes a node as its node-engine does, from an input that says how, and names a node it cannot judge from an older engine's input (issue 774, ADR 0593 §9)	2026-11-03 13:28:44 +01:00
jschoubben	df13a83a91	The sandbox composes a node from the input its engine took in, through one shape ... The second sandbox fault of the same kind on mesh-host #200 (postgres's secret reader handed, the module not): the engine stripped the whole catalogue from the input it answers, so the sandbox composed the node's own modules from the indexer's source manifests while the bus reader composes them taken in from their builds (artifacts, templates archive texts, what is handed). Both sides now go through composer.SentInput: the node's own taken-in manifests and kept builds stay in the input, and the sandbox composes them over the cases'. An input past what one bus answer carries is refused in words. A conformance row composes one node through the bus reader and through the sandbox and requires the same declaration. Issue 1126. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-03 01:55:08 +01:00
jschoubben	61a3bd996d	The sandbox composer carries the module the mesh provides itself ... A check that composes with a candidate's own composer (any mesh-host change) gave it the indexer's manifests alone, and the input carries no catalogue, so mesh-wireguard (shipped with mesh-sdk, no repository) was missing: "nothing provides mesh-wireguard / mesh-addressing" on novox for mesh-host #200. Each case now lays the provided module's manifest over its shelf, as the bus reader does. Issue 1126. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-03 01:44:15 +01:00
jschoubben	9a12f2851f	The node-engine owns the composition it alone runs (H1, H2) ... ADR 0593 §1 and §7: compose, its bus reader and runtime reader, takein, validate, the overlay generator, the composer's run and mesh-compose, and the judgement of a move leave mesh-sdk for the node-engine's internal packages, so no other module composes and a change to them rebuilds only the node-engine. The shapes others read (the composer's request and verdict, the overlay's names, compositions and answers) stay in mesh-sdk. The node's grant is now a golden file of what the grants part composes, since the composer of the bus's user list leaves mesh-sdk too. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 18:24:05 +01:00