[clydin]

When vitestConfig.root differs from workspaceRoot (such as with symlinks or Windows subst drives), VitestExecutor still invalidated and queried test specifications during incremental watch-mode rebuilds using the un-rebased workspaceRoot paths. Because Vitest keys its module graph and test specifications against vitest.config.root, incremental re-runs could fail to invalidate cached modules or locate the affected test specifications.

To address this, extract a rebasePath helper in plugins.ts that converts paths between roots while leaving paths that cannot be expressed relative to the original root (such as files on a different Windows drive) unchanged instead of concatenating them. VitestExecutor now uses this helper during incremental rebuilds to rebase modified output and source file paths onto vitest.config.root when the root is aliased. Additionally, configureVitest now rebases from the original plugin options rather than mutating from the previous root so repeated invocations remain idempotent. plugins_spec.ts is expanded to cover rebasePath, angular: virtual entries, absolute setup files under coverage, and repeated configureVitest calls, and a new executor_spec.ts covers the incremental rebuild paths.

[gemini-code-assist]

Code Review

This pull request introduces path rebasing support for the Vitest unit test runner when the Vitest root is aliased (different from the workspace root). It adds a rebasePath utility to correctly map file paths between the workspace root and the Vitest root, ensuring that incremental rebuilds, file invalidations, and setup file loading work correctly in aliased environments. Unit tests have been added to verify these changes. There are no review comments, so I have no feedback to provide.