feat(dashboard): one-time Stack Auth → Hexclave rebrand modal

[BilalG1]

Summary

Adds a one-time informational modal that announces the Stack Auth → Hexclave rebrand to existing logged-in dashboard users. Brand-new users signing up after the cutoff already land on a fully Hexclave-branded experience and don't see the modal — they have no "Stack Auth" mental model to update.

Stacked on top of PR #1481 (the visible-rebrand flip).

What's in here

• Component: apps/dashboard/src/components/hexclave-rebrand-modal.tsx — the modal itself plus the static RebrandIllustration (Stack Auth mark → arrow → Hexclave benzene mark).
• Mount: apps/dashboard/src/app/(main)/(protected)/layout-client.tsx — single <HexclaveRebrandModal /> inside ConfigUpdateDialogProvider so it covers every authenticated dashboard route.
• Asset: apps/dashboard/public/hexclave-icon.svg — the benzene-ring mark pulled from https://hexclave.com/icon.svg (the canonical Hexclave brand mark). Stack Auth side uses the existing /logo.svg + /logo-bright.svg (dark mode variant).

Targeting

Three independent conditions must all hold for the modal to render:

1. Logged-in user — useUser({ or: "return-null" }) opts out of the sign-in redirect so guests are silently skipped.
2. user.signedUpAt < REBRAND_CUTOFF where REBRAND_CUTOFF = 2026-05-27T00:00:00Z. This is the cleanest "pre-rebrand user" signal — more accurate than cookie inspection (the existing stack-is-https hint cookie gets dual-written for new and returning users alike since packages/template/src/lib/cookie.ts:201, so it can't distinguish), and it follows the same user across browsers/devices.
3. No hexclave-rebrand-modal-dismissed=true in localStorage. Any dismissal path (Got it button, X, overlay click, Escape) routes through onOpenChange and writes this flag, so the modal never re-opens for that browser.

Behavior verification

End-to-end checked against a live dev dashboard:

• ✅ Modal opens once on first authenticated dashboard view for a pre-cutoff user.
• ✅ localStorage["hexclave-rebrand-modal-dismissed"] flips to "true" on any dismissal path.
• ✅ Reload after dismissal: zero [role=dialog] elements rendered, localStorage flag persists.
• ✅ Not rendered for guests (no useUser → early return null, no auth-redirect).
• ✅ Not rendered for users with signedUpAt >= REBRAND_CUTOFF.
• ✅ SSR-safe: hooks into useEffect to read storage post-hydration; try/catch around storage access so private-mode / sandboxed iframes degrade silently.
• ✅ pnpm --filter @stackframe/dashboard lint clean.

Notes

• pnpm typecheck was not run as part of this change because the dashboard typecheck depends on codegen-prisma against a live DB (pre-existing infra debt noted in PR feat(hexclave): PR 2 — visible rebrand (Hexclave brand goes public) #1481). Lint covers the type-shape of the touched files via the project's strict TS-aware ESLint rules.
• Migration link points to docs.hexclave.com/migration, the same URL referenced from packages/template/src/internal/deprecation-warning.ts:36 — single source of truth for the migration story.
• No animation by design — the modal is static; entry/exit uses the existing Radix Dialog fade.

---

Summary by cubic

Adds a one-time modal in the dashboard to announce the Stack Auth → Hexclave rebrand for pre-rebrand users. It shows once per account per browser, inlines the import-rename step, links the migration guide, and doesn’t show for new signups or in dev/preview environments.

• New Features
  • Shows only for logged-in users with signedUpAt < '2026-05-27T00:00:00Z'; guests, post-cutoff signups, and local emulator/remote dev/preview never see it.
  • Dismissal persists via localStorage["hexclave-rebrand-modal-dismissed:<user.id>"]="true"; all close paths set the flag.
  • Mounted in the protected dashboard layout so it covers all authenticated routes once per account per browser.
  • Includes illustration (/logo.svg → arrow → /hexclave-icon.svg) and links to app.hexclave.com and the migration guide; copy tells users to rename @stackframe/* to @hexclave/* (@stackframe/stack → @hexclave/next).

^{Written for commit 92c07f2. Summary will update on new commits. Review in cubic}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
stack-auth-hosted-components	Ready	Preview, Comment	May 27, 2026 1:05am
stack-auth-mcp	Ready	Preview, Comment	May 27, 2026 1:05am
stack-auth-skills	Ready	Preview, Comment	May 27, 2026 1:05am
stack-backend	Ready	Preview, Comment	May 27, 2026 1:05am
stack-dashboard	Ready	Preview, Comment	May 27, 2026 1:05am
stack-demo	Ready	Preview, Comment	May 27, 2026 1:05am
stack-docs	Ready	Preview, Comment	May 27, 2026 1:05am
stack-preview-backend	Ready	Preview, Comment	May 27, 2026 1:05am
stack-preview-dashboard	Ready	Preview, Comment	May 27, 2026 1:05am

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1a857f8f-c077-46db-8c9d-6c1cf194f405

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cl/hexclave-rebrand-modal

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cubic-dev-ai]

No issues found across 4 files

<sub>Tip: cubic could auto-approve low-risk PRs like this, if it thinks it's safe to merge. Learn more

Re-trigger cubic</sub>

[greptile-apps]

Greptile Summary

Adds a one-time informational modal that announces the Stack Auth → Hexclave rebrand to dashboard users who signed up before the 2026-05-27T00:00:00Z cutoff. The component is mounted in the protected layout's ConfigUpdateDialogProvider and guards itself with an SSR-safe useEffect/localStorage pattern so the modal never re-appears after any dismissal path.

• hexclave-rebrand-modal.tsx: New client component; derives isPreRebrandUser from user.signedUpAt, reads a localStorage flag post-hydration to avoid SSR mismatch, and writes the flag on any close event (button, X, overlay, Escape).
• layout-client.tsx: Minimal one-line mount of <HexclaveRebrandModal /> inside the existing ConfigUpdateDialogProvider wrapper.
• hexclave-icon.svg: New brand asset served from /public, consistent with how the existing logo.svg is handled.

Confidence Score: 4/5

Safe to merge; the modal is purely informational and the changes are well-isolated to a new component and a one-line layout mount.

The modal logic is correct and SSR-safe, but the localStorage key is not scoped to the logged-in user — on a shared device the first dismissal silences the announcement for everyone else who uses that browser. The cutoff timing also means auto-created preview users will see the modal for the next ~24 hours. Both are non-blocking but worth addressing before wide production traffic.

apps/dashboard/src/components/hexclave-rebrand-modal.tsx — the dismissal key and preview-environment behaviour warrant a second look.

Important Files Changed

Filename	Overview
apps/dashboard/src/components/hexclave-rebrand-modal.tsx	New one-time rebrand announcement modal; SSR-safe localStorage pattern is sound but the dismissal key is not user-scoped, which causes the modal to be silently suppressed for other users sharing the same browser.
apps/dashboard/src/app/(main)/(protected)/layout-client.tsx	Single-line mount of HexclaveRebrandModal inside ConfigUpdateDialogProvider; no logic changes, safe addition.
apps/dashboard/public/hexclave-icon.svg	New brand asset SVG; filter/gradient IDs are scoped to their own document context when served via next/image, no conflicts expected.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[LayoutClient mounts] --> B[HexclaveRebrandModal renders]
    B --> C{useUser returns user?}
    C -- "null (loading/guest)" --> D[return null — nothing rendered]
    C -- "user loaded" --> E{signedUpAt < REBRAND_CUTOFF?}
    E -- No --> F[return null — post-rebrand user]
    E -- Yes --> G[isPreRebrandUser = true, open = false]
    G --> H[useEffect fires, read localStorage]
    H --> I{dismissed === 'true'?}
    I -- Yes --> J[stay closed — already seen]
    I -- No --> K[setOpen true — Dialog shown]
    K --> L{User dismisses}
    L -- "Got it / X / Escape / Overlay" --> M[dismiss: write localStorage, setOpen false]
    M --> N[Modal closed permanently for this browser]

Loading

Prompt To Fix All With AI

Fix the following 3 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 3
apps/dashboard/src/components/hexclave-rebrand-modal.tsx:16
The dismissal flag is not scoped to the logged-in user. On a shared device (or a browser where multiple users take turns logging in), the first person to dismiss the modal writes `"true"` to the same key for every subsequent user. Pre-rebrand teammates sharing a machine would never receive the announcement.

```suggestion
const storageKey = (userId: string) => `hexclave-rebrand-modal-dismissed:${userId}`;
```

### Issue 2 of 3
apps/dashboard/src/components/hexclave-rebrand-modal.tsx:42-54
If the `STORAGE_KEY` becomes user-scoped (see the other comment), the `useEffect` and the `dismiss` function both need `user.id` to construct the correct key. Both the read in `useEffect` and the write in `dismiss` reference the module-level `STORAGE_KEY` constant; once that's replaced with `storageKey(user.id)` the two call-sites must be updated consistently, otherwise the effect reads one key and the writer writes another, causing the modal to reopen on every page load.

### Issue 3 of 3
apps/dashboard/src/components/hexclave-rebrand-modal.tsx:37
Preview / local-emulator users created before `REBRAND_CUTOFF` (today is 2026-05-26, the cutoff is 2026-05-27) will have a `signedUpAt` that satisfies `< REBRAND_CUTOFF`. Because `layout-client.tsx` auto-signs-up fresh preview accounts each session, each new preview load shows the rebrand modal until the cutoff date passes tomorrow. A simple guard checking the preview/emulator env vars inside the modal would suppress noise in non-production environments.

_{Reviews (1): Last reviewed commit: "feat(dashboard): add one-time Stack Auth..." | Re-trigger Greptile}