Stabilize sign-up session creation and post-auth redirect flow #3
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Auth confidence is too low: multiple e2e flows reached Secure Sign In immediately after a supposed successful sign-up instead of landing in Command Center.
Evidence
bun run test:e2ee2e/financials.spec.ts(shows not meaningful expense breakdown rows for bank pack filings)e2e/graphing.spec.ts(supports graphing compare controls and partial failures)e2e/graphing.spec.ts(distinguishes not meaningful metrics from missing data in the latest values table)Expected
Acceptance Criteria
Related Issues
Implemented the task-3 auth handoff fix locally and validated the core behavior.
What changed:
use-auth-handoffhook so auth pages wait forauthClient.useSession()to expose a real user before navigating.router.replace(...)redirects with session-confirmedwindow.location.replace(...).Finishing sign-in...UI state plus a 10s timeout recovery message.next, redirecting authenticated users away from auth pages, delayed session visibility, and timeout recovery.Verification:
bun x tsc --noEmit✅bun x playwright test e2e/auth.spec.ts✅ 10 passedLatest findings from downstream specs:
analysis.spec.tsauth setup now reaches the app shell in serial runs.financials.spec.tsno longer shows the original auth bounce; the remaining failure there is a separate strict-locator assertion onUnmapped / Residual.graphing.spec.tsstill has an intermittent signup stall where the page stays onCreate AccountwithCreating account..., meaning the signup request never completed and the new handoff logic never started.Assessment:
Fixed in
ac3b036- post-auth handoff now waits for session. Remaining signup stall under e2e load tracked in #12.