4 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	652b00b25b	Say on every directory how it treats files it does not know, and check it (issue 1024, ADR 0422) ... Every directory and archive resource carries `unknown`: move-out for a home folder whose program writes nothing there (the node-engine, delivered in mesh-host #117, moves the rest to ~/.local/state/mesh-moved/<module>/ with a list), module for ~/.ssh and ~/.claude, program elsewhere; `knows` keeps what a program or the operator relies on (powerlevel10k's compiled files, i3's scripts and the asus/g14 drop-ins, dunst's slack rule, betterbird's records, node-env's forge credential, issue 1033). Two shared folders are no longer declared. Each module's README says it. checks/owned holds every manifest to it; checks/sshdir stays while main's merge check runs it (issue 1035). Tests that pin a manifest follow the new key only. Reviewed in three rounds.	2026-10-17 16:23:03 +00:00
mesh-tools	0260ae92f6	Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main	2026-10-16 09:42:45 +00:00
jschoubben	eed5e8958a	A definition names no host path for its own data ... Twenty-eight modules' data directories are placed: the root as place ".", a sub-directory named by its id, and every host-side reference — binds, secrets, own secrets, grants, receives, file paths, mounts, env-files — as ${dir:<id>}. Resolved on the default root every path is the one the manifest named before, which the controller's TestPlacedDirectoriesKeepTheirPaths proves over both checkouts; so no data moves and no machine sees a change. Five directories whose id is not their last segment keep their path as a placement (novox/hq issue 119, ADR 0112, design 27).	2026-09-30 21:10:18 +02:00
jschoubben	29fe7c5bd0	local model: an ollama provider + a local-model consumer (ADR 0055) ... Model access answered by a NODE, not a licence. `ollama` runs the model server on host network (0.0.0.0:11434) and provides model-access at node scope, serving its port and model — it mints nothing, so it is server-only, no runtime. The `local-model-consumer` requires model-access, gets the endpoint (no secret), and its templated openai.env carries OPENAI_BASE_URL=http://<at>:<port>/v1 + OPENAI_MODEL. One provision, two answers: the mesh's own model behind the same interface as a vendor's. Proven end to end by the mesh-lab local-model bed (green). Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF	2026-09-07 05:25:21 +02:00