feat(deleter): serve CheckOrganizationDelete for delete eligibility

[whoAbhishekSah]

Part of #1837. Top of the stack, based on #1893. Proto: raystack/proton#499.

The product decision for the delete button: disabled while any of the three blockers exist (active subscription on a paid plan, unpaid invoice, negative token balance), enabled on the unused-tokens case and the happy path. The client cannot compute the paid-plan case itself — it does not know the server's configured standard plan — so this adds a read-only check RPC.

CheckOrganizationDelete returns the same blocker list that DeleteOrganization's failed_precondition carries, without changing anything. Each blocker has type (the reason), subject (the blocking entity's id), subject_type (what kind of entity that id is: billing_subscription, billing_invoice, or billing_account), and message.

• No subscription gets canceled (the delete only cancels standard-plan subscriptions once everything else is clear).
• Invoice rows are read as they are — no forced provider sync per check, since clients may call this on every settings page view. The answer is advisory; the delete still re-checks against fresh provider data.
• Requires the same delete permission on the org as the delete itself.
• A missing org returns not_found.

The SDK will switch its delete button to this RPC once the proton npm package ships with it; until then #1881 greys the button on the invoice case only.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
frontier	Ready	Preview	Aug 24, 2026 8:23am

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 719f2937-c0f9-4fd1-9684-4be3b6f6a6ba

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coveralls]

Coverage Report for CI Build 32705926072

Coverage increased (+0.05%) to 49.131%

Details

• Coverage increased (+0.05%) from the base build.
• Patch coverage: 18 uncovered changes across 3 files (88 of 106 lines covered, 83.02%).
• 1 coverage regression across 1 file.

Uncovered Changes

File	Changed	Covered	%
core/deleter/service.go	83	70	84.34%
pkg/server/connect_interceptors/authorization.go	4	0	0.0%
internal/api/v1beta1connect/deleter.go	19	18	94.74%

Coverage Regressions

1 previously-covered line in 1 file lost coverage.

File	Lines Losing Coverage	Coverage
core/deleter/service.go	1	80.28%

---

Coverage Stats

Relevant Lines:	40522
Covered Lines:	19909
Line Coverage:	49.13%
Coverage Strength:	15.7 hits per line

---

💛 - Coveralls

[rohilsurana]

Stack-aware review (base org-delete-check-proto). Main thing is the check vs delete mismatch below; the other two are small. I dropped an earlier note about the NotFound mapping: it is only reachable for non-existent orgs, which a real client will not hit.

[rohilsurana]

Re-review after the fix commits. The err-before-loop fix and the shared paidPlans/balances cache both look good, and the negative-total case now lines up. I left the credit-covered greying alone since you already flagged it as a deferred, safe-direction gap. Two small cleanup/doc notes.