fix: chronicle start runs Nitro production server

[rsbh]

Summary

chronicle start was using Vite preview() — a static file server that doesn't run Nitro SSR, API routes, or search. Now it spawns node .output/server/index.mjs (the actual Nitro production server).

Before

• Used Vite preview (static files only)
• No SSR, no API routes, no search
• allowedHosts errors in Docker

After

• Runs Nitro production server
• Full SSR + API routes + search
• Checks build exists, clear error message if not
• Forwards PORT/HOST env vars
• Signal forwarding to child process

Test plan

• chronicle build && chronicle start — full SSR works
• API routes (/api/search, /api/health) respond
• Ctrl+C stops the server
• Without build → shows "Run chronicle build first" error

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
chronicle	Ready	Preview, Comment	May 15, 2026 7:42am

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 54abd9c0-301e-4ea4-8cac-bac81a7d7dbc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/start-nitro

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}