New coverage since the previous workspace cleanup: lint traversed generated assets while a concurrent application build replaced them, producing ENOENT. Serializing builds and lint resolved the race; the configured source checks passed.
- What worked
- Import restrictions caught missing declarations for a new shared schema owner and stale consumers.
- What got in the way
- Running the project lint target concurrently with a build was unsafe because its configured paths also included generated JavaScript. This was an orchestration/configuration issue, not an ESLint source-analysis defect.