Close out the node-addressing project

.drive/PLAN.md

@@ -0,0 +1,17 @@
+# Planning failure modes
+
+Checks to run when decomposing a project into slices.
+
+- **Every slice serves the project's purpose.** Before the plan is final,
+  read each slice against the spec's purpose sentence. A slice that came out
+  of the same design discussion but solves a different problem is its own
+  project or a deferred item, not a slice. Added 2026-10-28: the
+  node-addressing project carried a cascading Branch delete and
+  `prisma branch delete` because the discussion that started it was about
+  teardown. Neither was about addresses; Will canceled both.
+- **Read the owning team's recorded decisions before planning a slice in
+  their repository.** A slice in another team's repository (pdp-control-plane,
+  prisma-cli) needs that repository's specs and decision records read first.
+  Added 2026-10-28: the cascading Branch delete was planned without reading
+  pdp-control-plane's Branch spec, which records the platform team's decision
+  against a cascade. The conflict surfaced only when the slice started.

.drive/PROJECT.md

@@ -0,0 +1,12 @@
+# Project conventions
+
+- **Long-lived docs** go into the existing design docs, not a per-project
+  folder: decisions into `docs/design/90-decisions/` as new or amended ADRs,
+  terms into `docs/design/03-domain-model/glossary.md`, user-facing behaviour
+  into `docs/guides/` and `skills/`. Each slice lands its own docs, so
+  close-out usually migrates nothing.
+- **Transient** at close-out: everything under `.drive/projects/<project>/`,
+  including spikes' findings notes, QA records and review files. Their
+  evidence belongs in the slice's PR description.
+- **Tracking:** Will tracks Composer work outside Linear. Close-out PRs
+  reference no Linear Project.

.drive/deferred.md

@@ -245,4 +245,9 @@ ADR-0053 (the commands). What we deliberately didn't do:
 
 # Node addressing — deferred (2026-10-22)
 
-- **`prisma deploy delete @<stage>:<address>`: tear down a subtree.** Not built: `project delete`, `branch delete` and platform deletes by address cover every teardown scenario we found. Its only own jobs are emptying a stage while keeping its Branch (equivalent: `branch delete`, then redeploy) and resetting one module (equivalent: a few platform deletes, then redeploy). Design if it is ever needed: follow containment (the node and everything its modules provisioned), not dependency edges; delete compute before data and wait until each instance can be deleted; list nodes outside the subtree that depend on it and warn without blocking; leave the stored topology and deploy state alone so the next deploy rebuilds it; a subcommand of `deploy`; production must be named explicitly. Origin: node-addressing design discussion.
+- **`prisma deploy delete @<stage>:<address>`: tear down a subtree.** Not built: `project delete`, the `destroy` operation and platform deletes by address cover every teardown scenario we found. Its only own jobs are emptying a stage while keeping its Branch (equivalent: `destroy`, then redeploy) and resetting one module (equivalent: a few platform deletes, then redeploy). Design if it is ever needed: follow containment (the node and everything its modules provisioned), not dependency edges; delete compute before data and wait until each instance can be deleted; list nodes outside the subtree that depend on it and warn without blocking; leave the stored topology and deploy state alone so the next deploy rebuilds it; a subcommand of `deploy`; production must be named explicitly. Origin: node-addressing design discussion.
+
+# Node addressing — deferred at project close (2026-10-28)
+
+- **Stage removal through the platform: a cascading Branch delete in the Management API and `prisma branch delete`.** Canceled by Will, 2026-10-27: it is not about addresses. pdp-control-plane's Branch spec also records a decision against a cascading Branch delete. Removing one environment stays the `destroy` operation. Origin: node-addressing plan.
+- **Remove CI's `deleteProjectDeep` workaround** in `scripts/ci-cleanup-utils.ts`. It retries `project delete` after a 409 caused by live compute, which the platform no longer returns: `project delete` succeeded while services ran in the node-addressing QA. Not done because it is CI cleanup, not addressing. Origin: node-addressing plan.