[Deploy-S13] WATCH: RFC-14 unified-mode + Nitro deno_server (tier-3 serverless)

[rickylabs]

Scope

Watch / tracking only (decision D1): tier-3 serverless (Vercel / Cloudflare / Netlify) via the RFC-14 unified-mode program (Nitro v3 + oRPC + Fresh 2) and the Nitro deno_server preset. Not in v1 — it is a ~3-5 month, architecturally distinct effort, excludes sagas, and depends on the still---unstable Nitro preset. Aspire + Deno Deploy already deliver the cloud story without it.

Target / adapter

Tier-3 serverless (Vercel / Cloudflare / Netlify) — tracked, not built.

Acceptance criteria (tracking)

• Watch RFC-14 progress + Nitro deno_server preset stabilization.
• Re-evaluate for a milestone once tier-1/2 land and the preset is stable.

Dependencies

None (independent watch). Revisit post tier-1/2.

Tier / phase

WATCH · milestone Backlog / Triage

Parent epic: #327

Part of #327

[rickylabs]

Cross-link for the unified↔multi-process story: filed #371 (restore shared Deno KV Connect resource in the Aspire generator).

The load-bearing framing for RFC-14 unified-mode: local in-process Deno KV is the correct default for unified (single-process) deployment and should stay the default there. The gap is only that multi-process mode silently keeps that same per-process KV instead of switching to a shared backend, which breaks cross-process queue delivery + watch.

The promise to land is a config-driven switch: a dev runs unified mode + local Deno KV, and by changing only NetScript config flips to multi-process mode + shared Deno KV Connect (or Garnet/Redis on Docker-less bare metal) automatically — no app-code change; the generator provisions the shared resource and injects services__kv__http__0 + DENO_KV_ACCESS_TOKEN. The SDK already consumes this (@netscript/kv opens remote KV Connect URLs; @netscript/queue auto-selects its KvPollingAdapter for http(s):// KV paths, giving a cross-process queue over the shared KV). See #371 for the generator + CacheEntry schema work; the old rickylabs/netscript-start .NET AppHost (AddDenoKv/WithKvReference, --kv-mode=remote|local) is the historical reference. eis-chat is validating the bare-metal Garnet-executable arm now as a live reference.