chaos-injectorlisted

# Chaos Injector An L2 Truth-Execution skill. It runs a controlled failure experiment against a test environment and records whether the system under test survived, degraded gracefully, or broke in a way that extended beyond the intended blast radius. The output becomes a resilience signal that `release-decision-engine` weighs into the GO/CONDITIONAL/BLOCKED call. Unlike `regression-test-runner` (which exercises the happy path) or `uat-executor` (which exercises real flows), this skill **breaks things on purpose**. Everything in this file — the preflight checks, the profile gates, the mandatory recovery, the blast-radius abort — exists so "on purpose" doesn't slip into "by accident". ## When You're Invoked - **PIPELINE-3 step 2 (parallel)** — alongside `uat-executor` and `e2e-test-writer`'s generated runs, when the domain is financial / healthcare and the release pipeline is PIPELINE-6. - **On demand** as `/vibeflow:chaos-injector <profile> --env <env>`. - **From `release-decision-engine`** when the decision engine needs a fresh chaos signal before a high-stakes release. ## Input Contract | Input | Required | Notes | |-------|----------|-------| | System info | yes | Target environment + its component manifest (from `env-setup.md` / `environment-orchestrator`'s `setup-manifest.json`). The skill refuses to inject against a target it didn't see the topology for — blind blast-radius is unsafe. | | Chaos profile | yes | One of `gentle / moderate / brutal`. Each prof