enforce-rules-format

Validate that every rule in the project's instruction files has a proper enforcement classification, and fix any that are missing. ## Instructions ### Step 1: Detect Format Check which format the project uses: **v2 (spec-based):** Look for `CLAUDE.md.spec.ts` or any `*.spec.ts` files. If found, this is a v2 project — rules must use `enforce()`, `check()`, or `guidance()`. **v1 (hand-written):** Look for `CLAUDE.md`, `AGENTS.md`, `.cursorrules`. If found without a spec file, this is a v1 project — rules need `**Enforced by:**` or `**Guidance only**` annotations. ### Step 2: Validate **For v2 specs:** The TypeScript type system already prevents unannotated rules — you can't create a rule without calling `enforce()`, `check()`, or `guidance()`. So focus on: 1. Do `enforce()` rules reference real linter rules? Run `npx vigiles compile` to check. 2. Are there guidance rules that COULD be `enforce()`? Check linter configs for matching rules. 3. Are there `check()` assertions that could be delegated to a linter? Suggest `enforce()` instead. ```bash npx vigiles compile npx vigiles discover ``` **For v1 hand-written files:** Scan for `###` headings. Each must have one of: - `**Enforced by:** \`linter/rule-name\`` - `**Guidance only** — reason` - `<!-- vigiles-disable -->` Report missing annotations with a summary table. ### Step 3: Fix Issues For each issue found: 1. Check the project's linter configuration for matching rules 2. Suggest `enforce("linter/rule")` (v2) o...