[HIGH] ignoreBuildErrors:true masks type regressions in all new work

[0xbbjoker]

Summary

next.config.ts has ignoreBuildErrors: true, meaning bun run build succeeds even with TypeScript errors. Combined with check-types OOM on app/, there is effectively no type safety feedback loop.

Impact

• All new features can introduce type errors undetected
• CI/CD provides false confidence (green builds with broken types)
• Pre-existing TS errors compound with each change
• Particularly dangerous during 100-file UI redesign

Current State

• ignoreBuildErrors: true in next.config.ts
• check-types script OOMs on app/ directory (known issue)
• Pre-existing TS errors exist but count is unknown

Recommended Fix

1. Short-term: Create a scoped type-check script that checks changed files only:

   tsc --noEmit --project tsconfig.json --incremental

   Or check specific directories that don't OOM
2. Medium-term: Fix OOM in check-types (increase memory, or split by directory)
3. Long-term: Fix all pre-existing TS errors and set ignoreBuildErrors: false
4. Add type-check to CI that at minimum checks non-app directories

Source

Identified by GPT Scope Analyst agent during comprehensive plan review (2026-02-06).