A test suite that got smaller instead of failing
After a directory restructure, 13 of 57 Jest suites could not resolve @nestjs/* and workspace imports, so the run got quietly smaller instead of failing.
The safety net had a hole
The test, the audit log, the scanner, the CI run — covering less than I assumed it did.
The 2026-08-25 restructure into control-plane / data-plane / intelligence-plane moved a lot of paths. Afterwards, 13 of 57 suites couldn't resolve @nestjs/* or @open-derja/* imports.
The part worth remembering is what that looked like: not a failing test run, just a smaller one. Among the dead suites was a 403-line tasks.service spec covering the task engine — the single most important piece of domain logic in the project — and it had been silently not running. Fixed with modulePaths and moduleNameMapper in the jest config, taking the suite from a misleadingly green run to 59 suites and 302 tests genuinely green.
A test suite that can't resolve its imports and a test suite that doesn't exist look identical in a summary line. After any structural move, the number to check is the count, not the colour.