ErasureExecuteResponse

What the door's act did: the completion, in full or as the no-op completion on an
already-erased subject. It is the door's only answer, since no door raises a principal refusal
(a caller who is not a system admin is answered 404 before dispatch). It stays a tagged enum
of one variant so the wire keeps "status": "completed": removing the tag would change the
body's shape for no behavioural reason.

{ "already_erased": true, "blob_strikes": [ { "blob_id": "8249af2f-dd23-416e-b9c4-6cb13a792190", "released": true } ], "estate_stragglers": 0, "event_id": "a7a26ff2-e851-45b6-9634-d595f45458b7", "redacted_hashes": [ "string" ], "resource_erasures": [ { "event_id": "a7a26ff2-e851-45b6-9634-d595f45458b7", "kind": "erasure", "resource_id": "4d5215ed-38bb-48ed-879a-fdb9ca58522f" } ], "slack_revocation": { "failed": 0, "not_attempted": 0, "queued": 0, "revoked": 0 }, "status": "completed", "targets": [ { "outcome": "string", "target": "string" } ] }