Create a DeferEvent action. The event is published and folded but not persisted. Rejection and idempotent-reply folds should preserve state, because recovery cannot replay a deferred event.

Create a RunAsync effect (a "mini saga" without persistence) from an INSPECTABLE description object. The runner registered via `InitAggregateWithEffects` executes it and self-dispatches the resulting command. EPHEMERAL (not journaled, so a crash mid-flight loses it) and TOTAL (the runner must map failure to a command). See EventAction.RunAsync.

Create an IgnoreEvent action (command is ignored, no event produced)

Create a PersistEvent action (event will be persisted and published)

Create a PersistAllEvents action: all events from this command persist as one journal AtomicWrite (all-or-nothing), with sequential versions. State updates and publishes happen only after the whole batch is durable.

Create a PersistAndSnapshot action: persist the event, then save a manual snapshot once it is durable - independent of the SnapshotPolicy cadence.

Persist the event when `shouldPersist` is true; otherwise Defer it - the event is still published and folded but is not written to the journal or sent through a projection. Its fold should preserve the current state. The idempotent "emit this verdict, but only write it once" shape, e.g. re-approving an already-approved aggregate: `PersistConditionally(state.Approval != Approved, new Approved(id))`.