docs: first retro, and the ADR the history rewrite should have had

Retro 2026-08-09, the first one under the framework. Main finding: six silent failures in nine days - a green pipeline that uploaded nothing, a broken npm package, a blueprint rejected on every run, a working copy tracking the forbidden remote, empty pipelines going red for nothing, and a release build that nearly overwrote a published image. None was found by monitoring; four surfaced by accident while looking for something else. ADR-0009 documents the commit conventions and the retroactive anonymisation of 251 commits. It is filed after the fact, which is exactly the mistake the ADR duty exists to prevent - stated in the ADR rather than smoothed over. Also recorded: assigning status:next and reassigning milestones are forbidden to a session acting alone; both happened here in the refinement with sorb, so the rule stands unweakened.
2026-08-09 12:00:00 +00:00
parent 46c61e1c1e
commit 0fde69a6f2
3 changed files with 221 additions and 0 deletions
@@ -48,6 +48,9 @@ Drei Fragen, mehr nicht:
 Grundlage sind die AARs des Monats — sie sind die Retro-Vorbereitung, nicht ihr
 Ersatz.

+Ergebnisse werden unter [`retro/`](retro/) abgelegt, eine Datei je Termin. Die
+erste: [2026-08-09](retro/2026-08-09.md).
+
 ## AAR (anlassbezogen)

 Nach jedem Deploy mit Übergabe und nach jedem Incident, Vorlage in