chore(tsconfig): explicit sourceMap and declarationMap: false

[John-David Dalton (jdalton)]

Sets sourceMap: false and declarationMap: false explicitly on every tsconfig.json in the repo. Keys are fully alphanumerically sorted within each compilerOptions block.

We never want to ship sourcemaps or declaration maps. Making the flags explicit prevents accidental regression when someone edits a config and forgets to check inheritance.

Files touched

• .config/tsconfig.base.json (was sourceMap: true → false)
• .config/tsconfig.build.json (was declarationMap: true → false; also adds sourceMap: false)
• .config/tsconfig.check.json
• .config/tsconfig.external-aliases.json
• .config/tsconfig.test.json
• packages/cli/.config/tsconfig.check.json
• packages/cli/tsconfig.json
• tsconfig.json
• .claude/hooks/check-new-deps/tsconfig.json

Split out from #1211 so the dep-hook cleanup there stays focused.

---

Note

Low Risk
Config-only change affecting TypeScript build/check outputs; main risk is reduced debugging fidelity if any workflow relied on sourcemaps or declaration maps.

Overview
Disables generation of TypeScript sourcemaps and declaration maps across the repo by explicitly setting sourceMap: false and declarationMap: false in all relevant tsconfig variants (base/build/check/test, root, CLI, and the .claude dependency hook).

Also normalizes compilerOptions ordering and updates inherited defaults (notably flipping .config/tsconfig.base.json sourceMap to false, and .config/tsconfig.build.json declarationMap to false while adding sourceMap: false) to prevent accidental re-enablement via config edits.

^{Reviewed by Cursor Bugbot for commit 625010c. Configure here.}