Styled pod owner console — the 3 app layers (private / attested-w-override / attested-prod), watermelon design

[amiller]

Operator feedback, 2026-07-09: the pod site 'doesn't keep up with the oauth3 style,' and as owner I should see ALL apps — including ones not yet promoted to attested — across the 3 layers we discussed: private/dev, attested-with-operator-override, and attested-prod.

Current state (verified)

• The pod root https://pod.dstack.soc1024.com/ serves RAW JSON (the anonymous /_api/projects), not a styled page. There is no styled daemon-level console at all — the watermelon design system (~/projects/oauth3/design/, zed specs/design/) lives only in the oauth3 APP, never applied to the pod surface. That's why it 'doesn't match': the styled surface (RFC 0016 Fleet Console, Implement RFC 0016 — Fleet Console and Status Surface #20) was never built.
• Owner-visibility backend ALREADY EXISTS: PR Viewer: owner-token login so the pod owner sees non-attested projects (#72) #75 (merged, closes the ask in Viewer: owner token login so the pod owner sees non-attested projects #72) means the owner token sees 9 projects vs 3 anonymous. But there is no UI — you have to curl with a token to see the non-attested ones.
• Data already carries the layering signals: mode (attested/dev) + public flag + attestation fields (commit_sha, tree_hash). RFC 0029 (RFC 0029: Attested apps with declared operator debug #66) defines the middle 'attested-with-declared-operator-debug' layer.

Ask: a styled owner console at the pod root (or /console)

• Applies the watermelon constructivist-overprint kit (teal #00838a / fluoro pink #ff48b0), light-default, same system as the oauth3 app — so the pod and its apps read as one product.
• Owner-token login (reuse PR Viewer: owner-token login so the pod owner sees non-attested projects (#72) #75's mechanism); anonymous visitors see only public-verifiable apps + a pointer to the interesting ones (folds in Pod homepage should point visitors to the interesting apps deployed on it #43).
• Renders apps grouped into the 3 layers with a clear visual stripe/badge per layer: (1) private/dev — owner-only, (2) attested-with-operator-override (RFC 0029 RFC 0029: Attested apps with declared operator debug #66), (3) attested-prod public. Each card: name, mode, source+commit, tree_hash verify link, layer badge.

Acceptance

Screenshot of the console at the pod root, owner-authenticated, showing all 9 apps sorted into the 3 layers with distinct styled badges, in the watermelon palette (not raw JSON), light theme. Anonymous load shows only the 3 public apps + the app pointer. Screenshot committed in the PR.

Operator steps

Owner-token login in the console needs the owner secret at view time (same as PR #75); note it in the PR. Ties into RFC 0016 #20, RFC 0029 #66, homepage #43.