Preview deleting a node

Reports what deleting the node would remove, without deleting it. blockers lists what would refuse the delete (the root node, or an organization node, which is deleted through the organizations API); when any is listed nothing else is counted. Otherwise: subtree_size, the node and every node beneath it; roles, the role assignments made in the subtree counted by role, and assignments_total; identities_affected, and identities_losing_all_access, those holding no assignment anywhere else in the Environment; invites, the pending invitations there, by email; and directory_groups, the directory groups mapped there, by name. The same sets the delete removes. people is one page of the holders whose assignments go, one row per person by name, with via, their assignments that go as role at node, and pagination; q (name or email), role_id, page and take (up to 5000) narrow the page and never the counts. People are named only for a reader who may see the Environment's people (people_named: env_identities.view in the Console, and production_identities.access in a production Environment; identity.view for an API key; access administration at the node for a tenant's administrator); anyone else gets the counts and an empty page, whatever the query. Read-only. Send version as If-Match on the delete. Gated as the delete is: hierarchy.manage on the node. Returns 404 when the node is not found in this Environment.