Handling Destructive Changes Coordinate metadata deletion against a Salesforce org via the destructiveChanges manifest. Runs in three phases: scope → validate → execute, with stricter guardrails for production. Phase 1 — Scope the deletion Step 1a — Gather the components to remove Ask the user (or infer from context) which components to delete. For each, capture: - Metadata type (e.g. , , , , ) - API name (e.g. , , ) Step 1b — Local dependency scan (best-effort) Before generating the manifest, scan the local project for references to each component. Use Grep over : If references are found: -…