Admin design direction: keep Festival v2 or go admin-flavored #368

Question

Follow-up decision to #317's identity: should admin keep the Festival v2 skin it inherits from the tokenization (#367), or move to a more admin-like design — calmer, denser, utility-first (e.g. solid surfaces instead of translucent washes, no Unbounded display type on tables/forms, possibly a light-first default)?

The mockup/prototype passes (#320, PR #354) only ever evaluated voter-facing screens, so Festival v2 was never validated against admin's tables, forms, and import flows. This ticket decides whether admin gets its own variant of the token values (the plumbing makes that cheap — same roles, different values under an admin scope) or stays on the shared skin.

Blocked by: #367

Part of wayfinder map #317. Scope change decided 2026-08-22.