3 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
jochen	38b56a7877	node-env: the account's environment as one module's two files ... Every module contributes variables and PATH entries as facts, and one holder of node-environment places them (novox/hq ADR 0203, to-be 41 WP3). This is that holder: no package, no process, no tools — the directories it owns under the home and two files the controller fills, the POSIX file at the path the seat fixes (~/.config/mesh/environment.sh, sourced by the login shell) and environment.d's 50-mesh.conf for the account's service manager and graphical session.	2026-10-04 03:59:50 +02:00