integrity-check

# integrity-check ## Purpose Post-load and pre-merge validation that detects adversarial content in persisted state files, skill outputs, and context bus data. Complements hallucination-guard (which validates AI-generated code references) by focusing on the AGENT LAYER — prompt injection in `.rune/` files, poisoned cook reports from worktree agents, and tampered context between skill invocations. Based on "Agents of Chaos" (arXiv:2602.20021) threat model: agents that read persisted state are vulnerable to indirect prompt injection, memory poisoning, and identity spoofing. ## Triggers - Called by `sentinel` during Step 4.7 (Agentic Security Scan) - Called by `team` before merging cook reports (Phase 3a) - Called by `session-bridge` on load mode (Step 1.5) - `/rune integrity` — manual integrity scan of `.rune/` directory - Signal: `quarantine.notice.emitted` (from `rune:quarantine`) — bias toward stricter scanning of any state file that incorporated quarantined external content ## Calls (outbound) None — pure validation (read-only scanning). ## Called By (inbound) - `sentinel` (L2): agentic security phase in commit pipeline - `team` (L1): verify cook report integrity before merge - `session-bridge` (L3): verify `.rune/` files on load (L3→L3 exception, documented — same pattern as hallucination-guard → research) ## Execution ### Step 1 — Detect scan targets Determine what to scan based on caller context: - If called by `sentinel`: scan all `.rune/*.md` files + any...