novox/mesh-host

A directory says how it reacts to files it does not know; the node-engine moves out what a move-out directory does not know (issue 1024) #117

Merged

mesh-tools merged 2 commits from feat/owned-paths into main

2026-10-17 16:20:06 +00:00

Author	SHA1	Message	Date
mesh-tools	dae79c7643	Prove move-out on a machine that is not Arch (issue 1024) mesh/merge-gate head dae79c76434c merged into trunk cd13f7726ef0 — pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes wi… Details mesh/repo-check head dae79c76434c merged into trunk cd13f7726ef0 — pass: its merge-check.sh passed Details mesh/delivery delivered Details The merge check's build container has no pacman, so the acceptance test now stubs it and names the host it was built for, as other command tests do; nothing in the node-engine itself changes.	2026-10-17 16:16:02 +00:00
mesh-tools	d237dee4c9	Let a directory say how it reacts to files it does not know, and move out what a move-out directory does not know (issue 1024, ADR 0422) mesh/merge-gate head d237dee4c9e3 merged into trunk cd13f7726ef0 — pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes wi… Details mesh/repo-check head d237dee4c9e3 merged into trunk cd13f7726ef0 — fail: its merge-check.sh failed: --- FAIL: TestAMoveOutDirectoryKeepsOnlyWhatItKnows (0.… Details mesh/delivery superseded: a newer head of the same pull request Details A directory or archive resource carries `unknown` (move-out, module, program) and `knows`. For move-out under a home, every look moves each path the declaration does not know into ~/.local/state/mesh-moved/<module>/<time>/, the list written before each move, without following a link, a young path waiting, a socket or pipe left and reported, nothing made when nothing moved, and another file system refused. Reviewed in two rounds.	2026-10-17 16:09:33 +00:00