rule-script-reconcilerlisted

## What It Does Detects every form of rules-as-scripts drift and writes `.paqad/scripts/rules/.cache/drift.json`: | Code | Meaning | | ------------------ | ---------------------------------------------------------------------------------------------------------------- | | `RS-RULE-ADDED` | A markdown bullet without a `<!-- @rule -->` marker, or a marked rule absent from the map — an ungated addition. | | `RS-RULE-EDITED` | Marker present, but the text hash differs from the map entry. | | `RS-RULE-REMOVED` | A map entry whose marker is gone from the markdown. | | `RS-SCRIPT-STALE` | A rule was edited but its scripts were not regenerated. | | `RS-FIXTURE-FAIL` | A registered script no longer passes its own fixtures. | | `RS-CACHE-INVALID` | The findings report exists but its `rule_files_hash` no longer reconciles. | Any code except `RS-CACHE-INVALID` blocks `feature-development` per the project's `escalation.rule_scripts_stale` setting. ## Use This When - At `feature-development` planning entry (the planning stage instructions invoke it). - During `analyze rules`, to confirm the map is in