Delete actions across SendLit #152

Parent tracker for the missing delete actions.

Already supported (API + MCP + dashboard)

Contacts (one at a time), contact tags (per contact), templates, signup forms, media, segments, sequence emails, team API keys, ESP configs, teams (archive), org members, reputation connections, suppressions (release).

Missing

• Delete broadcasts (with archive for sent ones) #147 Delete broadcasts (archive for sent ones). The API exists but has no guard, and deleting cascades delivery history.
• Delete sequences #148 Delete sequences. The API exists but has no guard, and deleting drops enrolled contacts.
• Bulk delete contacts #149 Bulk delete contacts
• Delete (and rename) tags team-wide #150 Delete (and rename) tags team-wide
• Delete an organization from the dashboard #151 Delete an organization from the dashboard
• Delete account #134 Delete account (GDPR)
• ESP delete button does not work #12 ESP delete button does not work
• Delete MediaLit assets when their resource is deleted #157 Delete MediaLit assets when their resource is deleted

Cross-cutting rules

• Every delete goes through the REST API, the OpenAPI docs, MCP and the dashboard together.
• Confirm with a shadcn AlertDialog. For bulk or org-level deletes, ask the user to type the name to confirm.
• Never delete reporting or suppression data as a side effect of deleting a resource. Archive anything that has sent mail.
• Delete the MediaLit assets a deleted resource leaves unreferenced (see Delete MediaLit assets when their resource is deleted #157), but never assets used by mail that has already been sent.
• Tests for each delete must check that the MediaLit files the deleted entity owned are deleted (MediaLit client mocked), and that shared or sent-mail media is kept.
• Emit *_deleted events through captureEvent, with ids only.