burn-down Part A: 24 rows closed as fixed by later work, 2 duplicates merged, R-376/R-817/R-818 done (335 -> 306); Part A table

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-10-05 16:53:02 +02:00
parent 58ce696e16
commit f5a0aeb0b8
8 changed files with 714 additions and 38 deletions
@@ -758,6 +758,8 @@ expensive mistake. That asymmetry is the same one `looksLikeRepositoryDamage` is

 ## v0.109.0 — the Backup card told every operator that every customer had no backups (2026-08-30, R-331)

+> **Correction 2026-10-05 (R-818):** the ids **R-330** and **R-331** in this entry are mislabels. These two findings never had register rows of their own; the register's R-330 and R-331 are disk-health Phase 2 and Phase 3. Read „R-330" here as *the nightly false app alarm* (controller v0.224.0) and „R-331" as *the off-site snapshot count read as a measured zero* (hub v0.109.0 Backup card, controller v0.225.0 `stats_known`). Nothing was renumbered.
+
 > **This push used `git push --no-verify`, and that is declared here rather than worked around.**
 > `golden_currency_gate.py` was CONVICTED: controller v0.224.0 and v0.225.0 are released and the newest
 > golden bake carries 0.223.0, so a machine installed right now receives neither. **A bypass, not a