karvey-guardlisted

# Karvey Guard ## Purpose A **cross-cutting support layer** of the Karvey Method — NOT a pipeline phase: **it does NOT change `spec.json:phase`**. It switches the enforcement hooks the plugin ships, which block deterministically (`PreToolUse`), and runs the verification checklist. The canonical rule is `../karvey/rules/enforcement.md`; the flags live in `project.json:enforcement` (`../karvey/rules/project-config.md`). The hooks are registered by the plugin itself (`${CLAUDE_PLUGIN_ROOT}/hooks/hooks.json`). Nothing is copied into the project and `settings.json` is never edited: a guard is on or off by its flag. | Flag | Default | Guard | |---|---|---| | `enforcement.prod_gate_hook` | on | a merge to production needs a recorded human prod approval | | `enforcement.git_flow_hook` | off (opt-in) | no commit on integration/production, no direct push to production, no manual deploy | | `enforcement.plan_gate_hook` | off (opt-in) | edits and destructive commands need an approval marker (`plan_marker_ttl_min`) | **Approval comes only from the human's message.** The approval hook records the marker when the human types it; this skill never creates, touches or extends a marker, and has no override. ## Execution steps Read `../karvey/rules/enforcement.md` first. Resolve the mode from `$ARGUMENTS`. With no argument, show the current state (`karvey-context.py --section enforcement`) and offer the options. ### `--install` / `--disable-hooks` — switch the guards 1. `docs/spec/proje