fix: use activeOrganizationId for org redirect on app open

[Marfuen]

Summary

• The root page (/) was picking the first "ready" org from the memberships list, ignoring the session's activeOrganizationId
• This caused users to land on the wrong org after switching orgs and reopening the app
• Now always respects activeOrganizationId from the session, falling back to the previous behavior only for new users without an active org

Test plan

• Switch to a non-default org in the org switcher
• Close the browser window
• Reopen the app — should land on the org you last switched to

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
app	Ready	Preview, Comment	Apr 2, 2026 9:19pm
comp-framework-editor	Ready	Preview, Comment	Apr 2, 2026 9:19pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
portal	Skipped		Apr 2, 2026 9:19pm

[cursor]

PR Summary

Low Risk
Low risk: changes are limited to server-side redirect target selection and only affect which organization ID is chosen, with fallbacks preserved when no active org is set.

Overview
Redirect logic for /, /setup, and /admin now prefers the session’s activeOrganizationId when choosing which organization to land in, instead of defaulting to the first (or first “ready”) membership.

If the active org isn’t present, behavior falls back to the previous first-org selection, keeping existing onboarding/upgrade redirects intact.

^{Written by Cursor Bugbot for commit a2ad590. This will update automatically on new commits. Configure here.}