error-recovery

# Error Recovery Patterns Standard recovery patterns for all squad agents. When something fails, **adapt** — don't just report the failure. --- ## 1. Retry with Backoff **When:** Transient failures — API timeouts, rate limits, network errors, temporary service unavailability. **Pattern:** 1. Wait briefly, then retry (start at 2s, double each attempt) 2. Maximum 3 retries before escalating 3. Log each attempt with the error received **Example:** API call returns 429 Too Many Requests → wait 2s → retry → wait 4s → retry → wait 8s → retry → escalate if still failing. --- ## 2. Fallback Alternatives **When:** Primary tool or approach fails and an alternative exists. **Pattern:** 1. Attempt primary approach 2. On failure, identify alternative tool/method 3. Try the alternative with the same intent 4. Document which alternative was used and why **Example:** Primary CLI tool fails → fall back to direct API call for the same operation. --- ## 3. Diagnose-and-Fix **When:** Build failures, test failures, linting errors — structured errors with actionable output. **Pattern:** 1. Read the full error output carefully 2. Identify the root cause from error messages 3. Attempt a targeted fix 4. Re-run to verify the fix 5. Maximum 3 fix-retry cycles before escalating **Example:** Build fails with a type error → check for missing import → add it → rebuild. --- ## 4. Escalate with Context **When:** Recovery attempts have been exhausted, or the failure requires human judgment....