Fix critical auth, billing, and data-loss regressions - #119
Draft
cursor[bot] wants to merge 1 commit into
Draft
cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Cole Collins <DealPatrol@users.noreply.github.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Summary
mainis still at1524f3fwith prior critical-fix PRs (#88–#118) unmerged. This reapplies the validated fix set so production-bound code no longer ships with high-severity auth, billing, and data-loss bugs.Bugs and impact
/api/code-completionunauthenticated + cross-tenant leak — paid AI usable without auth;repo_filesfallback returned snippets across all tenants.userId— callers could skip billing or charge another user./api/build-appfalse success / public repos / no charge — generation/push failures still emitted SSEdone; repos created public; no credit charge/refund path.Root cause
Auth checks stopped at "is signed in" without ownership scoping; several paid routes trusted client-supplied identity or reported success before durable writes completed; credit mutations were read-modify-write without row locks / idempotency.
Fix
Cherry-pick of validated commit from PR #118 (
bb10a91) onto currentmain:(projectId, milestoneId, userId)Validation
node scripts/critical-regression-check.mjs— passedpnpm exec tsc --noEmit— passedlib/queries.ts)