cli-forge-resiliencelisted

> **Optimization:** This skill uses on-demand loading. Heavy content lives in `references/` and is loaded only when needed. > **Language rule:** Skill instructions are written in English. When generating user-facing output (reports, files, documentation), detect the project's primary language (from README, comments, docs, commit messages) and produce the output in that language. If the project is bilingual, ask the user which language to use before proceeding. # Forge Resilience — Prod-Parity, Failure Biology & Runbooks > *"A system survives production when it keeps homeostasis under stress, not when it merely passes happy-path tests."* ## Core Principle **Treat the system as an organism in an environment, not as a pile of files.** Production bugs usually appear when one of these mismatches exists: - **Genome mismatch** — contracts, ports, tags, secrets, roles, paths, or policies exist in multiple conflicting places. - **Membrane mismatch** — dev/staging do not reproduce the real boundary conditions of production. - **Homeostasis illusion** — the system looks healthy in one path, but another access path, operator path, or degraded state is broken. - **Immune weakness** — only happy-path tests exist, so negative cases, corrupted inputs, and drift survive until production. - **Hysteresis** — reruns, rollbacks, or partial failures leave dirty state behind (stale volume, cache, label, secret, ACL, artifact). - **Memory loss** — the incident is fixed once but never translat