fix(navigation): land on workspaces from the app entry, not settings

[waleedlatif1]

Summary

• Opening the app as an organization member whose organization has not been rolled out landed on the General settings form instead of a workspace. Send them to the workspace picker, which is where the entry pointed before the organization surface existed.
• The default landing never opens settings. The /o guards still fall back to settings for viewers who explicitly asked for the organization surface — that case is unchanged.
• Fixed an infinite /home ↔ /login redirect loop on a stale session cookie. The proxy treats /home as an app surface and redirects cookie-less requests to /login before the route renders, and auth-disabled deployments always resolve an anonymous session — so a null session inside /home always means a present-but-invalid cookie. Redirecting that to /login was bounced straight back by the proxy's presence-only cookie check, looping until the browser gave up and leaving the viewer unable to reach the login page at all. It now hands off to the workspace loader, the one identity-recovery surface, which clears the stale cookies before navigating.

Type of Change

• Bug fix

Testing

• 22 tests pass across app/home and lib/navigation. Both fixes verified to fail when reverted.
• bun run lint, block-registry audit, all 46 audits (check:audits), docs-manifest:check, and type-check pass.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Sep 9, 2026 10:33pm UTC

[greptile-apps]

Greptile Summary

This PR corrects signed-in application entry routing and stale-session recovery.

• Organization members without the organization surface enabled now enter through the workspace picker instead of workspace settings.
• A stale session reaching /home is handed to the workspace loader, where stale cookies can be cleared before login.
• Existing explicit organization-route fallbacks to workspace settings remain unchanged.

Confidence Score: 5/5

The PR appears safe to merge; both routing changes preserve existing access boundaries while correcting their destinations.

No actionable failure remains: stale-cookie requests can reach the workspace recovery flow, and the app-entry destination change retains the existing workspace selection and creation behavior without altering explicit organization-route guards.

Important Files Changed

Filename	Overview
apps/sim/app/home/page.tsx	Redirects missing sessions to the workspace recovery surface instead of entering the stale-cookie login loop.
apps/sim/lib/navigation/resolve-app-entry.ts	Routes members without organization-surface access to the workspace picker rather than workspace settings.
apps/sim/app/home/page.test.tsx	Updates the stale-session regression test to require workspace recovery and reject direct login redirection.
apps/sim/lib/navigation/resolve-app-entry.test.ts	Verifies the new workspace-picker destination for organization members without rollout access.
apps/sim/lib/navigation/organization-rollout.test.ts	Preserves impersonation coverage while updating the non-rolled-out destination.

_{Reviews (1): Last reviewed commit: "fix(navigation): land on workspaces from..." | Re-trigger Greptile}