4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	c9d8950fd0	Every module follows the assigner's new places: the contracts' go/ path, mesh-wants in the delivery contracts, the state and tool assignments (issue 1966) ... The legacy key form placement.<node> is gone from the client, so the readers and their fixtures lose it. The check noplacement now also refuses the assigner's retired names in a manifest. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-05 22:29:07 +01:00
jschoubben	e009088150	Point messenger, mesh-watcher, restic and mesh-issues away from the controller ... The controller is not placed (ADR 0590): messenger no longer treats it as a condition owner or a walk's subject, mesh-watcher reads only where the bus runs, restic tells the operator to compose the machine or set config through the seats that do it now, and mesh-issues' examples name a placed repository. mesh-issues keeps mesh-controller among its owners: issues located there, issue 1126 among them, and route-proxy until it moves, still name it (issue 1126 B11). Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 12:29:56 +01:00
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
jochen	0ae7933d54	Tell the operator what the mesh finds wrong, and watch the watcher (hq to-be 45 phase 1) ... The mesh noticed 48 core failures in six days and told nobody (ADR 0227). messenger holds the operator-channel seat: it consumes the controller's condition events and sends them to Telegram and the desktop notifier, deduplicated by key, reminded once, edited on clear, capped at 20 an hour with the rest folded, and refusing anything carrying an address, a path or a secret. mesh-watcher, on a machine other than the control node, sends to Telegram directly when the self-check heartbeat or the bus goes silent.	2026-10-06 09:35:55 +02:00