Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

docs(authz): clarify proxy namespace and admin roles

Address review feedback on the custom resources doc:

- Proxy namespace: state that the name is a free choice. The generator
  mirrors every custom permission onto app/project and app/organization
  regardless of namespace, so there is no convention to follow.
  user/project is just the example.
- Admin roles: use the titles and names from PredefinedRoles everywhere,
  so Owner (app_organization_owner), Admin (app_organization_manager),
  Project Owner (app_project_owner), and platform admin are no longer
  ambiguous.
- Built-in role permissions: clarify that "already had" means the
  predefined role defaults, not the base schema.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>