Repository navigation
Description
Part 3 of 3 of #16752. Refs #15703.
Problem
The mutation-testing principles pages and README illustrate neutral theory with one tool's catalog, vocabulary, flags or a one-language example, and link single tools' documentation as sources.
Rows (8: all R11)
| Row | Rule | Kind | Cited at (as of 5b66a7f) | Fact |
|---|---|---|---|---|
| F0291 | R11 | K4 | plugins/mutation-testing/skills/principles/reference/operators-and-states.md:49-67 |
PIT's default operator catalog |
| F0292 | R11 | K7 | .../principles/reference/operators-and-states.md:81-84 |
SBR note citing lib/hook-utils.test.sh |
| F0293 | R11 | K4 | .../principles/reference/metrics.md:45-59 |
four-names table (Stryker, PIT, Infection vocabulary) |
| F0294 | R11 | K7 | .../principles/reference/metrics.md:95-100 |
src/pricing.ts in the reporting-shape sample |
| F0295 | R11 | K5 | .../principles/reference/scaling-and-suppression.md:23-36 |
per-tool diff-scoping pointers (Stryker.NET since, StrykerJS --incremental, Infection, PIT) |
| F0296 | R11 | K7 | .../principles/reference/scaling-and-suppression.md:132-136 |
Stryker thresholds.break quote |
| F0297 | R11 | K7 | .../principles/reference/theory.md:46-50 |
Python range loop equivalent-mutant example |
| F0301 | R11 | K5 | plugins/mutation-testing/README.md:59-61, 119-136 |
README Sources links to Stryker, Stryker.NET, StrykerJS, PIT, Infection docs (README:61 dotnet test per project alone is R6 and may stay) |
Files
- Cut:
plugins/mutation-testing/skills/principles/reference/{operators-and-states,metrics,scaling-and-suppression,theory}.md,plugins/mutation-testing/README.md. - Outside references at d46efa9:
scripts/docs-anchor-baseline.txt:86(metrics.md),:87(operators-and-states.md),:88(scaling-and-suppression.md);.performance/ratchets.json:183(theory.md ceiling 1);scripts/em-dash-purged-paths.txt:360(README; stale only if the file is deleted).
Rules this part follows (from #16752, rules revision 5)
- R11 (shipped knowledge): model-read K2, K3, K4, K5 or K7 text. Generic text replaces it only at a routing site where the skill still takes a language-specific step; anywhere else it is deleted with no replacement. An item kept only because a removed item consumes it goes in the same pull request.
- R4 (consumer default): the value picks a tool or library for the consumer. It goes: no bundled default survives (ADR 0101 decision 2, "Ship no bundled default"); the choice is resolved from the consumer through
docs/contracts/ecosystem-resolution/. - R8 (measured fact): cut it like the other rows and mark it in the pull request body as pending its targeted case; the host session's eval (below) decides whether it comes back, annotated
portability-ok: measured <case-id>. - AC1's named exceptions are the kept classes of ADR 0101 (
docs/adr/0101-resolve-ecosystem-specifics-from-the-consumer-repository.md, Decision and the 2026-11-17 amendment). Bundled defaults that pick a tool, command or library are retired wherever they appear (Interview Q32, D4 of the Brief). - Line numbers below were read at
5b66a7faand may have moved; find each row by its cited text.
After the pull request opens (host session, not the lane)
The lane opens the pull request with Closes this issue and stops; it adds no label. The pull request stays held for the eval:
- Hold line: a sweep or host session adds
do-not-mergeand posts, from a listed human's account, a comment with<!-- pr-hold reason=eval -->on a line of its own. - Targeted case per changed skill: one before-and-after case on
sonnetat 3 runs a side,--case,--runs 3, a--max-cost-usdceiling;opusonly to confirm a sonnet loss; a new case gets a 1 to 3 run smoke first; start no batch after a usage-limit error (owner decision of 2026-11-16). - Controls: the owner's Q53 decision of 2026-11-17 (owner-decisions.md L202) reads: "each cut pull request is gated on a no-loss compare alone, with no wrong-text side". It supersedes Cut the model-read ecosystem specifics from mutation-testing, starting with its per-tool tables #16752's Controls line and its AC7 sentence ("each partial cut carries a detection-control result"). A whole-page deletion still states its predicted outcome in the pull request body before the first batch, and the record says the case cannot detect wrong text.
- On a LOSS reading: a trace read of each dropped case and an
opusconfirm; only a loss traced to the changed text counts. - R8 rows: the row's targeted case with and without it; on a
case dropor a mean fall of 0.15 or more without it, restore the row annotatedportability-ok: measured <case-id>; a deterministic grader states before the run in how many of n runs it must fail. - Record: on a VALID no-loss run, post from a listed human's account
<!-- eval-pair verdict=no-loss validity=VALID head=<40-hex head SHA> -->naming the current head, with no "do not merge" text (docs/contracts/loop-lane/README.md, "Cross-lane PR hold"). pr-merge's "Release eval holds whose record matches the head" step (.github/scripts/pr-merge/release-eval-hold.mjs) then removesdo-not-merge; a later push needs a new record.
Out of scope
Rows outside this part's table, the parent's kept rows, every other plugin, toolchain's bundled defaults (#15733), and widening the portability gate (#15732).
Done when
- Every row in this part's table is cut or replaced at a routing site; a row whose cited text is already gone on
mainis listed as GONE. - The pull request body states this part's row count (8) and lists every row id with its rule and outcome.
- Each R11 row's script-reader search is quoted in the pull request body; a row whose file a script reads is not cut, and is listed in the pull request body under a
Script readersheading. - The pull request body names, for the principles skill, the existing eval case that reads the cut text, or says none does.
- The pull request body says, for each changed file, whether the cut deletes the whole page or part of it.
- The
skill-stack-fencesceiling forplugins/mutation-testing/skills/principles/reference/theory.mdin.performance/ratchets.jsonis lowered if the cut removes its fence, andscripts/docs-anchor-baseline.txt:86-88match the remaining anchors. - AC10: no new enforcement-placing skill is added.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Work status
needs-triage
Priority
medium
Activity
github-actions commentedon Nov 21, 2026
Size: Medium
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: five mutation-testing docs (four principles reference pages and the README), plus the docs-anchor baseline and the theory.md ratchet ceiling. Model-read skill text changes, so it affects anyone running the principles skill.
Reversible: yes; revert the pull request. Any R8 row that the eval shows to be a loss is restored with a
portability-okannotation.Open questions: none
I read this as part 3 of 3 of #16752: cut or replace the 8 listed R11 rows (F0291 to F0297 and F0301) under the stated rules, and fix the baseline and ratchet entries that depend on them. The done-when list is exact. The eval gate runs in a host session after the pull request opens, so it doesn't hold this issue. The two sibling parts, #15703's other mutation-testing issues (the audit skill, and setup and the tooling page), cover different files, so I don't treat them as duplicates. No merged pull request already fixes this.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 21, 2026
{"v":1,"actor_id":337595936,"title_sha256":"8a13511f2cac1daf164664d95eee4059cbe2ae5a4b528a5ca95bc968a6fc272e","body_sha256":"0654a1b2755d9302107625ab7ae1438cce655ecd9e299dc9ae360487267dca0e"}
github-actions commentedon Nov 21, 2026
github-actions commentedon Nov 21, 2026
docs(mutation-testing): cut single-tool examples from principles refe…