Write Incident Report

Create a finished, evidence-backed incident report for this repository. Reports are operational records, not task summaries: distinguish observed facts from inference, record the actual failure path, document the fix and verification status, and leave future agents enough information to prevent recurrence.

Workflow

1. Inspect docs/incidents/README.md and at least two recent reports before writing.
2. Determine the next numeric incident ID from existing filenames and frontmatter. Do not reuse an ID or silently renumber an existing report.
3. Gather concrete evidence from code, logs, tests, deployment records, or user reports. Mark unknown facts as TBD; never fill gaps with plausible details.
4. Create docs/incidents/NNN-kebab-case-title.md with the exact frontmatter contract below and all required body sections.
5. Add one row to the incident table in docs/incidents/README.md.
6. Validate frontmatter, filename/ID agreement, index linkage, and Markdown formatting before handing off.