Skip to content

Plan Phase 5: SuperTokens client integration (v1.9) - #12

Open
NeverEndingCode wants to merge 1 commit into
mainfrom
v1.9-phase5-plan
Open

Plan Phase 5: SuperTokens client integration (v1.9)#12
NeverEndingCode wants to merge 1 commit into
mainfrom
v1.9-phase5-plan

Conversation

@NeverEndingCode

Copy link
Copy Markdown
Owner

Docs only. Written at the end of a session so the next one can start cold.

Deliberately a plan rather than a half-built implementation — partial frontend auth is worse than none.

Task 1 needs no code: drive the SuperTokens login by hand with two curl calls against production dual, and check user.id comes back as github:37058311 rather than a UUID. That is the first time the signInUp mapping ever runs for real — it is exhaustively unit-tested, but dual does not exercise it, because the client still logs in through passport. If Task 1 fails, everything after it is premature.

Records the decision to hand-roll the three fetch calls rather than adopt supertokens-web-js, whose signOut() targets the /auth/signout v1.8 deliberately removed.

Also carries forward the constraints a fresh session would otherwise rediscover the hard way, and lists the five documents that currently say supertokens mode is unusable and must be un-blocked together.

🤖 Generated with Claude Code

Written at the end of a session so the next one can start cold. Deliberately a
plan and not a half-built implementation - partial frontend auth is worse than
none.

Task 1 needs no code at all: drive the SuperTokens login by hand with two curl
calls against production dual, and check user.id comes back as
github:37058311 rather than a UUID. That is the first time the signInUp mapping
ever runs for real - it is exhaustively unit-tested, including the ordering
guarantee, but dual does not exercise it because the client still logs in
through passport. If Task 1 fails, everything after it is premature.

Records the decision to hand-roll the three fetch calls rather than adopt
supertokens-web-js, whose signOut() targets the /auth/signout that v1.8
deliberately removed, and which pulls in more surface than the allowlist
permits.

Also carries forward the constraints a fresh session would otherwise have to
rediscover: users.id never changes, nobody gets logged out, the allowlist IS
the SuperTokens HTTP surface, signinup takes only the redirect flow, and the
five documents that currently say supertokens mode is unusable and will need
un-blocking together.

Docs only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant