guard

# procoder:guard Rules the agent enforces are a habit. Rules CI enforces are a guarantee. This installs the second. ## Procedure 1. **Detect what already exists.** Never add a second mechanism beside a working one. | Look for | If present | |---|---| | `.pre-commit-config.yaml` | add a `local` repo hook entry; do not write `.git/hooks/pre-commit` | | `.husky/` | append the procoder line to `.husky/pre-commit` | | `lefthook.yml` / `lefthook.yaml` | add a `pre-commit.commands.procoder` entry | | `.git/hooks/pre-commit` (bare, no manager) | append to it; never overwrite it | | none of the above | write `.git/hooks/pre-commit` from the template, `chmod +x` | | `.github/workflows/` | write `.github/workflows/procoder.yml` | | `.gitlab-ci.yml`, `.circleci/`, `azure-pipelines.yml` | translate the CI template's two steps into that provider's syntax | 2. **Check the starting position, before writing anything.** Run `node <plugin>/bin/procoder.js check .`. If no `.procoder-baseline.json` exists and the count exceeds ~50, say so plainly and offer `node <plugin>/bin/procoder.js baseline .` first — a guard that fails on its first run gets removed the same day. Ask before writing the baseline. 3. **Name every file, then wait.** List each file you will create or modify, one line each, with create-or-modify marked. Ask for confirmation and do not write until you get a yes. This step is not optional and not skippable, no matter how routine...