37ae0e1d39
The curator LLM fork was steered by its own prompt to re-home skill support files with terminal `mkdir -p ... && mv ...`. A terminal move writes the same bytes with NO ledger entry, so the archive that follows snapshots an already-stripped package (files: 1) and `hermes curator rollback` restores a hollow skill — SKILL.md back, references/ gone. Remove the capability rather than guard it: the fork's enabled_toolsets drops "terminal", so terminal and process disappear together and there is no shell to parse, no process stdin to feed, no remote-backend divergence — a heuristic command guard over a Turing-complete input space can guarantee none of that. Every mutation the pass needs has a ledgered skill_manage action (write_file / remove_file / delete), and the prompt now steers exactly those. Reading works through skill_view. Tests pin both halves: the call-site kwarg (["skills"] only), the resolved surface (no execution/write tools), and the prompt steering (no mkdir -p / mv shapes).