refactor(api)!: drop the removed permission namespace and name fields

[whoAbhishekSah]

Summary

Final step of #1782 for the permission APIs. The deprecated namespace/name fields are deleted from the Permission message and PermissionRequestBody in proton (raystack/proton#500, numbers and names reserved), so key (service.resource.verb) is the only way a permission's identity travels on the wire in either direction. This lands the regenerated protos and stops populating the two response fields.

Depends on raystack/proton#500. The PROTON_COMMIT pin currently points at that PR's head commit; I'll move it to the proton main commit once it merges.

Why this is safe for clients

• Requests: the server stopped reading the two body fields in refactor(api): require permission key in create and update requests #1885, so senders of the old shape already get InvalidArgument today; proto3 ignores the unknown bytes either way.
• Responses: key round-trips losslessly since fix(permission): make the response key lossless and migrate its readers #1887 and every in-repo reader (reconciler, CLI, e2e) uses it. A client still reading namespace/name would now see them empty — this is the breaking part, so it should ride a minor version bump and be called out in the release notes.

Changes

• Makefile: bump PROTON_COMMIT; the regen also picks up the CheckOrganizationDelete RPC definition recently added on proton main — the handler embeds the generated unimplemented fallback, so that endpoint answers unimplemented until its implementation (feat(deleter): clear or report org delete blockers up front #1857) lands.
• proto/: regenerated.
• internal/api/v1beta1connect/permission.go: transformPermissionToPB no longer sets Name/Namespace; the key round-trip guard stays.
• internal/api/v1beta1connect/permission_test.go: expectations are key-only; the two "deprecated fields sent without key" cases are gone since the fields no longer exist.

Test Plan

• go build ./... and go vet ./... (including regression,e2e tags) pass
• go test ./internal/api/v1beta1connect/... passes
• golangci-lint run internal/api/v1beta1connect/... — 0 issues
• Full go test ./... — only the Docker-backed postgres/e2e suites fail locally (Docker not running); CI runs them
• CI regression + smoke green

🤖 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 25, 2026 6:59am

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes

  • Permission API responses now use validated permission keys consistently.
  • Create, update, list, and get responses no longer rely on deprecated name and namespace fields.

• Chores

  • Updated an internal dependency version to support ongoing compatibility and maintenance.

Walkthrough

Permission API tests no longer expect deprecated Name and Namespace fields. The permission key validation comment is clearer, with no executable change. The Makefile pins Proton to a different commit.

Changes

Permission response cleanup

Layer / File(s)	Summary
Permission API response expectations internal/api/v1beta1connect/permission.go, internal/api/v1beta1connect/permission_test.go	Tests for create, update, list, and get now validate Id, Key, and timestamps without deprecated fields. Invalid requests using deprecated fields without a key are no longer tested. The key validation comment is more explicit.

Proton dependency pin

Layer / File(s)	Summary
Proton commit pin Makefile	PROTON_COMMIT is updated to a different Proton commit.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: 🔵 Low · up to 8321f

This change removes deprecated permission fields from the API contract, so it should be published with a minor version bump and release-note entry. The code is otherwise mergeable, with explicit owner follow-up needed for release handling.

Suggested reviewers: amangit07

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

⚔️ Resolve merge conflicts 💡

• Resolve merge conflict in branch refactor/remove-deprecated-permission-proto-fields

---

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 32819377341

Coverage decreased (-0.002%) to 49.129%

Details

• Coverage decreased (-0.002%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	40520
Covered Lines:	19907
Line Coverage:	49.13%
Coverage Strength:	15.7 hits per line

---

💛 - Coveralls

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: f9c61842-ace1-4a8a-8307-91188d5cc6ba

📥 Commits

Reviewing files that changed from the base of the PR and between db2730d and 8321fdf.

📒 Files selected for processing (2)

• Makefile
• internal/api/v1beta1connect/permission.go

🚧 Files skipped from review as they are similar to previous changes (1)

• internal/api/v1beta1connect/permission.go

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.