[Change] Zero-finding code review — dogfooding specfact review on specfact-cli

[djm81]

Why

SpecFact CLI's specfact review flow must prove the repo can pass its own quality gates before downstream clean-code enforcement becomes credible.

What Changes

• Fix the zero-finding backlog across type-check, logging, contracts, complexity, and tooling.
• Keep the CI review gate blocking once the repo reaches overall_verdict: PASS.
• Add a final self-compliance phase for the expanded clean-code categories (naming, kiss, yagni, dry, solid) so this issue remains the prerequisite for clean-code-01-principle-gates.

OpenSpec Change Proposal: code-review-zero-findings