[Prashansa-K]

Declares the Management API permissions for the project network commands: vanity-subdomains (get, check-availability, activate, delete), ssl-enforcement (get, update), encryption (get-root-key, update-root-key), network-bans (get, remove), network-restrictions (get, update) and postgres-config (get, update, delete). Each leaf composes the project-ref picker and the linked-project cache.

Shared change: postgresConfigRead and postgresConfigWrite are new blocks in postgres-config.shared.ts, next to the helpers that issue the calls (postgres-config reaches the API through executeRaw on the typed client, so the drift matcher resolves them). get uses the read block, update the read block (only when --replace-existing-overrides is false) plus the write block, and delete both.

Conditions declared

• network-restrictions update: is on --append selects the POST /apply or the PATCH.
• ssl-enforcement update: the PUT is declared once per switch (--enable-db-ssl-enforcement, --disable-db-ssl-enforcement), each with is: true.
• vanity-subdomains activate and check-availability: the call is declared for --desired-subdomain present and for oneOf: [""], because the handlers send an empty value to the API. Both also compose upgradeSuggestion.

Findings

• v1-get-pgsodium-config is a GET that needs project_admin_write, and check-availability is a POST that needs vanity_subdomain_write.
• postgres-config makes no restart call and has no delete endpoint: delete is a GET followed by a PUT, and --no-restart only shapes the PUT body.
• network-bans remove fills the linked-project cache even when an IP is invalid, while network-restrictions update and ssl-enforcement update validate before resolving the ref and fill nothing. postgres-config update only checks that each --config value is a key=value pair before resolving; an unknown key is rejected after the ref resolves and the GET, so the cache is still filled. encryption resolves the ref outside the cache-fill scope.
• The SIDE_EFFECTS docs pointed the cache at ~/.supabase/<workdir-hash>/, described a .supabase/config.json that nothing reads, and omitted the picker and cache-fill routes. They now match the code.

Not covered

• The experimental gate is not modelled; declarations describe a run whose gate is open.
• ssl-enforcement update over-declares when both switches are true, a run that fails before any call.
• Picker, cache and upgrade-lookup entries carry a context, so they are checked by request sequence rather than by the exact drift check. Dropping linkedProjectCache from vanity activate or check-availability fails no test, because upgradeSuggestion also declares v1-get-project.
• --switch=false and --desired-subdomain= are exercised with parsed values, not through the flag parser.
• No new entries in OPERATIONS_WITHOUT_FGA.

🤖 Generated with Claude Code

[github-actions]

🤖 AI Review

Both independent reviews completed and reported zero findings. Reading the permission declarations, corresponding handlers, shared picker/cache logic, and trusted conventions revealed no additional concrete defects. No fundamental conflict was identified in the supplied next-branch context. Runtime tests were not run.

Findings

No issues found.

Stats

Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · Refuted: 0 · Uncertain: 0

---

Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: auto · Workflow run

This review runs once per PR. A maintainer can request another with a /ai-review comment.

[Coly010]

LGTM, thanks! one small wording nit inline, happy for you to take it or leave it