FIB-51490: Scope testing-library plugin to test files only

[agierloff88]

Summary

@fishbrain/eslint-config-react applied eslint-plugin-testing-library's flat/react preset with no files restriction, so it linted the entire codebase — not just tests. That produces false positives in source, e.g. our own logger.debug(...) flagged by testing-library/no-debugging-utils as if it were screen.debug().

This scopes the plugin to test files only, following the plugin's official recommendation:

const testingConfig = [
  {
    files: ['**/__tests__/**/*.[jt]s?(x)', '**/?(*.)+(spec|test).[jt]s?(x)'],
    ...testingLibraryPlugin.configs['flat/react'],
  },
];

Version bumped 6.3.6 → 6.3.7 (all three package.json files, per the repo's lockstep convention).

Verification

calculateConfigForFile confirms testing-library/* rules are now active only on test files:

File	no-debugging-utils
src/foo.ts	NOT ACTIVE
src/foo.test.tsx	active (warn)
src/__tests__/bar.ts	active (warn)

Workspace tests pass (yarn workspaces foreach --all run test).

Downstream

Once 6.3.7 is published, consumers ("mykiss and friends") can bump and will lose the false positives. In mykiss-web specifically this also unblocks removing the testing-library/render-result-naming-convention: 'off' workaround (whose comment cites this exact "plugin runs against all files" limitation).

Part of FIB-35810 → FIB-51490.

🤖 Generated with Claude Code

[lhansford]

Thanks for fixing this 🙏

[agierloff88]

@lhansford whats the workflow on bumping versions here? I see in other prs the versions have not been bumped. Should we add something to the readme so claude also know the workflow?

[lhansford]

@lhansford whats the workflow on bumping versions here? I see in other prs the versions have not been bumped. Should we add something to the readme so claude also know the workflow?

We're just cutting release manually when we want to. There's instructions in the readme

[agierloff88]

got it thanks