docs: count the JustDummies analyzers in the mutation pages - #328
Merged
Conversation
ADR-0044 added a third leg to the JustDummies mutation matrix and a fifth Stryker configuration at `break: 0`, but the two workflow pages still described the state before it. Three claims had gone false: the JustDummies gate covering "two packages", its configurations being `justdummies.json` and `justdummies-xunit.json` alone, and "four projects have no bar yet". Correct the count everywhere it is stated — including the migration checklist, where taking only two configurations to the new repository would have dropped the analyzers leg — and say why that leg carries no bar: unlike the others it is not waiting on a sweep, it reports rather than blocks because its residual survivors are the analyzer-infrastructure mutants the FirstClassErrors analyzers carry too. The section titles are left untouched: `mutation` links to them by anchor. No threshold figure was stale — the pages quote none, so raising `testing` to 90 and `justdummies-xunit` to 80 left them accurate. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TGVx78thdSPSQY9pRRsP45
Reefact
enabled auto-merge
July 27, 2026 21:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ADR-0044 added a third leg to the JustDummies mutation matrix and a fifth Stryker configuration at
break: 0. The two workflow pages were written before it and still described the state without it, so three of their claims had quietly gone false. This pull request brings them back in line with the workflows they document. No code, no workflow and no configuration is touched.Type of change
Changes
mutation.{en,fr}.mdjustdummies-mutation.{en,fr}.md— what it coversjustdummies.jsonandjustdummies-xunit.jsonjustdummies-analyzers.jsonincludedsolutionfield of all threeThe last row is the one that mattered most. The "when JustDummies moves to its own repository" checklist told a future maintainer to take two configurations across; followed literally, it would have left the analyzers leg behind — a gate leg silently lost in the move, which is precisely what a checklist exists to prevent.
The pages now also say why that leg carries no bar, because its reason is not the others'. The four originals are waiting on a measured sweep. This one reports rather than blocks because its residual survivors are the analyzer-infrastructure and descriptor-string mutants the FirstClassErrors analyzers carry too — so Monday's sweep will not hand it a bar the way it will the others.
Two things deliberately left alone:
mutation.{en,fr}.mdlink into them by anchor (#justdummies-has-no-score-threshold-yet); renaming them would break the cross-reference, so the new material was added inside instead.testingto 90 andjustdummies-xunitto 80 in Assert what the mutation gate found unasserted in the two test-support packages #324 left them accurate, and nothing there needed touching.Testing
dotnet build FirstClassErrors.slndotnet test FirstClassErrors.slnFirstClassErrors.Analyzers.UnitTests)None were run, and none apply: the diff is prose in four Markdown files. What was verified: no stale claim survives anywhere in
doc/handwritten/for-maintainers/workflows/, every relative link in the four edited files resolves to a file that exists, both anchors referenced across pages still match a heading, and the commit message passes the repository's owntools/commit-lint/lint-commit-message.sh.Documentation
doc/updateddoc/handwritten/for-users/README.fr.md) updated if user-facing behavior changedBoth boxes are ticked on purpose: this is the documentation change, and the French maintainer pages are updated alongside the English ones as the bilingual convention requires.
doc/handwritten/for-users/README.fr.mdis untouched — the user-facing documentation is unaffected, since no user-facing behaviour changed.Architecture decisions
Proposed: ADR-____This records no decision; it makes the documentation match one already taken and merged (ADR-0044).
Related issues
None.
Generated by Claude Code