Skip to content

reliability: add warm-pool outbox only for a proven recovery gap #2332

Description

@Brad-Edwards

Follow-up to #2076. Move warm-pool lifecycle transitions to the shared transactional outbox only if the existing reconciler and durable state cannot recover a demonstrated lost or duplicated operation.

Acceptance

  • Reproduce the failure with the current CLAIMED and RETIRING recovery path.
  • Record the state change and retryable intent atomically without adding a second lifecycle authority.
  • Prove restart, duplicate dispatch, and partial failure converge without orphaned warm ranges.

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    deferredOptional work held until a concrete need is demonstrated

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions