feat(billing): apply claim-backed effective plan limits - #565
feat(billing): apply claim-backed effective plan limits#565seonghobae wants to merge 12 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Caution Review failedAn error occurred during the review process. Please try again later. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Buyer/access outcome
Refs #488. This Draft child of #564 applies durable Stripe entitlement claims to ScopeWeave's existing project/member plan-limit authorization without mutating
orgs.plan. A Free organization becomes effectively Pro only while at least one tenant-owned current claim head is entitled and unexpired; expiry or a revoke/deny head re-locks limits automatically.Exact current stack
feat/stripe-entitlement-claim-ledger-488@c176efda6abbd3796fab776484422bb8efc612a8;c9d21ade938bb7eaba89a37a271bb5eed464c17a;The current head is a non-destructive two-parent reconciliation of predecessor child
30d28a54543e05e9c54ca6db96fdfacef32a6885with exact current #564. It starts from the repaired claim-ledger parent tree and overlays only this slice's seven effective-plan paths, so #564's new claim-head composite tenant-integrity constraint and regression remain inherited without rewriting this child.Any parent/head movement invalidates this ancestry statement until freshly reconciled.
Authorization contract
orgs.plan;planOfconsumers use the bootstrapped server-owned claim database while caller-selected claim identities remain impossible.The production database enables SQLite foreign-key enforcement and the parent schema now binds every head to a decision for the same Subscription via a composite foreign key. This child does not weaken or duplicate that authority boundary.
Current exact-head evidence
Fresh repository-native workflows for exact head
c9d21ade938bb7eaba89a37a271bb5eed464c17aare non-passing while in flight:32345781144— pending;32345781142— queued; and32345781572— queued.There are no submitted reviews or review threads on this exact head. No predecessor-head, queued/pending, absent, synthetic, status-only, author-only, or model-only evidence is treated as approval.
Scope boundary
This slice applies claim authority only to existing commercial resource-limit gates. It does not change authentication, membership/RBAC, persist a plan rewrite, issue capabilities, or itself define buyer-visible billing status. #568 owns that public-status child and has been reconciled to this exact parent.
Remain Draft. Do not integrate independently of #564 and its prerequisite stack. Hosted exact-head deterministic/browser/coverage/security/dependency/supply-chain/review evidence must be terminal and current before integration.