v1.1.0

Breaking changes

• Verify report schema is now 2. Consumers must read the separate outcomes: pass, findings failure, incomplete analysis, and non-certifying baseline maintenance.
• --update-baseline now exits 1: it is maintenance, not a passing verification.
• --fail-on applies only to dead code that is explicitly opted in; dead code is advisory by default.
• MCP baseline writes require --allow-baseline-update (baseline-write authority is separate from execution).

Changed

• Verify schema 2 separates pass, findings failure, incomplete analysis, and non-certifying baseline maintenance. Required failures and invalid Git bases no longer pass.
• Independent per-check enforcement; dead code is advisory by default. CLI/MCP library mode and policy agree; baseline-write authority is separate from execution.
• Pinned Git baseline mode, atomic maintenance, explicit baseline read errors, preserved unobserved provider entries, complete totals and coverage caveats.
• Provider exit/output failure handling and an offline gate regression corpus.
• Init checks actual Git worktree status rather than any ancestor named .git.
• See migration details before upgrading gate consumers.

Limits (honest)

• No native Windows or macOS validation of 1.1.0; only Linux was verified for this release (see README for what was tested earlier on Windows).
• Trusted verification mode has documented limits: see docs/VERIFY.md. Tier-0 analysis is name-based; a pass covers only the selected checks.
• The attached binary is linux-x64, built locally with cargo build --release --locked (not CI-built). Verify with sha256sum -c SHA256SUMS.txt.