chaos-testlisted

# Chaos Test — Resilience Gap Analysis Scan the codebase for failure modes that would surface under real-world stress: network partitions, dependency outages, slow consumers, and burst traffic. ## Usage ``` /chaos-test # full scan of staged changes and key integration points /chaos-test <path> # target a specific file or directory /chaos-test --service <name> # focus on a named external service dependency ``` ## Behavior ### Step 1 — Identify integration boundaries ```bash # Find outbound HTTP calls, queue producers/consumers, DB calls, cache hits grep -rn "fetch\|axios\|http\.\|requests\.\|redis\|pg\.\|mysql\|amqp\|kafka" \ --include="*.ts" --include="*.py" --include="*.go" --include="*.js" \ -l . | head -30 ``` ### Step 2 — Check each boundary for resilience controls For every integration point found, verify presence of: | Control | What to grep for | Risk if absent | |---|---|---| | Timeout | `timeout`, `AbortController`, `signal` | Hangs under slow upstream | | Retry | `retry`, `backoff`, `attempt` | Single transient failure = hard failure | | Circuit breaker | `opossum`, `cockatiel`, `breaker`, `circuitbreaker` | Cascading failure under sustained outage | | Fallback / degraded mode | `fallback`, `default`, `catch` returning a stub | No graceful degradation | | Rate-limit handling | `429`, `RateLimitError`, `retry-after` | Thundering herd kills upstream | | Bulkhead / concurrency cap | `semaphore`, `pLimit`, `asyncio.Semaphore` | Si