noyalib-failure-archaeologylisted

# noyalib Failure Archaeology The chronicle. Every entry is a battle already fought. Read the entry that matches your area BEFORE you touch it — several are booby-trapped with settled middles where the naive fix is one of the already-rejected paths. - Audience: mid-level engineer or Sonnet-class model. - Scope: `noyalib` v0.0.14 and its CI/supply chain. - Not this skill: live triage → `noyalib-debugging-playbook`; rules extracted from these incidents → `noyalib-change-control`. - Dated: 2026-07-08. > **Full chronicle in `reference.md`** — this file is the index and > the load-bearing DO NOT RETRY summary. Jump to > `reference.md#entry-N-...` for the full symptom / root cause / > evidence / DO NOT RETRY narrative of any entry. The SHA > re-verification one-liner for all 25 references and the "how to > add an entry" template also live in `reference.md`. ## How to use 1. Scan the **incident index** below by area. Each row points to `reference.md § Entry N`. 2. Read the matching entry end-to-end in `reference.md`. Respect **DO NOT RETRY**. 3. Cross-check your proposed change against the compact **DO NOT RETRY summary** further down. 4. If the issue recurs: append a new entry to `reference.md` (template there) and add a row here. --- ## Incident index | # | Entry (→ `reference.md`) | One-line | Status | |---|--------------------------|----------|--------| | 1 | [Cache-poisoning no_std mask](reference.md#entry-1--cache-poisoning-no_std-mask-v009--v0011) | Swat