feat/account brackets - #50
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
avatarneil
added this pull request to stack #53
September 14, 2026 00:09
avatarneil
force-pushed
the
feat/account-brackets
branch
from
September 14, 2026 00:55
58add1f to
6f5ad04
Compare
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.
Account-backed brackets need durable storage and server-side ownership enforcement. This adds Postgres/Drizzle storage keyed to Clerk users, canonical pick validation, paginated CRUD routes, optimistic revision checks, and idempotent browser imports. It also introduces private/public snapshot storage for the sharing layer.
CI migrates an ephemeral Postgres service and tests ownership isolation, stale updates, import retries, snapshot isolation, and revoked links. The same tests passed against the new isolated Neon development branch. Database clients initialize lazily, so builds do not require production database credentials.
Repository guidance now uses GitHub native stacks (
gh stack).Deployment prerequisite: configure pooled
DATABASE_URL, supply directDATABASE_URL_UNPOOLEDfor migration execution, and runbun run db:migrateagainst the target database. Production hosting configuration is not included in this PR.