/** * BACKLOG P6 (ARK-14): import-boundary check. Advisory today (run manually / * `pnpm run deps:check`) -- not wired as a blocking CI gate in this pass, * so a first real run surfacing findings doesn't turn a green PR red * unexpectedly. Wiring it into CI is a reasonable next step once the * initial finding set (if any) has been triaged. * * Boundaries encoded, matching CLAUDE.md / docs/architecture/ARCHITECTURE.md: * - `services/scrapers` and `services/api` are Python -- not traversed by * this JS/TS dependency graph at all; no rule needed, they're simply * out of dependency-cruiser's file-type scope. * - `src/` (the capability layer, blocking-typechecked) must not import * from `app/` or `components/` (the v0-generated UI layer, advisory-only) * -- that would pull UI-layer assumptions into the tested backend layer. * - Nothing may import from `tests/` (test helpers stay test-only). */ module.exports = { forbidden: [ { name: 'no-src-importing-app-or-components', comment: 'src/ is the blocking-typechecked capability layer (tsconfig.check.json); app/ and components/ are the advisory v0-generated UI layer. src/ importing from them would pull unverified UI-layer code into the tested backend layer.', severity: 'error', from: { path: '^src' }, to: { path: '^(app|components)' }, }, { name: 'no-importing-tests', comment: 'Test helpers stay test-only -- application code must not depend on tests/.', severity: 'error', from: { pathNot: '^tests' }, to: { path: '^tests' }, }, { name: 'no-circular', comment: 'Circular imports make the module graph hard to reason about and can hide load-order bugs.', severity: 'warn', from: {}, to: { circular: true }, }, ], options: { tsPreCompilationDeps: true, tsConfig: { fileName: 'tsconfig.json' }, exclude: { path: 'node_modules|\\.next|services/(api|scrapers)|services/infra' }, reporterOptions: { text: { highlightFocused: true }, }, }, };