Repository navigation
Closed
Task
Copy link
Description
Part 1 of 3 of #16752. Refs #15703. Blocks #15732 through #16752.
Problem
mutation-testing's setup skill and its tooling reference pick the consumer's mutation tool and runner from a bundled ecosystem table, which ADR 0101 retires.
Rows (7: R11 5, R4 2)
| Row | Rule | Kind | Cited at (as of 5b66a7f) | Fact |
|---|---|---|---|---|
| F0276 | R11 | K7 | plugins/mutation-testing/skills/setup/templates/config-template.md:65-73 |
pytest, vitest and Maven forms illustrate the neutral {tests} rule (the dotnet test sentence describes K1 script behavior and may stay as R6) |
| F0277 | R11 | K2 | plugins/mutation-testing/skills/setup/SKILL.md:67-70 |
probe-1 manifest list is a model-read detection table |
| F0278 | R11 | K2 | plugins/mutation-testing/skills/principles/reference/tooling.md:59-72 |
"Selecting a tool" manifest list duplicates setup probe 1 |
| F0279 | R11 | K4 | plugins/mutation-testing/skills/setup/SKILL.md:74-86 |
probes 3-4 runner guidance (Maven -Dtest, Gradle --tests, dotnet test per project) no script implements |
| F0280 | R4 | K3 | plugins/mutation-testing/skills/setup/SKILL.md:161-189 |
apply step 2 names the tool and its install command; step 6 proposes a per-runner test-command |
| F0289 | R4 | K4 | plugins/mutation-testing/skills/principles/reference/tooling.md:1-57 |
the Established tools table maps each ecosystem to the tool setup proposes |
| F0290 | R11 | K7 | plugins/mutation-testing/skills/principles/reference/tooling.md:90-114 |
Shell, Terraform, SQL and the lib/hook-utils.test.sh worked example |
F0280 and F0289 are one R4 pair (setup consumes the table) and stay in this part.
Files
- Cut:
plugins/mutation-testing/skills/setup/SKILL.md,plugins/mutation-testing/skills/setup/templates/config-template.md,plugins/mutation-testing/skills/principles/reference/tooling.md. - Outside references found by full-path
git grepat d46efa9:scripts/docs-anchor-baseline.txt:89(tooling.md, count 4);docs/conventions/mutation-testing.yaml:1(mentions config-template.md).
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, replaced at a routing site, or (R8) cut and marked pending its targeted case; a row whose cited text is already gone on
mainis listed as GONE. - The pull request body states this part's row count (7) 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 each changed skill (setup, principles), 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.
-
scripts/docs-anchor-baseline.txt:89matches tooling.md's remaining anchors after the cut, anddocs/conventions/mutation-testing.yamlstill names a file that exists. - 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: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: three mutation-testing skill files (setup SKILL.md, config-template.md, principles tooling.md), plus the docs-anchor baseline line and the conventions yaml. Read by the model when it runs setup or principles.
Reversible: yes; revert the pull request.
Open questions: none
I understood this as part 1 of 3 of #16752: cut the 7 listed rows (F0276–F0280, F0289, F0290) of bundled ecosystem specifics from mutation-testing, per rules R11 and R4 and ADR 0101. Scope, files and done-when are exact. The post-PR eval is a host-session step, so it doesn't hold triage. I found no duplicate among the open issues and no merged pull request that already does this.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 21, 2026
Not admitted to the issue lane: its done-when asks for what an unattended lane run cannot perform: item 3 (tracker-output: "Each R11 row's script-reader search is quoted in the pull request body; a row..."); recommended split: keep the other items here as the admissible issue and move these to a child issue for the host queue (
host-run). Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).melodic-automation-lanes commentedon Nov 21, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: Cut or replace the seven ecosystem-specific rows (F0276-F0280, F0289, F0290) in mutation-testing's setup SKILL.md, config-template.md and principles/reference/tooling.md, keeping the baseline and convention references valid.
Split. Done-when item 3 of the issue body needs a person: it is a check a person runs, listed below, and the lane does not do it. This issue keeps the rest of its done-when.
Not done by the lane: checks a person runs
External state: none
Related work
Sources read
Automated refinement by the lanes App. Intake triages the issue again with it.
melodic-automation-lanes commentedon Nov 21, 2026
{"v":1,"actor_id":337595936,"title_sha256":"a6c758157d09f12d11667fe1dcf8aadcca2df19e00fd829afe0de25619c2623c","body_sha256":"e46716b6be4a69f4fcd05f183521bb96c4a58f2ec76b3aebc236c1cc0b634d80"}
melodic-automation-lanes commentedon Nov 21, 2026
This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44845749610, the work-resolve-issue run that
agent-readystarted, before any model turn, because the GITHUB_TOKEN budget was under its start-gate share, or the window was projected to have under its start-project share of the header's limit left by the run's expected end (github-token start-gate, start-project and start-run-minutes in rate-limits.json; the run's start-gate notice names which); that run ended at 2026-11-21T00:45:29Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A budget stop is the lanes' load, not a fault in this issue: it never counts toward limits.limit-stops-per-issue or thekill-switchwait.github-actions commentedon Nov 21, 2026