Couple side-effect claims with bounded queue ownership

When automation claims a case before an external side effect, the claim must define who owns the case next. Park it only for a bounded recovery window, then explicitly return rejected, ambiguous, and final attempts to the existing human queue.

Recheck eligibility immediately before provider submission; an earlier transactional claim cannot protect against assignment, help requests, or state changes during asynchronous preflight. Ambiguous acceptance is not safely retryable: keep it at-most-once, auditable, and human-routed.

This applies to routine recovery actions layered onto an existing queue. Exact park duration, attempt caps, and provider timeouts require system-specific evidence.