[TheGreatAxios]

If the hub doesn't answer the "who is signed in?" check when the page loads, the interface now keeps trying and opens by itself once the hub is back. Before, someone signed in was stuck on the loading screen until they reloaded.

The shell and the invitation screen now share that one check, so it's asked once per load instead of two or three times.

Closes CL-12203.

[linear-code]

CL-12203

[TheGreatAxios]

Before and after, signed in, 45 seconds after the session check was unblocked (no reload):

Before	After

Before, the loading screen stays. After, the page has moved on by itself. This test account has no model key yet, so it lands on model setup.

This stays a draft until #213 and #214 merge; it will be rebased onto them, keeping the session answer when the cache is cleared on sign-out.

[corbits-triage]

Triage requests changes:

• Conventions: added code matches a code pattern
  • apps/web/src/App.tsx:558-562 nested-ternary: Nested ternary; use if statements or a lookup.

Nothing triage asked to change still fails, so this request no longer stands.

This pull request is no longer ready to approve, so this approval no longer stands.

[TheGreatAxios]

Closing as needs further research. When the session check fails on page load with a 429, a 403, or a non-JSON reply, this PR shows the sign-in screen to someone who may still be signed in. main shows a loading screen in those cases instead. Reproduced in the browser 2/2 for each case. The findings and open questions are on CL-12203.