fix: drop orgId from group RPCs

[rohanchkrabrty]

Summary

• Bumped @raystack/proton to the latest (0.1.0-f0b06e61...) in both web/sdk and web/apps/admin so the SDK regenerates without org_id on the affected group RPCs.
• Removed the now-invalid orgId argument from getGroup, updateGroup, listGroupUsers, removeGroupUser, deleteGroup, and setGroupMemberRole calls across the team views.
• Left ListOrganizationGroups and ListCurrentUserGroups untouched — they still take org_id.
• Verified the full pnpm build (SDK + admin) passes against the regenerated SDK types with no new type errors.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
frontier	Ready	Preview, Comment	Jul 14, 2026 10:07am

[coderabbitai]

Warning

Review limit reached

@rohanchkrabrty, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 36 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fe1c347f-281e-40ce-9950-6bac982ef779

📥 Commits

Reviewing files that changed from the base of the PR and between dab6e85 and 8631db1.

⛔ Files ignored due to path filters (1)

• web/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (6)

• web/sdk/client/views/teams/components/add-member-menu.tsx
• web/sdk/client/views/teams/components/delete-team-dialog.tsx
• web/sdk/client/views/teams/components/edit-team-dialog.tsx
• web/sdk/client/views/teams/components/remove-member-dialog.tsx
• web/sdk/client/views/teams/team-details-view.tsx
• web/sdk/package.json

---

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 29324173132

Warning

Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes.
Quick fix: rebase this PR. Learn more →

Warning

No base build found for commit dab6e85 on main.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 44.876%

Details

• Patch coverage: No coverable lines changed in this PR.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →

---

Coverage Stats

Relevant Lines:	37644
Covered Lines:	16893
Line Coverage:	44.88%
Coverage Strength:	12.54 hits per line

---

💛 - Coveralls