Prove the UltraModern.js direct-scan Zerops deployment path

[BleedingDev]

Question

What exact current UltraModern.js build and runtime contracts support one service containing the UI, BFF/API, Streamable HTTP MCP, and bounded analyzer subprocesses on Zerops, with PostgreSQL as the separate state service? Determine the production commands, container/runtime requirements, database wiring, writable temporary storage, subprocess packaging, Zerops configuration, and whether challenge eligibility truly requires a third product service.

[BleedingDev]

Research dispatched.

• Branch: research/ultramodern-zerops
• Temporary worktree: /tmp/codebase-radar-research.O8qi1B/worktrees/deployment
• Shared brief: /tmp/codebase-radar-research.O8qi1B/brief.md
• Primary report: /tmp/codebase-radar-research.O8qi1B/reports/deployment.md
• Branch context pointer: docs/research/ultramodern-zerops.md

The branch is throwaway and will contain the report snapshot; implementation remains on main.

[BleedingDev]

Resolved by the UltraModern/Zerops research branch.

Deploy two services: one Node 24 UltraModern.js application containing UI, Hono BFF/API, Streamable HTTP MCP, PostgreSQL-backed job loop, and bounded analyzer subprocesses; plus PostgreSQL 18. Use a minimal pnpm monorepo pinned through npm aliases to UltraModern 3.5.0-ultramodern.100. The challenge permits a single container and merely recommends, rather than mandates, three services.