You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ts-react-linter-driven-development v2.1.0 — one set of thresholds, mixed-diff routing, hunter listings
This commit was created on GitHub.com and signed with GitHub’s verified signature.
[2.1.0] - 2026-10-18
Changed
A whole-repository review leaves the mutant question to scoped reviews. On --all, the hunter does not judge the question "does a mutant survive a leaf's
tests?". Its receipt reads per-leaf, not judged, and its not reached: line names
the three leaf directories with the most hits, each as the scoped review that
judges it (/tsr-ldd-review <dir>). A scoped review judges the question in full. The lead for
the mutant question also skips .tsx files, components/, hooks/ and context/.
The god file has a mechanical lead. The question "is one feature's code spread
across layer directories?" lists the longest files in scope with wc -l and checks
each against sonarjs/max-lines (600). A file over the limit, or with
a max-lines directive that silences the rule, is a violation when it stands in for the
whole slice.
The review command says how to cover a large repository. On a repository
larger than a few dozen source files, --all reports PARTIAL coverage. The
command names the form that covers everything: one review per directory
(/tsr-ldd-review <dir>).
Fixed
A claim that something is missing needs a listing. A rule hunter that reports
a missing test file, doc, case or cleanup now carries the ls, find or grep
command that looked for it, run over the repository and not only the review's
bundle, and that command's output. Without the listing there is no finding. A
hunter once reported a test file as missing when it existed outside the scope.
When the hunter's budget leaves no call for the listing, the claim appears in the
hunter's not reached: line as unverified; the report never drops it.
A cluster title carries its rule ids. The review reference shows every cluster
title as 🔗 CLUSTER: <anchor> — <rules>, the same form as the skill. Agents
followed the reference, so the rule ids were on the lines below the title, and the
report graders missed correct clusters.
The mutant hand check reads the error assertions. The hand check opens the
leaf's test file, also when the file is outside the review's scope, and reads each
error assertion. An assertion that matches only a word all the leaf's errors share
(toThrow('tenant')) lets a removed check or a changed message survive, and it is a
violation.