[HAPPYS1NGH]

Screenshots (before → after)

⏳ Pending — captured locally in light and dark themes for all seven steps; to be attached here.

• Universal usernames overview, lookup diagram: before = "Parent name" (.eth / DNS) and "Records" (Onchain / Offchain) toggles, ENS Resolver → CCIP Gateway → onchain or offchain store, 6 steps · after = no toggles; Wallet → Universal Resolver → HybridResolverV2 (OffchainLookup) → Namespace gateway → your endpoint → signed answer → verified callback, 7 steps, follows the site theme
• Universal usernames overview, page body: before = promises happy.brand.id via DNS import and records "on an L2, or on another chain" · after = v1 scope only, "Who controls what" and "What this does not do" sections, valid next-step cards

Changes

• Cherry-pick 578fe11 (FlowExplainer motion and theme tokens) — keeps the user's motion work and light/dark palette — the diagram follows the site theme instead of being dark in both
• Skip 83a6d3d — it re-implements the same light/dark tokenization with older values and conflicts in every hunk; its only extra tokens style the toggles and muted store node this PR removes, and its --fx-muted opacity token collides with 578fe11's --fx-muted color — nothing left to carry
• Reduce FlowExplainer to the v1 lookup — wallet → Universal Resolver → HybridResolverV2 OffchainLookup → Namespace gateway → brand endpoint → signed answer → verified callback — no DNS or onchain-records path that v1 doesn't support
• Draw the gateway request and signed answer as arcs between wallet and gateway — the client makes the HTTP call, not the contract — and make the recoil reach the resolver on the short edge
• Narrow overview/universal-usernames.mdx to v1 — second-level .eth parent, one label, brand-hosted HTTPS endpoint, HybridResolverV2 offchain route via CCIP-Read — removes the DNS-import and other-chain promises
• State who controls what and what v1 doesn't do — brand is authoritative, only the exact parent owner configures (signature, no transaction), records are public, no nested names, no reverse resolution
• Replace the "Issue gasless subnames" card with "Talk to us" next to "Learn about subnames" — both targets exist; the guide cards land in the stacked PR

Notes

• Layer 1 of 2. The integration guide, endpoint reference, API pages and adapter template stack on top in docs/universal-usernames-guides.
• Source of truth: the Universal Usernames contract (v1 scope, HybridResolverV2 offchain route 1, exact-owner configuration).
• 5859d5c (empty guide page, broken cards) is not used.
• Verification: npm ci then npm run check — build validation, broken links, a11y, content checks (86 pages, 85 routes) and check:examples all pass. Baseline on main also passed. Rendered with mint dev and Playwright: all 7 beats in light and dark, with and without reduced motion; the packet follows the arcs.
• No pre-existing failures.

🤖 Generated with Claude Code

https://claude.ai/code/session_019oGqmTa3TRAEt8JZnPPL6p

[HAPPYS1NGH]

Closing: Universal Usernames won't ship an SDK package, docs or skill changes for now. Branch kept.