preflight

# preflight ## Purpose <HARD-GATE> Preflight verdict of BLOCK stops the pipeline. The calling skill (cook, deploy, launch) MUST halt until all BLOCK findings are resolved and preflight re-runs clean. </HARD-GATE> Pre-commit quality gate that catches "almost right" code — the kind that compiles and passes linting but has logic errors, missing error handling, or incomplete implementations. Goes beyond static analysis to check data flow, edge cases, async correctness, and regression impact. The last defense before code enters the repository. ## Triggers - Called automatically by `cook` before commit phase - Called by `fix` after applying fixes (verify fix quality) - `/rune preflight` — manual quality check - Auto-trigger: when staged changes exceed 100 LOC ## Calls (outbound) - `scout` (L2): find code affected by changes (dependency tracing) - `sentinel` (L2): security sub-check on changed files - `hallucination-guard` (L3): verify imports and API references exist - `test` (L2): run test suite as pre-commit check ## Called By (inbound) - `cook` (L1): before commit phase — mandatory gate ## Check Categories ``` LOGIC — data flow errors, edge case misses, async bugs ERROR — missing try/catch, bare catches, unhelpful error messages REGRESSION — untested impact zones, breaking changes to public API COMPLETE — missing validation, missing loading states, missing tests SECURITY — delegated to sentinel IMPORTS — delegated to hallucination-guard ``` ## ...