Onboarding: clicking "Open your inbox" sends new user to a non-existent URL (bounces back to start)
After completing onboarding, the "Open your inbox" button on the "Your workspace is ready" screen does not navigate to the workspace inbox. The user is bounced back to an empty start page with no erro
Claudio shipped a fix to ensure the onboarding flow correctly routes new users to their inbox instead of bouncing them back to the start page. The issue was identified as a routing failure where the layout attempted to mount on a path resolving to `/start` rather than the authenticated inbox URL, causing session initialization errors.
### Current Status
{color:green}Complete{/color} (Verification deferred to next fresh-account flow)
### Implementation Details
* **Problem:** The "Open your inbox" button failed to navigate to the workspace, triggering `error initializing session` in the console and redirecting the user to an empty start screen.
* **Fix:** Claudio updated the routing logic to ensure the post-onboarding redirect lands on the workspace inbox URL with generated issues visible.
* **Workaround:** Manually navigating to the root `socra.com` successfully redirects to the dashboard inbox.
### Verification Checklist
Hunter confirmed that manual navigation works but deferred the full "fresh user" verification due to session constraints. Future testing on a clean profile should confirm:
1. [ ] No bounce back to `/start` on clicking **Open your inbox**.
2. [ ] Four AI-generated issues are visible in the inbox.
3. [ ] Console is quiet (no session init errors).
4. [ ] **Skip** button flow also lands cleanly in the inbox.
> [!INFO]
> Status changed to Complete by @drhunter. Verification of the fix will be validated during the next live onboarding run.Hunter Johnson identifies a critical onboarding blocker where the "Open your inbox" button fails to navigate to the workspace, triggering "error initializing session" logs and redirecting users to an empty start page. The bug prevents new users from accessing four AI-generated issues despite the workspace being successfully created server-side.By Hunter Johnson