docs(permissions): the walled package refusal on the package delete and permission-set provenance pages

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015JgoXpZUGtNxnMDvRZsKzP

Author: claude

content/docs/api/metadata-api.mdx

@@ -123,7 +123,9 @@ Get package details.
 
 ### `DELETE /packages/:id`
 
-Uninstall a package.
+Uninstall a package. Under a `group` or `isolated` tenancy posture, a package
+holding positions or permission sets is the platform operator's to delete: any
+other caller is refused `403 PERMISSION_DENIED` (ADR-0131 D3).
 
 ### `PATCH /packages/:id/enable`
 

content/docs/permissions/permission-sets.mdx

@@ -348,7 +348,11 @@ position/user bindings, and its pending audience-binding suggestions in the
 same request (no ghost grants); the uninstall response reports the revocation
 under `data.persisted.cleanups` (the dispatcher's `/packages` domain answers
 the route, and it nests the protocol's uninstall report under `persisted`).
-Environment-authored sets and other packages' rows survive.
+Environment-authored sets and other packages' rows survive. Under a `group` or
+`isolated` tenancy posture, removing a package that carries positions or
+permission sets is the platform operator's (ADR-0131 D3): that delete, and an
+`install-local` install, upgrade or uninstall of such a package, refuse any
+other caller `403` before anything changes.
 
 ## One authoritative store — the record is a projection (ADR-0094)