[lukemaj]

What: A paired browser whose cookie renewal fails briefly at startup now shows a reconnecting state and retries, instead of asking to pair again.
Why: Startup caught every renewal failure as null and returned requires-auth, even when the durable renewal secret was still valid and the failure was transient.
So what: Luna review and CI, then the backlog coordinator merges.

Problem

apps/web/src/environments/primary/auth.ts turned any renewal failure (network error, HTTP 5xx, renewal-store failure) into requires-auth, so a returning paired browser saw the pairing prompt during a short server or network hiccup.

Fix

• Typed transient renewal failures return a retryable startup result with capped exponential delays (500, 1000, 2000, 4000, then at most 5000 ms).
• The root route shows a reconnecting surface and invalidates the router after the delay, cleaning up its timer on state change or unmount.
• The chat route keeps the requested route during retry; the pair route handles the new variant.
• Definitive renewal rejection and an absent enrollment still require pairing; explicit pairing intent is preserved.
• packages/client-runtime/src/connection/supervisor.ts is untouched (PR fix(auth): pace renewal when the client clock is ahead #473 owns its pacing).

Upstream

No matching fix in pingdotgg/t3code; renewal is fork-owned. Details: #330 (comment)

Proof

• vp test run apps/web/src/authBootstrap.test.ts: 38 passed (worker, and again by the coordinator after rebasing onto 7f300491d3).
• The network, HTTP 500 and storage regressions fail against the original auth.ts with requires-auth instead of retryable; definitive rejection passes on both.
• Tests use the real SessionRenewal with fake transport and storage boundaries.
• Targeted lint and apps/web typecheck passed (worker); scripts/fork-check.sh OK after rebase.
• Not exercised in a real browser; the rendered reconnecting timer is covered only through the bootstrap path.

Elon record

• Requirements and who asked: fix(web): retry transient cookie renewal during startup #330, a follow-up from Paired desktop and browser sessions renew instead of closing at 30 days #323's design review; the user asked on 2026-10-18 to clear discussed backlog work.
• Deleted: a new retry service; the existing renewal service and startup result type carry the retry state.
• Bottleneck: startup's catch-to-null in auth.ts.
• Checked myself: the coordinator reran the focused test file after rebase and the fork check.

Closes #330

Implemented by GPT-6.1 Sol (Codex harness in T3 Code). Committed, rebased and opened by Claude Opus 5.5 (Claude Code in T3 Code) because the worker's git commit was blocked by a ContextMD hook.

🤖 Generated with Claude Code

[lukemaj]

Luna review round 1 at 230a6a9: CHANGES REQUESTED

• Blocking — fork registration is missing. This PR ships work for the tracked paired-session-renewal part, but docs/map.md still records only %% PRN: #323 #336 and does not add PR #504 after the primary ref. docs/fork-features.md also links this part to Issue fix(web): retry transient cookie renewal during startup #330 but still lists only PR feat(auth): renew active paired sessions with device authority #334. The repository rules require both registrations for a PR shipping tracked-part work; update the map and feature record so maintainers can find this implementation from the part.

The requested auth behavior otherwise checks out: the server maps a rejected renewal secret to 401 / RenewalRejected, which exits retry and requires pairing; transport/storage failures and server errors become ConnectionTransientError; retry delays cap at 5000 ms and reset after a non-retryable outcome; the root retry timer cleans up on state change or unmount; and route invalidation preserves the active location. Mobile does not use the web root bootstrap path, and desktop uses the shared web root, so the web-only startup scope is consistent. The focused tests cover bootstrap results, real renewal transport/storage recovery, definitive rejection, capped/reset delay, concurrency, and explicit pairing intent. Fork allowlist registration includes the added web files.

[lukemaj]

Luna review round 2 at 96be3c6: APPROVE