Docker Volume Guardrails

Sets up a PreToolUse hook that unconditionally blocks any Docker command that permanently deletes one or more volumes.

Why unconditional, with no override

This repo's own global instructions already say: "never delete volumes without explicit human confirmation." A hook only ever sees the raw command string handed to it - it has no way to observe whether a human actually confirmed this specific deletion earlier in the conversation. The only mechanical enforcement that is actually faithful to that rule is to never let the agent run this class of command at all - exactly matching git-guardrails-claude-code's own precedent for force-push and reset --hard. If a human has genuinely decided to delete a volume, they run that command themselves, outside the agent.