fix(portal): static files 404 on clients host + raw cuid in revision picker

[tanthehack]

Two portal bugs, both visible right now on main.

1. Static files 404 on the clients host — the login wash vanished

My regression from #9. The proxy rewrote /auth-wash.png → /portal/auth-wash.png, which doesn't exist. The old matcher only excluded _next/static, _next/image, favicon.ico and icon.svg, so every other file in public/ got swallowed:

  /auth-wash.png   primary=200   clients=404
  /logo.svg        primary=200   clients=404

The giveaway was that the login page still showed its lime dot grid but no green wash — the grid is pure CSS (radial-gradient), so it drew fine, while the background <Image> was a 404. The wash only seemed to half-work because next/image proxies through /_next/image, which was excluded.

Fix: any path with a file extension (plus all of /_next/) returns early untouched; extension-less paths are routes and still rewrite into app/portal/*. Matcher broadened to /((?!_next/|api/).*) and the asset test moved into proxy() where it can carry a comment explaining why.

This also pre-empts robots.txt, sitemap.xml, manifest.json, OG images, and font files — all of which would have 404'd on the client domain.

2. Revision picker showed a raw cuid

The "Request a revision" dialog rendered cmss519yc0002o8rke1kpkv3x instead of the project name.

Base UI's Select.Root takes an items map (value → label), and its own types are explicit:

When specified, <Select.Value> renders the label of the selected item instead of the raw value.

Without it, Select.Value prints the raw value — the project id. Fix passes items={{ [p.id]: p.name }}.

Cherry-picked from 2c1c9c7 on feature/revision-flow, where this was already written but sits unmerged behind five feature commits. Applied cleanly and kept the root-relative link rewrites from #9 intact. When feature/revision-flow eventually lands, git will see the identical change — but worth a glance at that file during its rebase.

Verification

• /auth-wash.png and /logo.svg now 200 on both hosts; login wash confirmed rendering (bright green leaf-shadow, sampled avg luminance 118/255 — it was loading and bright all along, just 404ing).
• Full 21-case routing matrix re-run, nothing regressed — routes, bookmarks, admin blocking, dynamic routes, 404s, case-insensitive host match, other subdomains, primary-host admin.
• tsc --noEmit clean · eslint clean on both changed files.

Not visually verified: the revision picker itself — that needs a logged-in portal session (OTP to your email), which I can't do. The fix is confirmed against Base UI's documented API rather than a screenshot. Worth a 5-second look after merge.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clover-admin	Ready	Preview	Aug 21, 2026 2:29pm