konjo-retrofit

# Konjo Retrofit — Existing Repo Quality Migration ## The Problem With Retrofitting Blind Installing hard quality gates on an existing codebase without measuring first causes one of two outcomes: 1. **Gates fail on day 1** — blocks all work, team disables the gates in frustration 2. **Gates are set too loose** — they pass everything, provide no value The Retrofit Protocol solves this by measuring before gating, then ratcheting up incrementally. --- ## Step 1 — Baseline Audit (measure everything, fix nothing yet) Run these and save the output. Do not fix violations yet — just establish the baseline. ```bash # Coverage baseline cargo llvm-cov nextest --workspace --json > coverage_baseline.json # Rust python -m pytest --cov --cov-report=json > coverage_baseline.json # Python # Lint baseline cargo clippy --workspace --all-targets --message-format json > clippy_baseline.json # Rust ruff check --output-format json > ruff_baseline.json # Python # Dead code RUSTFLAGS="-W dead_code" cargo check --workspace 2>&1 | grep "dead_code" > dead_code.txt # Rust vulture . --min-confidence 60 > vulture_baseline.txt # Python # Complexity radon cc . -n C > complexity_baseline.txt # Python (grade C = cyclomatic > 10) # For Rust: cargo clippy -W clippy::cognitive_complexity 2>&1 | grep "cognitive_complexity" # DRY python3 .konjo/scripts/dry_check.py --json > dry_baseline.json # File sizes find . -name...