fix: exclude local agent artifacts from checks
Description
Git-ignored .agents diagnostics could still be collected by lint and test commands. Exclude these directories at any depth from ESLint, TypeScript, Vitest and every Playwright project.
No linked issue.
Type of change
- Bug fix
- New feature
- Breaking change
- Documentation update
- Refactor
- Other (please describe):
How Has This Been Tested?
- Local build
- Lint
- Typecheck
- Unit tests
- Manual testing
Verified root and nested diagnostic fixtures against the real tools. The before/after discovery comparison retains all 212 real unit-test files and 294 browser-test cases, while excluding the nested agent fixtures. Application files remain included by ESLint and TypeScript. Temporary fixtures were removed.
GitHub CI passed on 65ad30a5: lint, types, production build, 2,156 unit tests (four existing skips), and browser tests (291 passed, one navigation test passed on retry, two skipped). The follow-up also passed focused local lint, type checking and the normal pre-commit hook.
Local CPU/GPU component-import timeouts also reproduce on unchanged staging. Local pre-push bypasses were approved for this PR; test assertions and timeout settings are unchanged.
Screenshots (if applicable)
Not applicable.
Checklist
- My code follows the style guidelines of this project
- I have performed a self-review of my code
- I have made corresponding changes to the documentation
- I have checked that all checks (lint, typecheck, test) pass
Notes for reviewers
Playwright's project-level ignore list overrides its top-level list, so the agent-folder exclusion is included in both. Vitest's default exclusions are preserved. No documentation update is needed for this tooling fix.
Summary by CodeRabbit
- Chores
- Updated project validation settings to exclude agent-related files from linting, TypeScript checks, and Playwright tests.
- Updated unit test settings to retain default exclusions while excluding Playwright configuration and agent-related files.
- Reformatted an internal route-boundary notice without changing its wording. These changes affect development tooling only; no end-user features or behavior changed.