releaselisted

# Release Release a new version of cqs. ## Arguments - `$ARGUMENTS` — version bump type: `major`, `minor`, or `patch` (default: `patch`) ## Process 1. **Pre-flight checks**: - `git status` — must be clean (no uncommitted changes) - `gh pr list --state open` (via PowerShell) — review any open PRs. Merge or close before releasing. - `cargo test --features cuda-index` — all tests must pass (full suite is correct here; this is the one place it runs deliberately) - `cargo clippy --all-targets --features cuda-index -- -D warnings` — no warnings (CI runs `--all-targets`) - Confirm on `main` branch 2. **Recall gate (REQUIRED before tagging)**: - Run BOTH fixtures against the current index: ```bash cqs eval evals/queries/v3_test.v2.json --json cqs eval evals/queries/v3_dev.v2.json --json ``` - Compare R@1/R@5/R@20 against the previous release's snapshot (README TL;DR line / RESULTS log). - **If numbers dropped**: check for dead gold origins FIRST — the matcher is `(origin, name)`, so file splits/renames since the last release kill gold origins and cap R@K, masquerading as a recall regression. Line-number drift alone is harmless. - The definitive regression test is a same-corpus binary A/B: run the previous release binary and the new one against the SAME index and diff the reports. Only a regression confirmed by the A/B blocks the release. 3. **Version bump**: - Read current version from `Cargo.toml` - Calculate new version ba