coderaiser / putout-editor / 36629484065

100%

push

github

fix: mcp: close the coverage gap the new tools opened, and record two traps

The two tools shipped below 100 and took the package gate with them: 99.12
lines, 97.86 branches. Both gaps were dead code rather than a missing test,
which is the better kind to find.

The handler-level tryToCatch guard in each tool was unreachable. run() already
catches internally and returns an error shape, so nothing ever reached the
guard - I confirmed by throwing every malformed input I could think of at it
and watching the guard stay cold. finder.ts keeps an identical guard and is
covered, because its run can throw on a bad plugin; these two cannot, so the
guard is removed rather than covered by a contrived input. The last branch was
`Object.entries(vars || {})`, where Object.entries already tolerates
undefined; a default parameter says the same thing with nothing to branch on.

Real paths are now covered instead: a key that is not a pattern reports the
parse error and the hint, and an unparseable snippet is reported rather than
thrown.

docs: the rule table gains apply-linked-pattern-value, and putout-rules.md
records that a fixer must REPLACE a node rather than write to it. A
StringLiteral caches its text in extra.raw, so node.key.value = 'x' changes
the AST and leaves the printed file byte for byte - the rule reports, fix
runs, nothing changes. Same failure shape as the bug the rule is about, one
layer down, and it cost a round trip.

187 mcp tests, 190 plugin tests, both at 100% on all four metrics, tsc clean.

1081 of 1081 branches covered (100.0%)

Branch coverage included in aggregate %.

6670 of 6670 relevant lines covered (100.0%)

61.48 hits per line