4 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	41f18b2452	Keep today's module mesh-delivery in the catalogue, unchanged: its removal follows the handover as a pull request of its own	2026-10-20 06:41:48 +00:00
mesh-tools	09f0b0d5ab	Move the delivery module to the gate: mesh-delivery-gate claims the seat with its own buckets and reads (issue 1346)	2026-10-20 00:19:19 +00:00
jschoubben	8f7aeeeb81	Hold a delivering delivery for a failed backup before the send; release asks the backups again (issue 1068)	2026-10-17 22:45:03 +02: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