proof-zk-recovery

Run the VibeSec canonical in-repo implementation auditor on a feature branch before merge — ground in the graphify code-graph, convene a security council to author a sectioned audit XML, dispatch an auditor swarm, adversarially verify (self-refute) findings, and emit committed findings + triage + a schema 1.2 machine-readable gate report. Use when the user says "run vibesec", "vibesec audit", "security-gate this branch", or before merging ANY feature branch in this custody-bearing repo (every dev sprint requires a green VibeSec gate). The gate is enforced in CI (.github/workflows/vibesec.yml).

Run the per-phase Lean review-council QA gate on the lean-spec-enhancement work — a tool-executing council of four expert lenses (axiom-hygiene guardian, spec<->code fidelity, proof nonvacuity, adversarial red-team) that build the proofs, run

Property-based spec<->code conformance for this repo — regenerate Lean-emitted vectors (lake exe vectorgen), replay them against Recovery.Logic with the Haskell tasty-hedgehog suite, and run the mutation sweep (each single-guard mutation must fail at least one vector). Use when validating that the Lean spec still verifies the Haskell implementation, or when the review council's fidelity/adversarial lenses need conformance evidence.

Interactive Lean 4 proof development for this repo — the sorrify-then-fill loop driven over lean-lsp-mcp (goal state, diagnostics, Loogle search), with Duper/lean-auto escalation and a hard