incidentlisted

Write the entry when the problem is fixed, not at the end of the session — CLAUDE.md and `incidents/index.md` both call this out: the failed attempts are the part that's gone forever if it's left until later. Run this proactively, right after landing a fix, without waiting to be asked. 1. **Determine the next number.** Read `incidents/index.md`'s table, take the highest existing `I{nnn}`, increment. Don't guess or reuse a number. 2. **Create `incidents/I{nnn}-{slug}.md`** from `incidents/_template.md`. Fill every field from what actually happened this session, not a generic description: - **Area** — one of the fixed vocabulary in the template's header comment and the index's "Areas" section: `rpm-ostree`, `flatpak`, `toolbox`, `gnome`, `hardware`, `network`, `etc`, `backup`, `agent`, `boot`. - **Symptom** — what was observed, verbatim where possible (error text), not the diagnosis. - **Cause / Fix** — what turned out to be true, and the exact copy-pasteable fix. - **Tried first** — what didn't work and why it looked plausible. This is the field most likely to be skipped under time pressure and the one the template calls "usually the most valuable paragraph in the file." Don't skip it. - **Reversibility** — name the actual layer: `rpm-ostree` rollback, `etckeeper` diff, `/var/home` backup, or none (say what the exposure was if none). - **Captured in** — the script this incident got automated into, o