unblock

Topics in the source

• Unblock Stalled or Failing Work
• 1. Verify It Is Actually Blocked
• 2. Diagnose by Failure Class
• Parent-operation recovery
• Missing pull-request CI
• Missed completion events
• Tool-launch failures
• Build wrapper timeouts

Use this skill to restore a task, CI run, merge queue entry, or deployment that has actually stalled or failed. When an environment disappears or is about to be retired, preserve stranded work using references/stranded-work.md before resuming delivery or allowing cleanup. Before intervening, read the live state of the job, queue, or target resource: 1. Normal progress needs no action: A build, test suite, or external store review running within its expected duration is not blocked. Do not cancel and restart healthy in-flight work. Recovery eligibility belongs to the failure state, not the target ID: re-read the exact state that justified recovery immediately before the write and skip it if that state no longer holds. 2. Never resend an uncertain mutation blindly: Follow the duplicate-safety recovery contract: reconcile potentially harmful duplicate effects, while a documented duplicate-safe refresh can recover with bounded serial retries before its output expires. 3. Discard self-imposed blocks: A hypothetical third-party ToS question, an unscored civil risk (../challenge/references/risk.md), or a local convention that protects neither user data nor authorized spend is not a real b

This is an excerpt. Refer to the complete source and its current requirements.