6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	ae4b86e333	route-proxy's proof skips aloud when mesh-networking is not beside, since the running checker places none for the node-engine until this release is delivered ... With mesh-networking beside, or with nothing beside and the captured copy read, it still judges the manifest. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 20:39:56 +01:00
jschoubben	3293f6ddcd	Take the environment's rendering integration tests with the code they test ... ADR 0593 §7: the environment's rendering left mesh-sdk for the node-engine, so its two integration tests (the POSIX environment sourced twice, and the service manager reading the systemd rendering) move with it. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 19:21:10 +01:00
jschoubben	1ada760a64	Hold the proofs that a manifest composes, which left the judge's and route-proxy's tests ... ADR 0593 §7: the composition is the node-engine's, so its tests hold what the indexer's judge tests and route-proxy's tests proved by composing: a bundle's words per machine, a Go bundle's delivery, the credential form in a handed plan, settings refusals, placeholder and vault refusals, the session's files, a field set aside composed whole, route-proxy's manifest composing for a machine, a route endpoint's machine port in six cases and the plan's route entry end to end. Two table tests, one subtest per item; route-proxy's manifest is captured beside the catalogue. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 19:19:49 +01:00
jschoubben	d68e241724	Take the catalogue's composition rules into the node-engine ... ADR 0593 §7: the composer with its refusals leaves mesh-sdk, so mesh-sdk carries no composition rule. The catalogue functions only the node-engine's composition reaches (Resolve, Resolution's Compose, Declaration, DataItems, LeftOut, Rules and the rest, the settings, placeholder and template refusals, the rendering helpers) are copied with their tests into internal/compose/resolution; a method of a mesh-sdk shape becomes a function taking it first. The composition calls its own copies, and the captured catalogue its tests read lives here now, shared by mesh-compose's tests. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 19:15:55 +01:00
jschoubben	be0226b624	Stop verifying composition signatures: the node applies only its own ... ADR 0593 §6: a composition read from composed-<node> is a record never applied, and the engine applies only what it composes itself, so no composition carries a signature and nothing is verified. The agent's trusted signers, its signed-composition test and the unused signing helper of the integration bed go, so mesh-sdk can drop SignComposed, VerifyComposed and Composed.Signature. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 19:01:12 +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