thePR0M3TH3ANandClaude Opus 5 74a5c23dfb Clear the linter's built-in findings, keeping the one that was deliberate ...

Six warnings from oxlint's default rules, five of them genuinely redundant:
`...(x ?? {})` in an object literal, where spreading undefined is already a
no-op, and a `Boolean()` wrapping an `if` condition.

The sixth is kept. `for (const held of [...this.held.keys()]) this.forget(held)`
looks like a pointless array copy, and oxlint is right that for..of accepts an
iterable directly — but forget() deletes from this.held, so the spread is
what makes the loop iterate a snapshot instead of the map it is mutating.
Disabled on that line with the reason written next to it.

That distinction is the whole reason to read lint output rather than apply
it: a rule that is correct in general was wrong about the one site here where
it mattered, and the site it was wrong about locks every held seed.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01Vtx94nXDmNgXEeThUZP4QN

2026-08-20 13:02:55 -04:00

..

cli

Clear the linter's built-in findings, keeping the one that was deliberate

2026-08-20 13:02:55 -04:00

core

Clear the linter's built-in findings, keeping the one that was deliberate

2026-08-20 13:02:55 -04:00

test-vectors

feat(vault): port index0/atlas, and keep it current on every mutation

2026-08-19 11:13:15 -04:00