completion-gate

# completion-gate ## Purpose The lie detector for agent claims. Validates that what an agent says it did actually happened — with evidence. Catches the #1 failure mode in AI coding: claiming completion without proof. <HARD-GATE> Every claim requires evidence. No evidence = UNCONFIRMED = BLOCK. "I ran the tests and they pass" without stdout = UNCONFIRMED. "I fixed the bug" without before/after diff = UNCONFIRMED. "Build succeeds" without build output = UNCONFIRMED. </HARD-GATE> ## Triggers - Called by `cook` in Phase 5d (quality gate) - Called by `team` before merging stream results - Called by any skill that reports "done" to an orchestrator - Auto-trigger: when agent says "done", "complete", "fixed", "passing" ## Calls (outbound) None — pure validator. Reads evidence, produces verdict. ## Called By (inbound) - `cook` (L1): Phase 5d — validate completion claims before commit - `team` (L1): validate cook reports from parallel streams ## Execution ### Step 1 — Collect Claims Parse the agent's output for completion claims. Common claim patterns: ``` CLAIM PATTERNS: "tests pass" / "all tests passing" / "test suite green" "build succeeds" / "build complete" / "compiles clean" "no lint errors" / "lint clean" "fixed" / "resolved" / "bug is gone" "implemented" / "feature complete" / "done" "no security issues" / "sentinel passed" ``` Extract each claim as: `{ claim: string, source_skill: string }` ### Step 1a — Type Each Claim (Claim Discipline) <MUST-READ ...