@rune-kit/rune 2.10.0 → 2.11.0

package/skills/browser-pilot/SKILL.md

@@ -1,168 +1,168 @@
----
-name: browser-pilot
-description: Playwright browser automation. Navigates URLs, takes screenshots, checks accessibility tree, interacts with UI elements, and reports findings.
-metadata:
-  author: runedev
-  version: "0.2.0"
-  layer: L3
-  model: sonnet
-  group: media
-  tools: "Read, Bash, Glob, Grep"
----
-
-# browser-pilot
-
-## Purpose
-
-Browser automation for testing and verification using MCP Playwright tools. Navigates to URLs, captures accessibility snapshots and screenshots, interacts with UI elements (click, type, fill form), and reports findings with visual evidence.
-
-## Called By (inbound)
-
-- `test` (L2): e2e and visual testing
-- `deploy` (L2): verify live deployment
-- `debug` (L2): capture browser console errors
-- `marketing` (L2): screenshot for assets
-- `launch` (L1): verify live site after deployment
-- `perf` (L2): Lighthouse / Core Web Vitals measurement
-
-## Calls (outbound)
-
-None — pure L3 utility using Playwright MCP tools.
-
-## Executable Instructions
-
-### Step 1: Receive Task
-
-Accept input from calling skill:
-- `url` — target URL to open
-- `task` — what to do: `screenshot` | `check_elements` | `fill_form` | `test_flow` | `console_errors`
-- `interactions` — optional list of actions (click X, type Y into Z, etc.)
-
-### Step 2: Navigate
-
-Open the target URL using the Playwright MCP navigate tool:
-
-```
-mcp__plugin_playwright_playwright__browser_navigate({ url: "<url>" })
-```
-
-Wait for the page to load. If navigation fails (timeout or error), report UNREACHABLE and stop.
-
-### Step 3: Snapshot
-
-Capture the accessibility tree to understand page structure:
-
-```
-mcp__plugin_playwright_playwright__browser_snapshot()
-```
-
-Use the snapshot to:
-- Identify interactive elements (buttons, inputs, links)
-- Find specific elements referenced in the task
-- Detect accessibility issues (missing labels, roles)
-
-### Step 4: Interact
-
-Based on the task, perform interactions using Playwright MCP tools:
-
-- **Click**: `mcp__plugin_playwright_playwright__browser_click({ ref: "<ref>", element: "<description>" })`
-- **Type**: `mcp__plugin_playwright_playwright__browser_type({ ref: "<ref>", text: "<value>" })`
-- **Fill form**: `mcp__plugin_playwright_playwright__browser_fill_form({ fields: [...] })`
-- **Navigate back**: `mcp__plugin_playwright_playwright__browser_navigate_back()`
-- **Select option**: `mcp__plugin_playwright_playwright__browser_select_option({ ref: "<ref>", values: [...] })`
-
-Limit: max 20 interactions per session. If the task requires more, stop and report partial results.
-
-After each interaction, take a new snapshot to verify the result before proceeding.
-
-### Step 5: Screenshot
-
-Capture visual evidence:
-
-```
-mcp__plugin_playwright_playwright__browser_take_screenshot({ type: "png" })
-```
-
-For full-page capture (landing pages, long content):
-
-```
-mcp__plugin_playwright_playwright__browser_take_screenshot({ type: "png", fullPage: true })
-```
-
-Save with a descriptive filename if the `filename` param is supported.
-
-### Step 6: Report
-
-Compile findings into a structured report:
-
-```
-## Browser Report: [url]
-
-- **Task**: [task description]
-- **Status**: SUCCESS | PARTIAL | FAILED
-
-### Page Info
-- HTTP Status: [status]
-- Load outcome: [loaded | timeout | error]
-
-### Accessibility Findings
-- [finding from snapshot — missing labels, broken roles, etc.]
-
-### Interaction Log
-- [action taken] → [result: success | element not found | error]
-
-### Console Errors
-- [error message — source]
-
-### Screenshots
-- [screenshot path or description]
-
-### Summary
-- [overall assessment — what works, what failed, any critical issues]
-```
-
-### Step 7: Close
-
-Always close the browser when done:
-
-```
-mcp__plugin_playwright_playwright__browser_close()
-```
-
-This step is mandatory even if earlier steps fail. Use a try-finally pattern in your reasoning.
-
-## Output Format
-
-Structured Browser Report with task status, page info, accessibility findings, interaction log, console errors, screenshots, and summary. See Step 6 Report above for full template.
-
-## Constraints
-
-1. MUST close browser when done — Step 7 is non-optional even if earlier steps fail
-2. MUST NOT exceed 20 interactions per session
-3. MUST NOT store credentials or sensitive data in interaction logs
-4. MUST take screenshot evidence before reporting visual findings
-
-## Sharp Edges
-
-Known failure modes for this skill. Check these before declaring done.
-
-| Failure Mode | Severity | Mitigation |
-|---|---|---|
-| Not closing browser when done (including on error) | CRITICAL | Constraint 1: Step 7 browser_close() is mandatory — treat as try-finally |
-| Storing credentials or tokens in interaction logs | HIGH | Constraint 3: redact all sensitive values before logging |
-| Exceeding 20 interactions without stopping and reporting partial | MEDIUM | Constraint 2: stop at 20, report what was tested and what remains |
-| Reporting visual findings without screenshot evidence | MEDIUM | Constraint 4: screenshot before reporting — "looks broken" without screenshot is invalid |
-
-## Done When
-
-- URL navigated successfully (or UNREACHABLE reported)
-- Page snapshot captured for accessibility context
-- All requested interactions completed (or partial with reason if >20)
-- Screenshot taken as visual evidence
-- Console errors captured if task requested them
-- Browser closed (Step 7 executed)
-- Browser Report emitted with status, findings, and screenshot reference
-
-## Cost Profile
-
-~500-1500 tokens input, ~300-800 tokens output. Sonnet for interaction logic.
+---
+name: browser-pilot
+description: Playwright browser automation. Navigates URLs, takes screenshots, checks accessibility tree, interacts with UI elements, and reports findings.
+metadata:
+  author: runedev
+  version: "0.2.0"
+  layer: L3
+  model: sonnet
+  group: media
+  tools: "Read, Bash, Glob, Grep"
+---
+
+# browser-pilot
+
+## Purpose
+
+Browser automation for testing and verification using MCP Playwright tools. Navigates to URLs, captures accessibility snapshots and screenshots, interacts with UI elements (click, type, fill form), and reports findings with visual evidence.
+
+## Called By (inbound)
+
+- `test` (L2): e2e and visual testing
+- `deploy` (L2): verify live deployment
+- `debug` (L2): capture browser console errors
+- `marketing` (L2): screenshot for assets
+- `launch` (L1): verify live site after deployment
+- `perf` (L2): Lighthouse / Core Web Vitals measurement
+
+## Calls (outbound)
+
+None — pure L3 utility using Playwright MCP tools.
+
+## Executable Instructions
+
+### Step 1: Receive Task
+
+Accept input from calling skill:
+- `url` — target URL to open
+- `task` — what to do: `screenshot` | `check_elements` | `fill_form` | `test_flow` | `console_errors`
+- `interactions` — optional list of actions (click X, type Y into Z, etc.)
+
+### Step 2: Navigate
+
+Open the target URL using the Playwright MCP navigate tool:
+
+```
+mcp__plugin_playwright_playwright__browser_navigate({ url: "<url>" })
+```
+
+Wait for the page to load. If navigation fails (timeout or error), report UNREACHABLE and stop.
+
+### Step 3: Snapshot
+
+Capture the accessibility tree to understand page structure:
+
+```
+mcp__plugin_playwright_playwright__browser_snapshot()
+```
+
+Use the snapshot to:
+- Identify interactive elements (buttons, inputs, links)
+- Find specific elements referenced in the task
+- Detect accessibility issues (missing labels, roles)
+
+### Step 4: Interact
+
+Based on the task, perform interactions using Playwright MCP tools:
+
+- **Click**: `mcp__plugin_playwright_playwright__browser_click({ ref: "<ref>", element: "<description>" })`
+- **Type**: `mcp__plugin_playwright_playwright__browser_type({ ref: "<ref>", text: "<value>" })`
+- **Fill form**: `mcp__plugin_playwright_playwright__browser_fill_form({ fields: [...] })`
+- **Navigate back**: `mcp__plugin_playwright_playwright__browser_navigate_back()`
+- **Select option**: `mcp__plugin_playwright_playwright__browser_select_option({ ref: "<ref>", values: [...] })`
+
+Limit: max 20 interactions per session. If the task requires more, stop and report partial results.
+
+After each interaction, take a new snapshot to verify the result before proceeding.
+
+### Step 5: Screenshot
+
+Capture visual evidence:
+
+```
+mcp__plugin_playwright_playwright__browser_take_screenshot({ type: "png" })
+```
+
+For full-page capture (landing pages, long content):
+
+```
+mcp__plugin_playwright_playwright__browser_take_screenshot({ type: "png", fullPage: true })
+```
+
+Save with a descriptive filename if the `filename` param is supported.
+
+### Step 6: Report
+
+Compile findings into a structured report:
+
+```
+## Browser Report: [url]
+
+- **Task**: [task description]
+- **Status**: SUCCESS | PARTIAL | FAILED
+
+### Page Info
+- HTTP Status: [status]
+- Load outcome: [loaded | timeout | error]
+
+### Accessibility Findings
+- [finding from snapshot — missing labels, broken roles, etc.]
+
+### Interaction Log
+- [action taken] → [result: success | element not found | error]
+
+### Console Errors
+- [error message — source]
+
+### Screenshots
+- [screenshot path or description]
+
+### Summary
+- [overall assessment — what works, what failed, any critical issues]
+```
+
+### Step 7: Close
+
+Always close the browser when done:
+
+```
+mcp__plugin_playwright_playwright__browser_close()
+```
+
+This step is mandatory even if earlier steps fail. Use a try-finally pattern in your reasoning.
+
+## Output Format
+
+Structured Browser Report with task status, page info, accessibility findings, interaction log, console errors, screenshots, and summary. See Step 6 Report above for full template.
+
+## Constraints
+
+1. MUST close browser when done — Step 7 is non-optional even if earlier steps fail
+2. MUST NOT exceed 20 interactions per session
+3. MUST NOT store credentials or sensitive data in interaction logs
+4. MUST take screenshot evidence before reporting visual findings
+
+## Sharp Edges
+
+Known failure modes for this skill. Check these before declaring done.
+
+| Failure Mode | Severity | Mitigation |
+|---|---|---|
+| Not closing browser when done (including on error) | CRITICAL | Constraint 1: Step 7 browser_close() is mandatory — treat as try-finally |
+| Storing credentials or tokens in interaction logs | HIGH | Constraint 3: redact all sensitive values before logging |
+| Exceeding 20 interactions without stopping and reporting partial | MEDIUM | Constraint 2: stop at 20, report what was tested and what remains |
+| Reporting visual findings without screenshot evidence | MEDIUM | Constraint 4: screenshot before reporting — "looks broken" without screenshot is invalid |
+
+## Done When
+
+- URL navigated successfully (or UNREACHABLE reported)
+- Page snapshot captured for accessibility context
+- All requested interactions completed (or partial with reason if >20)
+- Screenshot taken as visual evidence
+- Console errors captured if task requested them
+- Browser closed (Step 7 executed)
+- Browser Report emitted with status, findings, and screenshot reference
+
+## Cost Profile
+
+~500-1500 tokens input, ~300-800 tokens output. Sonnet for interaction logic.

package/skills/constraint-check/SKILL.md

@@ -1,165 +1,165 @@
----
-name: constraint-check
-description: "Meta-validator for HARD-GATEs. Verifies that skills' mandatory constraints were followed during a workflow. Called by cook, team, and audit to audit discipline compliance."
-user-invocable: false
-metadata:
-  author: runedev
-  version: "1.1.0"
-  layer: L3
-  model: haiku
-  group: validation
-  tools: "Read, Glob, Grep"
----
-
-# 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>/SKILL.md
-  Extract:
-    - <HARD-GATE> blocks → mandatory, violation = BLOCK
-    - ## Constraints numbered list → required, violation = WARN
-    - ## Mesh Gates table → required gates
-```
-
-### Step 3 — Audit Compliance
-
-Check each constraint against the conversation evidence:
-
-| Constraint Type | How to Verify | Evidence Source |
-|---|---|---|
-| "MUST write tests BEFORE code" | Test file Write/Edit timestamps before implementation Write/Edit | Tool call ordering |
-| "MUST get user approval" | User message containing "go"/"yes"/"proceed" after plan | Conversation history |
-| "MUST run verification" | Bash command with test/lint/build output | Tool call results |
-| "MUST show actual output" | Stdout captured in agent response | Agent messages |
-| "MUST NOT modify files outside scope" | Git diff files vs plan file list | Git + plan comparison |
-| "Iron Law: delete code before test" | No implementation code exists before test creation | Tool call ordering |
-
-### Step 4 — Classify Violations
-
-| Violation Type | Severity | Meaning |
-|---------------|----------|---------|
-| HARD-GATE violation | BLOCK | Skill says this is non-negotiable |
-| Constraint violation | WARN | Skill says this is required but not fatal |
-| Best practice skip | INFO | Recommended but optional |
-
-### Step 5 — Report
-
-```
-## Constraint Check Report
-- **Status**: COMPLIANT | VIOLATIONS_FOUND | CRITICAL_VIOLATION
-- **Skills Audited**: [count]
-- **Constraints Checked**: [count]
-- **Violations**: [count by severity]
-
-### HARD-GATE Violations (BLOCK)
-- [skill:test] Iron Law: implementation code written at tool_call #12 BEFORE test file created at #15
-- [skill:cook] Plan Gate: Phase 4 started without user approval message
-
-### Constraint Violations (WARN)
-- [skill:verification] Constraint 2: "All tests pass" claimed at message #20 without stdout evidence
-- [skill:sentinel] Constraint 3: files scanned list not included in report
-
-### Compliance Summary
-| Skill | HARD-GATEs | Constraints | Status |
-|-------|-----------|-------------|--------|
-| cook | 3/3 ✓ | 6/7 (1 WARN) | WARN |
-| test | 0/1 ✗ | 8/9 (1 WARN) | BLOCK |
-| verification | 1/1 ✓ | 4/6 (2 WARN) | WARN |
-| sentinel | 1/1 ✓ | 7/7 ✓ | PASS |
-
-### Remediation
-- BLOCK: test Iron Law — delete implementation, restart with test-first
-- WARN: verification — re-run and capture stdout
-```
-
-## Constraint Catalog (Quick Reference)
-
-Key HARD-GATEs across skills that constraint-check audits:
-
-| Skill | HARD-GATE | Check Method |
-|---|---|---|
-| test | Tests BEFORE code (Iron Law) | Tool call ordering |
-| cook | Scout before plan, plan before code | Phase progression |
-| plan | Every code phase has test entry | Plan content |
-| verification | Evidence for every claim | Stdout capture |
-| sentinel | BLOCK = halt pipeline | No commit after BLOCK |
-| preflight | BLOCK = halt pipeline | No commit after BLOCK |
-| debug | No code changes during debug | No Write/Edit in debug |
-| debug | 3-fix escalation | Fix attempt counter |
-| brainstorm | No implementation before approval | User message check |
-
-## Output Format
-
-Constraint Check Report with status (COMPLIANT/VIOLATIONS_FOUND/CRITICAL_VIOLATION), HARD-GATE violations, constraint violations, compliance summary table, and remediation steps. See Step 5 Report above for full template.
-
-## Constraints
-
-1. MUST check all HARD-GATEs for every invoked skill — not just the ones that seem relevant
-2. MUST use tool call ordering (not agent narrative) to verify temporal constraints
-3. MUST distinguish HARD-GATE violations (BLOCK) from constraint violations (WARN)
-4. MUST report specific evidence for each violation — not just "violated"
-5. MUST NOT accept agent's self-report as compliance evidence — check independently
-
-## Sharp Edges
-
-| Failure Mode | Severity | Mitigation |
-|---|---|---|
-| Agent self-reports compliance and constraint-check trusts it | CRITICAL | Constraint 5: check tool calls independently, not agent narrative |
-| Only checking cook constraints, missing test/sentinel/etc | HIGH | Constraint 1: audit ALL invoked skills, not just the orchestrator |
-| Temporal check wrong (tool calls reordered in context) | MEDIUM | Use tool call sequence numbers, not message ordering |
-| Too strict on optional steps (INFO treated as BLOCK) | LOW | Step 4 classification: only HARD-GATE = BLOCK, constraints = WARN |
-
-## Done When
-
-- All invoked skills identified from context
-- HARD-GATEs and constraints extracted from each skill's SKILL.md
-- Each constraint checked against conversation evidence
-- Violations classified as BLOCK/WARN/INFO
-- Compliance summary table emitted per skill
-- Remediation steps listed for each violation
-
-## Cost Profile
-
-~1000-2000 tokens input, ~500-1000 tokens output. Haiku for speed — reads skill files and checks tool call ordering.
+---
+name: constraint-check
+description: "Meta-validator for HARD-GATEs. Verifies that skills' mandatory constraints were followed during a workflow. Called by cook, team, and audit to audit discipline compliance."
+user-invocable: false
+metadata:
+  author: runedev
+  version: "1.1.0"
+  layer: L3
+  model: haiku
+  group: validation
+  tools: "Read, Glob, Grep"
+---
+
+# 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>/SKILL.md
+  Extract:
+    - <HARD-GATE> blocks → mandatory, violation = BLOCK
+    - ## Constraints numbered list → required, violation = WARN
+    - ## Mesh Gates table → required gates
+```
+
+### Step 3 — Audit Compliance
+
+Check each constraint against the conversation evidence:
+
+| Constraint Type | How to Verify | Evidence Source |
+|---|---|---|
+| "MUST write tests BEFORE code" | Test file Write/Edit timestamps before implementation Write/Edit | Tool call ordering |
+| "MUST get user approval" | User message containing "go"/"yes"/"proceed" after plan | Conversation history |
+| "MUST run verification" | Bash command with test/lint/build output | Tool call results |
+| "MUST show actual output" | Stdout captured in agent response | Agent messages |
+| "MUST NOT modify files outside scope" | Git diff files vs plan file list | Git + plan comparison |
+| "Iron Law: delete code before test" | No implementation code exists before test creation | Tool call ordering |
+
+### Step 4 — Classify Violations
+
+| Violation Type | Severity | Meaning |
+|---------------|----------|---------|
+| HARD-GATE violation | BLOCK | Skill says this is non-negotiable |
+| Constraint violation | WARN | Skill says this is required but not fatal |
+| Best practice skip | INFO | Recommended but optional |
+
+### Step 5 — Report
+
+```
+## Constraint Check Report
+- **Status**: COMPLIANT | VIOLATIONS_FOUND | CRITICAL_VIOLATION
+- **Skills Audited**: [count]
+- **Constraints Checked**: [count]
+- **Violations**: [count by severity]
+
+### HARD-GATE Violations (BLOCK)
+- [skill:test] Iron Law: implementation code written at tool_call #12 BEFORE test file created at #15
+- [skill:cook] Plan Gate: Phase 4 started without user approval message
+
+### Constraint Violations (WARN)
+- [skill:verification] Constraint 2: "All tests pass" claimed at message #20 without stdout evidence
+- [skill:sentinel] Constraint 3: files scanned list not included in report
+
+### Compliance Summary
+| Skill | HARD-GATEs | Constraints | Status |
+|-------|-----------|-------------|--------|
+| cook | 3/3 ✓ | 6/7 (1 WARN) | WARN |
+| test | 0/1 ✗ | 8/9 (1 WARN) | BLOCK |
+| verification | 1/1 ✓ | 4/6 (2 WARN) | WARN |
+| sentinel | 1/1 ✓ | 7/7 ✓ | PASS |
+
+### Remediation
+- BLOCK: test Iron Law — delete implementation, restart with test-first
+- WARN: verification — re-run and capture stdout
+```
+
+## Constraint Catalog (Quick Reference)
+
+Key HARD-GATEs across skills that constraint-check audits:
+
+| Skill | HARD-GATE | Check Method |
+|---|---|---|
+| test | Tests BEFORE code (Iron Law) | Tool call ordering |
+| cook | Scout before plan, plan before code | Phase progression |
+| plan | Every code phase has test entry | Plan content |
+| verification | Evidence for every claim | Stdout capture |
+| sentinel | BLOCK = halt pipeline | No commit after BLOCK |
+| preflight | BLOCK = halt pipeline | No commit after BLOCK |
+| debug | No code changes during debug | No Write/Edit in debug |
+| debug | 3-fix escalation | Fix attempt counter |
+| brainstorm | No implementation before approval | User message check |
+
+## Output Format
+
+Constraint Check Report with status (COMPLIANT/VIOLATIONS_FOUND/CRITICAL_VIOLATION), HARD-GATE violations, constraint violations, compliance summary table, and remediation steps. See Step 5 Report above for full template.
+
+## Constraints
+
+1. MUST check all HARD-GATEs for every invoked skill — not just the ones that seem relevant
+2. MUST use tool call ordering (not agent narrative) to verify temporal constraints
+3. MUST distinguish HARD-GATE violations (BLOCK) from constraint violations (WARN)
+4. MUST report specific evidence for each violation — not just "violated"
+5. MUST NOT accept agent's self-report as compliance evidence — check independently
+
+## Sharp Edges
+
+| Failure Mode | Severity | Mitigation |
+|---|---|---|
+| Agent self-reports compliance and constraint-check trusts it | CRITICAL | Constraint 5: check tool calls independently, not agent narrative |
+| Only checking cook constraints, missing test/sentinel/etc | HIGH | Constraint 1: audit ALL invoked skills, not just the orchestrator |
+| Temporal check wrong (tool calls reordered in context) | MEDIUM | Use tool call sequence numbers, not message ordering |
+| Too strict on optional steps (INFO treated as BLOCK) | LOW | Step 4 classification: only HARD-GATE = BLOCK, constraints = WARN |
+
+## Done When
+
+- All invoked skills identified from context
+- HARD-GATEs and constraints extracted from each skill's SKILL.md
+- Each constraint checked against conversation evidence
+- Violations classified as BLOCK/WARN/INFO
+- Compliance summary table emitted per skill
+- Remediation steps listed for each violation
+
+## Cost Profile
+
+~1000-2000 tokens input, ~500-1000 tokens output. Haiku for speed — reads skill files and checks tool call ordering.