Problem
app/onboarding/page.tsx and app/callback/page.tsx have no loading.tsx/error.tsx siblings, unlike app/bookmarks, app/canvas, app/social, app/workspaces, and app/admin, which all have both. app/names/page.tsx and app/names/[slug] have the same gap despite being a content-heavy, data-fetching route similar to bookmarks/canvas.
Proposed fix
Add loading.tsx and error.tsx for the onboarding, callback, and names routes, following the existing pattern from app/bookmarks/app/canvas.
Why this matters
Onboarding and the OAuth callback are exactly the flows where a stalled network request or a thrown error leaves users on a blank/broken screen with no recovery UI — and they're also the flows where a stuck new user is most likely to bounce entirely.
Problem
app/onboarding/page.tsxandapp/callback/page.tsxhave noloading.tsx/error.tsxsiblings, unlikeapp/bookmarks,app/canvas,app/social,app/workspaces, andapp/admin, which all have both.app/names/page.tsxandapp/names/[slug]have the same gap despite being a content-heavy, data-fetching route similar to bookmarks/canvas.Proposed fix
Add
loading.tsxanderror.tsxfor the onboarding, callback, and names routes, following the existing pattern fromapp/bookmarks/app/canvas.Why this matters
Onboarding and the OAuth callback are exactly the flows where a stalled network request or a thrown error leaves users on a blank/broken screen with no recovery UI — and they're also the flows where a stuck new user is most likely to bounce entirely.