Team Deletion

Team deletion is conservative. DELETE /teams/{id} checks the current region for team-owned resources and returns 409 conflict while any blocking resource remains.

The response contains error.details.blocking_resources with a category and count. Clear those resources before retrying deletion.

Blocking categories include active sandbox/lifecycle records, templates and in-progress template captures, credential sources and bindings, API keys, team-scoped SSH public keys, RootFS filesystems/heads/snapshots/objects and deletion work, team quota policies, and any discovered non-metering regional table with a team_id column. Team membership and admission bootstrap state are removed by the final team transaction.

Historical metering and bounded operational delivery records are retained by policy and do not block deletion. When present they appear in error.details.retained_resources with the response's retention-policy text.