Skip to content

Eliminate mutation testing references from CLAUDE.md #95

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tschm merged 1 commit into from
Aug 21, 2026
Merged

Eliminate mutation testing references from CLAUDE.md #95

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 0 additions & 23 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,29 +51,6 @@ Versions live in `[tool.bumpversion]` and are rewritten across `pyproject.toml`,
`uv.lock` and `CITATION.cff` together — never edit one by hand. `CHANGELOG.md` is
generated by git-cliff from Conventional Commit subjects; do not hand-edit it.

**Mutation testing is gone from this project — do not offer it as an option.**
Three separate things, and all of them are true at once:

- No workflow. `.github/workflows/` has no mutation job; the template's
`rhiza_mutation.yml` is in `exclude:` in `.rhiza/template.yml`.
- No baseline. `docs/development/MUTATION.md` held the survivor table and the
analysis of which mutants are provably equivalent, and has been deleted.
- **`make mutation` does not work.** It is not in the list above for that reason.
The task comes from `rhiza-task` and drives the mutmut **2.x** CLI
(`--paths-to-mutate`, `--tests-dir`, `mutmut html`), all removed in 3.x, with
`mutmut` installed unpinned — [jebel-quant/rhiza#1492](https://github.com/jebel-quant/rhiza/issues/1492).
The override that used to correct this lived in the hand-written `Makefile`
that the rhiza v1.4 migration replaced with the task-runner shim, and it was
not carried into `local.mk`.

So do not suggest running it, do not cite a mutation score, and do not treat
assertion strength as something this repo measures. `[tool.mutmut]` is still in
`pyproject.toml`, so a `uv run --with 'mutmut>=3' mutmut run` reaches a working
mutmut 3 directly if someone genuinely wants a one-off — but that is a decision
to raise with the maintainer, not a gate to run unprompted, and the numbers it
prints mean nothing without the deleted baseline
(`git log --diff-filter=D -- docs/development/MUTATION.md`).

## Architecture

`src/cvx/quadprog/` — public surface is exactly three names (`solve_qp`,
Expand Down