constraint-check

# constraint-check ## Purpose The internal affairs department for Rune skills. Checks whether HARD-GATEs and mandatory constraints were actually followed during a workflow — not just claimed to be followed. Reads the constraint definitions from skill files and audits the conversation trail for compliance. While `completion-gate` checks if claims have evidence, `constraint-check` checks if the PROCESS was followed. Did you actually write tests before code? Did you actually get plan approval? Did you actually run sentinel? ## Triggers - Called by `cook` (L1) at end of workflow as discipline audit - Called by `team` (L1) to verify stream agents followed constraints - Called by `audit` (L2) during quality dimension assessment - `/rune constraint-check` — manual audit of current session ## Calls (outbound) None — pure read-only validator. ## Called By (inbound) - `cook` (L1): end-of-workflow discipline audit - `team` (L1): verify stream agent compliance - `audit` (L2): quality dimension - User: manual session audit ## Execution ### Step 1 — Identify Active Skills Parse the conversation/workflow to identify which skills were invoked: ``` Extract from context: - Skills invoked via Skill tool (exact list) - Skills referenced in agent narrative - Phase progression (cook phases completed) ``` ### Step 2 — Load Constraint Definitions For each invoked skill, extract HARD-GATEs and numbered constraints: ``` For each skill in invoked_skills: Read: skills/<skill>/SKI...