{ "title": "Clear the bucket_catch frontend eslint backlog without suppressions", "objective": "bucket_catch/packages/frontend had 45 eslint errors that were unmasked, not caused, by a typecheck repair last session: `lint` is `tsc --noEmit && eslint src`, and a broken tsc had been short-circuiting the && so eslint had never run on the package. The user asked for all of them fixed. The binding constraint is that the package holds a 100% coverage gate, so any fix that adds an unreachable branch trades a lint error for a coverage failure - and the no-suppressions rule forbids escaping either with a disable comment.", "acceptance_criteria": [ "eslint error count drops substantially from 45, with every remaining error named and explained rather than silenced", "No eslint-disable, no @ts-ignore, no rule downgraded in config, no coverage threshold lowered", "npm run coverage still reports 100% on statements, branches, functions and lines; any change in the totals is attributable to a named edit", "The test count stays at 145 across 15 files", "npx tsc --noEmit exits 0" ], "out_of_scope": [ "Refactoring App.tsx's phase state to carry the game result - the correct fix for the last no-non-null-assertion, but a wider change than a lint pass", "Any change to component behaviour or to what the tests assert", "The other repos touched in this session" ], "verifier": "npx eslint src for the count; npm run coverage for the 100% gate and the 145-test count; npx tsc --noEmit for the typecheck. Each touched test file was additionally run on its own with npx vitest run as it was edited." }