Path alias imports resolve to actual files

Path-alias hallucinations are one of the most common AI failure modes: the model writes import { calculateTax } from '@/lib/billing/calculator' for a file it imagined rather than a file that exists. The TypeScript compiler and the bundler both fail at the resolution step, so the build breaks and the route cannot render. Even when tsc --noEmit is skipped in CI, runtime imports via dynamic import() throw Cannot find module the first time the code path executes in production.

Run tsc --noEmit to surface every unresolved alias, then for each one decide whether to create the missing file or correct the import specifier. Fix the reference in place:

// Correct: points at a file that actually exists under src/lib/billing/
import { calculateTax } from '@/lib/billing/tax'

If the alias itself is wrong, update tsconfig.json compilerOptions.paths so the prefix maps to the real directory.