Separate the records
No generic work status replaces these owners. A ready-event replay cannot repeat the original email send.
Durable handoffs
Persist the operation and effect intent before realizing effects. Commit owner state, events and handoffs through the selected atomic boundary. Use accepted WorkGraph/native semantics for runtime work rather than private parallel admission or custody protocols. An awaiting caller can disappear after a successful commit. Recover using the same canonical operation and exact input identity before attempting another mutation. Readiness still needs current grants and runtime observations when the original task resumes.Coalescing without merging authority
Exact replay and host-authorized workflow grouping can avoid duplicate setup teams. Every distinct logical request still receives agent interpretation. After concrete package/subject/strategy selection, compatible requests can share one preparation. Shared preparation does not merge requester, grant, role, target, audience, deadline or result destination. Cancelling one waiter releases its interest and prevents its uncommitted role activation while preserving callbacks needed by surviving waiters. The preparation owner’s policy decides what happens when no waiters remain.Recovery cases
A credential challenge must itself be durably owned or explicitly invalidated after restart. Persisting setup state alone does not preserve a process-local browser transaction. Person-bound ceremonies may prohibit replacement until domain reconciliation.