From 8f3d303d7b9910d39ddac2a2a5d7450ca422751c Mon Sep 17 00:00:00 2001
From: Veillax <126523099+Veillax@users.noreply.github.com>
Date: Tue, 27 Oct 2026 16:54:23 -0600
Subject: [PATCH] Clarify delete cascade in API notes

---
 docs/api-automation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/api-automation.md b/docs/api-automation.md
index 6114836..e8d7036 100644
--- a/docs/api-automation.md
+++ b/docs/api-automation.md
@@ -33,4 +33,4 @@ level, and a server key has no user, so `/api/me` and other per-user routes refu
 - Keys are all-powerful within their scope (no read-only or per-resource scopes), and have no expiry.
 - `PUT` on ports replaces the whole object; omitted fields reset.
 - Site tokens are returned on create and, for admins, in `state`.
-- Deleting an edge/site does not check for ports that use it (the server cleans up or refuses; clients should order deletes).
+- Deleting an edge or site cascades silently (its ports and domains go with it, as do ports left with no target), so Terraform plans should not rely on dependent resources surviving.