rule-analyzerlisted

## What It Does Turns prose rules into a reviewable contract. For every bullet under `docs/instructions/rules/**` it: - Embeds an opaque, stable `<!-- @rule RL-<hash> -->` marker (idempotent — reruns cause no churn). - Classifies verifiability: - `deterministic` — a script can decide pass/fail (e.g. "no debugger statements"). - `heuristic` — a script can flag candidates; humans/LLM adjudicate (e.g. "business logic belongs in hooks"). - `unverifiable` — with a reason (e.g. "coherence is judgment-dependent"). - Records pre-existing enforcers in `enforced_by` so no duplicate script is generated. - Detects contradictory rules and surfaces them via the Decision Pause Contract before any script work. It writes a draft `docs/instructions/rules/rule-script-map.yml`. **The user reviews this map before `generate rule scripts`.** ## Use This When - A user prompt matches the priority-225 router rule `analyze rules`. - After adding or editing several rules and you need to re-classify the rule set. - Before `generate rule scripts` on a fresh project — generation reads this map. ## Inputs - All markdown rule files under `docs/instructions/rules/**` (the `.yml` registries are not prose rules and are skipped). - The project's existing enforcers, read to populate `enforced_by`: `eslint.config.js` / `.eslintrc.*`, `tsconfig.json` strictness flags, Prettier config, and existing paqad infra (`module-health`, `design-test`, `pentest`). - The prior `rule-script-map.yml` if present (scr