fix: make typecheck:infra runnable from a normal checkout

The script called a bare `tsc`, but the root package has no typescript
dependency, so it failed with "tsc: command not found" unless a global tsc
happened to be installed. Add typescript (catalog) to the root devDependencies
and run it through scripts/typecheck-infra.sh.

That script also checks for the generated .sst/platform and infra/.sst/platform
type directories first. When either is missing, tsc reports hundreds of
"Cannot find name 'aws'" errors that hide the cause; it now stops and prints
the bootstrap commands from docs/agents/local-dev.md instead.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GxJAQRVHiCL6JA2xUf2nRg

Author: stewartjarod

docs/agents/local-dev.md

@@ -17,10 +17,12 @@ defaults (`http://localhost:3001` / `:3000`), which portless leaves unserved.
 ## `pnpm check:all` in a fresh checkout
 
 `pnpm install` is **not** enough for `check:all` in a tree nobody has built in — a fresh
-clone, a CI runner, or an isolated git worktree. Its `typecheck:infra` step is a bare
-`tsc` over `sst.config.ts` and `infra/selfhost.config.ts`, and both files open with
+clone, a CI runner, or an isolated git worktree. Its `typecheck:infra` step
+(`scripts/typecheck-infra.sh`) runs the root `tsc` over `sst.config.ts` and
+`infra/selfhost.config.ts`, and both files open with
 `/// <reference path="./.sst/platform/config.d.ts" />`. That file is *generated*, never
-built, so no amount of `turbo run build` produces it. Bootstrap it:
+built, so no amount of `turbo run build` produces it. The script checks for both
+directories first and prints these commands when one is missing. Bootstrap it:
 
 ```bash
 pnpm install

package.json

@@ -17,7 +17,7 @@
     "test:e2e": "pnpm --filter @wraps/e2e test:e2e",
     "test:coverage": "turbo run test:coverage --filter=@wraps.dev/cli",
     "typecheck": "turbo run typecheck",
-    "typecheck:infra": "tsc --noEmit --strict --skipLibCheck --target ES2022 --module ESNext --moduleResolution bundler --resolveJsonModule --esModuleInterop --allowSyntheticDefaultImports sst.config.ts infra/selfhost.config.ts",
+    "typecheck:infra": "bash scripts/typecheck-infra.sh",
     "check": "pnpm dlx ultracite@6.3.2 check",
     "check:errors": "pnpm dlx ultracite@6.3.2 check --diagnostic-level=error",
     "test:architecture": "vitest run --config vitest.config.ts",
@@ -76,6 +76,7 @@
     "react-email": "5.2.8",
     "sst": "4.2.4",
     "tsx": "^4.23.1",
+    "typescript": "catalog:",
     "turbo": "^2.10.7",
     "ultracite": "6.3.2",
     "vitest": "catalog:"

pnpm-lock.yaml

@@ -0,0 +1,28 @@
+#!/usr/bin/env bash
+# typecheck:infra — tsc over the two SST configs, which sit outside the pnpm
+# workspace so `turbo run typecheck` never visits them.
+#
+# Both files open with `/// <reference path="./.sst/platform/config.d.ts" />`,
+# and that file is generated by `sst install`, not built. Without it tsc reports
+# hundreds of "Cannot find name 'aws'" errors that hide the real cause, so check
+# for it first and say how to create it. Bootstrap steps: docs/agents/local-dev.md.
+set -euo pipefail
+
+cd "$(dirname "$0")/.."
+
+missing=()
+[[ -f .sst/platform/config.d.ts ]] || missing+=(".sst/platform")
+[[ -f infra/.sst/platform/config.d.ts ]] || missing+=("infra/.sst/platform")
+
+if (( ${#missing[@]} > 0 )); then
+  echo "typecheck:infra needs generated SST platform types that are missing: ${missing[*]}" >&2
+  echo "Generate them (details in docs/agents/local-dev.md):" >&2
+  echo "  node_modules/.bin/sst install" >&2
+  echo "  (cd infra && ../node_modules/.bin/sst install --config selfhost.config.ts --stage production)" >&2
+  exit 1
+fi
+
+exec node_modules/.bin/tsc --noEmit --strict --skipLibCheck \
+  --target ES2022 --module ESNext --moduleResolution bundler \
+  --resolveJsonModule --esModuleInterop --allowSyntheticDefaultImports \
+  sst.config.ts infra/selfhost.config.ts