4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	8e32583089	A node names its provisioner client's account whenever a client runs there, filled files or not (issue 774) ... The declaration named the account only beside its filled files (node.go), so a node whose every filled-file module was held this pass named none: on ace from 2026-11-04 01:29 its build modules and ssh-client were held for their forge binding, and the node-engine refused every write of the files they keep, and of every other module's. The account is the node's, named whenever the rendering has one. A row holds restic, the provisioned mesh's one filled-file module, with the client placed: the node's own still names the account; it named none before. Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-04 02:17:01 +01:00
jschoubben	054754482c	The running provisioner account is kept only for a client held this pass, and rows hold the guard (issue 774, review) ... The review removed the guard and the suite still passed. The guard is now provisionerHeld, a placed client held as its stand-in, rather than any placed client, so one placed and not held that composes no account keeps none stale. Rows in the held client's table: the client taken out of the node's placement while what runs names the account, read from the running own composition and from the client's running process, names no account; a placed client whose process names no user names none. With the guard removed the first three fail; with it reduced to "placed", the last. Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-04 01:53:29 +01:00
jschoubben	514cf23aef	The provisioner client's account stays named while the client is held: a held client keeps the node's handing (issue 774) ... provisionerAccount reads the user of the client's process from this pass's plan, and a client held as its stub (or carried as it runs) composes no process: on ace, 2026-11-04 01:29 to 01:33, the node's own composition named no account, the node-engine refused every filled write, and no module was handed (postgres's consumers, restic, power). A node now carries the account its client runs as (Node.RunningProvisioner: its own composition's account as it runs, else the user of the client's running process), and a placed client that composes none this pass keeps it. A row holds the client in the provisioned mesh, both ways: the account stays and restic keeps its filled files; both were lost before. Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-04 01:47:19 +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