Parent

#112 — PRD: macOS Desktop Client (Electron, Intel x64 v1)

What to build

Enable standalone production output for the Next application so a single Node process can serve the full editor without pnpm dev. Wire the e2e Capability Parity seam: Playwright runs against this production standalone server (same artifact the Desktop Client will bundle).

End-to-end outcome: after next build, starting the standalone server on loopback serves the entry view, API routes, Skill templates, and existing e2e specs pass unchanged against that server.

Include any copy/trace steps required so Skill template assets and static files needed at runtime are present in the standalone artifact.

Acceptance criteria

• Next application builds with standalone output enabled
• Standalone server starts on a loopback port and serves the editor entry view
• /api/agents, /api/templates, and host-validation middleware behave as in dev
• e2e Playwright config uses the standalone production server (or documents an equivalent command that CI runs)
• Existing e2e cases (host-validation, export-menu, deploy-control) pass in CI against standalone
• Contributor docs note how to run standalone locally for Desktop Client development

Blocked by

None — can start immediately.