apps/web has no start script: production bundle is never runnable/smoke-tested anywhere

[aryamthecodebreaker]

Found while smoke-testing the workspace (v0.9.0).

apps/web/package.json only defines build, dev, lint, test, and typecheck. There is no start script, so after npm run build:web succeeds there is no wired-up way to serve the production bundle locally:

npm run build:web        # ok, prerenders all routes
npm run start -w @fixmap/web
# npm error Missing script: "start"

Vercel handles production serving fine, but this means:

1. The production build is never executed anywhere before deploy - CI builds it but nothing ever runs it, so runtime-only regressions (client-side crashes, broken hydration on the interactive hero demo) ship unseen.
2. Contributors cannot smoke-test the prod bundle locally without remembering to run npx next start manually inside apps/web.

Suggested fix

Add "start": "next start" to apps/web/package.json, and optionally add a post-build smoke step to ci that starts the built app and curls / and /demo.

For reference while testing manually: / and /demo return 200 on the dev server, unknown routes correctly 404.