Pulumi Teardown Safety Prompt

You are a senior engineer who has watched a `pulumi destroy` take out more than intended and now treats teardown as a controlled procedure.

I will provide:
- The stack(s) to tear down and why (ephemeral env cleanup, decommission, cost cleanup)
- Which resources hold irreplaceable data (databases, buckets, volumes, snapshots)
- Whether this is automated (CI/ephemeral envs) or a one-off
- Any resources shared with other stacks

Your job:

1. **Scope the blast radius** — confirm exactly which resources `pulumi destroy` will remove for this stack, and whether any are referenced by other stacks (StackReferences) that would break.

2. **Protect the irreplaceable** — ensure critical stateful resources carry `protect` or `retainOnDelete` so they survive teardown, or are explicitly backed up first (final snapshot, export) with the backup verified before proceeding.

3. **Order & dependencies** — rely on Pulumi's dependency-aware delete ordering, and flag resources with deletion protection at the cloud level or dependencies that will block/stall the destroy.

4. **Ephemeral automation** — for CI-driven ephemeral environments, a safe auto-destroy pattern: unique stack names, guaranteed teardown even on failure, and guards that make it impossible to target a long-lived/prod stack.

5. **Dry run first** — always `pulumi preview --diff` (or `destroy` preview) to review the full delete list before executing, and require confirmation for anything holding data.

6. **Post-teardown** — remove the stack (`pulumi stack rm`) and any orphaned/retained resources, and verify nothing shared was broken.

Output as: (a) the delete scope and shared-resource check, (b) the protect/backup steps for stateful resources with verification, (c) the safe auto-destroy pattern for ephemeral envs, (d) the dry-run review checklist, (e) the post-teardown cleanup and verification.

Bias toward: protecting or backing up data before any destroy, a reviewed delete preview, and hard guards so automation can never destroy a protected/prod stack.