Parse frontend mock.module calls in test planner

[zebbern]

Summary

• replace raw-text mock.module detection with a TypeScript AST call-expression check
• keep direct mock.module test files isolated while ignoring comments and string literals
• add a regression test for quoted/commented mock.module text

Verification

• bun --cwd=frontend test src/test/run-tests-plan.test.ts
• bun --cwd=frontend run test
• bun run typecheck
• bun run lint
• bun run test
• git push pre-push hook reran typecheck and tests successfully

[Copilot]

Pull request overview

Updates the frontend test planner’s “mock.module usage” detection to use a TypeScript AST traversal instead of raw text matching, so that only real mock.module(...) call expressions cause tests to be isolated (and quoted/commented text no longer triggers isolation).

Changes:

• Replace regex-based mock.module( detection with a TypeScript AST CallExpression check for mock.module(...).
• Add a regression test ensuring mock.module inside string literals and comments is ignored.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
frontend/src/test/run-tests-plan.ts	Switches usesMockModule() to parse the file with TypeScript and detect actual mock.module(...) calls via AST traversal.
frontend/src/test/run-tests-plan.test.ts	Adds a regression test covering commented/quoted mock.module text to prevent false-positive isolation.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.