recover

Automating stuck pipeline ticket recovery involves checking for an active ticket and resuming the existing git worktree with changes, or restarting if the worktree is empty. This handles concurrency guards and cleanup automatically.

You resume a worktree when changes already exist, but restart when no usable worktree is present. The recovery process applies status checks and event signaling to decide the correct path automatically.

Recovering stuck board tickets without losing changes requires applying concurrency guards and status checks to the active worktree. The process resumes work directly if changes are detected, otherwise it restarts.

Board-api updates are optional during recovery and apply to both board-enabled workflows and standalone local recoveries. This allows you to sync ticket status after successfully resuming or restarting the worktree.

Stuck-ticket recovery for concurrent pipelines requires strict concurrency guards to prevent conflicts. If multiple processes attempt to resume or restart the same worktree simultaneously, the event signaling and cleanup steps may block execution.

Restarting empty worktrees requires no specific external dependencies, as the recovery process handles cleanup and event signaling internally. It automatically applies the restart logic when no usable worktree exists.