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.

modules/rofi/README.md

@@ -70,9 +70,10 @@ A Wayland session gets the same menu from whichever launcher holds the seat ther
 - `icon-theme` and `window-command` are gone. They named an icon theme and a program (`wmctrl`) that
   nothing installs. rofi's defaults serve.
 
-## What it leaves as found
+## What it moves out
 
-- `~/.config/rofi/themes-repo/` (a cloned theme repository), the five symbolic links into it
+- Moved out by the node-engine to `~/.local/state/mesh-moved/rofi/` with a list, never deleted (ADR 0422 §4),
+  because no `knows` names them: `~/.config/rofi/themes-repo/` (a cloned theme repository), the five symbolic links into it
   (`applets`, `images`, `launchers`, `powermenu`, `scripts`), `colors/`, `theme.rasi` and
   `powermenu.rasi`.
 - The predecessor's scripts in `~/scripts`: `rofi-launcher-normal`, `rofi-launcher-terminal`,
@@ -83,8 +84,9 @@ A Wayland session gets the same menu from whichever launcher holds the seat ther
 
 Once the `i3` module carries the main i3 configuration:
 
-1. Delete `~/.config/rofi/theme.rasi`, `powermenu.rasi`, `colors/`, the five links and `themes-repo/`.
-   Nothing reads them any more.
+1. `~/.config/rofi/theme.rasi`, `powermenu.rasi`, `colors/`, the five links and `themes-repo/` are moved
+   out for you (with a list, in `~/.local/state/mesh-moved/rofi/`). Nothing reads them any more; delete the
+   moved copies when you like.
 2. Delete the four scripts above from `~/scripts`.
 3. Your scripts that call `rofi -dmenu` keep working. Calling `dmenu` instead lets them follow the
    seat, for example to a Wayland launcher later.
@@ -102,3 +104,10 @@ The module no longer writes a file into i3's `config.d`. Its window-manager line
 under `files/i3/` where it had one) are a contribution to `node-display-session`. The i3 module places
 them in its own configuration under a `# <module>` line, so this module depends on a window manager
 being assigned beside it.
+
+## Files it does not know
+
+Each directory or archive this module declares says how it treats a file it did not write (ADR 0422, ADR 0416).
+
+- `~/.config/rofi`: holds only what this module declares; anything else is moved out by the node-engine to `~/.local/state/mesh-moved/rofi/` with a list, never deleted (ADR 0422 §4).
+- `~/.config/rofi/themes`: holds only what this module declares; anything else is moved out by the node-engine to `~/.local/state/mesh-moved/rofi/` with a list, never deleted (ADR 0422 §4).

modules/rofi/module.json

@@ -34,14 +34,16 @@
       "type": "directory",
       "path": "${machine:account-home}/.config/rofi",
       "owner": "${machine:account}",
-      "mode": "0755"
+      "mode": "0755",
+      "unknown": "move-out"
     },
     {
       "id": "themes-dir",
       "type": "directory",
       "path": "${machine:account-home}/.config/rofi/themes",
       "owner": "${machine:account}",
-      "mode": "0755"
+      "mode": "0755",
+      "unknown": "move-out"
     },
     {
       "id": "configuration",