[process-manager PM-32] Desktop packaging of the console (deno desktop, 5-target cross-compile)

[rickylabs]

Summary

Package the PM-29 console as a Deno 2.9 Desktop app via the #456 mechanics: --backend cef (bare-metal admin boxes can't assume WebView2), 5-target cross-compile, per-app-name persistent KV. Documented gap inherited verbatim: Windows auto-update stages-but-does-not-apply. Optional #451 in-process oRPC link as a soft optimization.

Scope

• Archetype / area: console packaging (SCOPE-frontend)
• Part of Epic: NetScript Process Manager — bare-metal supervisor + admin console (pup/pm2 done right) #510
• Depends on: [process-manager PM-29] Admin console: Fresh app, browser-served by the control plane #540 · Soft deps: feat(deploy): single-artifact packaging + release server + snapshot updater (substrate) #456 (packaging), feat(sdk): in-process link-mode adapter for single-process service mounting #451 (in-process link) — never M1 blockers
• Slips to a later milestone if feat(deploy): single-artifact packaging + release server + snapshot updater (substrate) #456 slips (R8); browser-served mode is the always-ships path

Design source

• research/design/d4-cli-admin-console-surfaces.md §3.2–3.4 (PMS-6) · plan.md §4 PM-32, R2

Acceptance criteria

• gate: packaged binary serves the console with the loopback (or in-process) client on all 5 targets
• gate: Windows auto-update caveat documented in the console guide
• gate: scoped check/lint/fmt wrappers green (--ext ts,tsx)

Non-scope

• New console features — packaging only.

Drift / Debt

• none

RFC #820 amendment (owner-ratified 2026-07-17 — PR #822)

The "Windows auto-update stages-but-does-not-apply caveat documented" acceptance line is superseded: the console updates via #456's snapshot transaction (real Windows apply). Deno.autoUpdate must not re-enter as a second authority.