hostwarden-fleet-readlisted

# hostwarden-fleet-read **Overrides.** Load them before anything else, key `hostwarden-fleet-read`, per `rules/overrides.md`. An operations host (`references/operations-host.md`) — an always-on machine that runs Hostwarden without anyone at the keyboard — reaches each host with one key of its own, and its fleet run (`bin/hostwarden-fleet-run`) uses nothing else. On the host, that key is forced to `fleet-read`, a wrapper that accepts exactly two requests: - **collect** — run a bundle of read-only checks, but only one the operator signed for the namespace `fleet-read` and whose `# valid-until:` date has not passed; - **log** — write one line to the journal, under the tag `hostwarden` and a prefix the wrapper sets: `[<name> as root] read-only: <line>`. Nothing else runs: no shell, no other command. Whoever takes the operations host over can replay a signed bundle until its date and write read-only journal lines, and that is all. The signature is the operator's approval of every command in the bundle, and the signing key never lies on the operations host. ## What stays with the operator Hostwarden never does these, whatever mode the session runs in: - **Making the operations host's key** and adding its line to root's `authorized_keys` on each host. The taboo guard blocks both, and `AGENTS.md` → Critical Safety Rules forbids them anyway; the session writes out the line for the operator. - **The signing key.** It is the operator's, kept where they keep keys t