dsh-safety-net

When a DSH agent runs autonomously, a single misdirected write can silently overwrite profile manifests, session state, or plugin data under ~/.dsh and leave the entire harness unstartable. dsh-safety-net makes that outcome impossible by default: waterfall listeners on fs/write-intent and fs/edit-intent hard-block any mutation targeting DSH critical paths and raise a FS_POLICY_DENIED error that the agent cannot work around by retrying.

Before every refused mutation, the original file is snapshotted into a local backup store, so the worst-case scenario is one restore command away from being undone. Five /safety-net-* slash commands—status, backup, restore, repair, and approve—form a CLI recovery channel that keeps working even after the GUI has gone down, letting you list backups, restore individual snapshots by id, get step-by-step repair instructions, or grant a one-time write bypass to a protected path. Strict mode is on by default, declaring a read-only sandbox baseline and warning when the host sandbox default is wider than necessary.

If you run autonomous agents on DSH and want a guardrail that stays invisible during normal operation but catches the harness before a single bad edit becomes an unrecoverable outage, this plugin is that seatbelt: silent until you need it, and one command away from undoing the damage when you do.