noyalib-change-controllisted

# noyalib — Change control rulebook > **Reference material** (full 9-row change taxonomy, complete CI gate > inventory, long-form v0.0.9 → v0.0.11 cache-poisoning narrative, > jargon glossary): see `reference.md` in this directory. Load when you > need the exhaustive table for §1, the gate-name inventory that fills > in §5, or the incident write-up that §4 summarises. Repo: `github.com/sebastienrousseau/noyalib` — pure-Rust YAML 1.2 library, zero `unsafe`, release branch `feat/v0.0.14`. Ground truth: `PLAN.md` (§ Working invariants), `CONTRIBUTING.md`, `GOVERNANCE.md`, `doc/POLICIES.md`, `doc/adr/0003-zero-unsafe-policy.md`, `.github/workflows/ci.yml`, `RELEASE-NOTES-v0.0.*.md`. If this skill and those files disagree, the files win — re-verify with the commands in "Provenance and maintenance" at the bottom. Jargon (ADR, MSRV, release branch, non-negotiable, satellite crate) is defined once in `reference.md` §R1 and used verbatim below. --- ## 1. Classify the change first Every change belongs to exactly one row. Pick the row before you write code — the row tells you which gates to satisfy and whether an ADR is required. Compact summary here; the exhaustive 9-row table (all classes, triggers, branch prefixes, ADR triggers, extra gates) lives in `reference.md` §R2. | Class | Branch prefix | ADR? | Signature gate beyond default | |---|---|---|---| | **Bug fix** | `fix/` | No | Regression test in same commit. | | **Feature** | `feat/` | **Yes** | Design issue first; changel