reference
SupportOS durable case lifecycle
Revision-fenced snooze, automatic resume, and archive semantics.
Snooze and archive mutations derive authority from server context, require an idempotency key and current case revision, and append immutable events. Snooze persists the prior service state and atomically emits a fenced unsnooze job. Hosts must register the matching durable handler before enabling automatic resume. Archive is terminal and cannot be used as a substitute for erasure.