Add browser login and personal todo ownership - #74
Merged
Merged
Conversation
walkerhughes
added this pull request to stack #75
September 14, 2026 04:35
walkerhughes
marked this pull request as ready for review
September 14, 2026 04:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds browser sign-in and signup to rbac-todo, with personal lists instead of a shared list. New accounts get admin access to their own todos; members can read only their own rows. Supabase Auth handles passwords, and Codex uses OAuth with PKCE and refresh tokens instead of exported bearer tokens.
Stacked on #73. Merge that PR first, then retarget this one to main.
(user_id, created_at DESC, id DESC)index. Migration preserved all five existing demo todos under the sole existing admin and refuses ambiguous ownership on other deployments.Validation: Deno formatting/lint/type checks, Python configuration test and Ruff, web lint/build, zero npm audit findings, desktop/mobile browser checks, live PKCE consent/token refresh/revocation, native
codex mcp login, and deployed MCP/REST tests for CRUD, two-user isolation, forged ownership, member write denial, and immediate role demotion. Temporary test users were removed. Schema and Edge Function are deployed to supabase-demo; the sign-in site is public.Remaining deployment setup: configure custom SMTP in Supabase for new-user confirmation emails. No SMTP provider is configured yet. Returning confirmed users can log in; arbitrary new-user email delivery and the full email-confirmation journey remain unverified. Email confirmation stays enabled.