From d01c0f8e286da8ffa36c50bb8de8553031ab75bf Mon Sep 17 00:00:00 2001 From: Garrett Allen <98648590+Gerrrt@users.noreply.github.com> Date: Tue, 8 Sep 2026 15:37:13 +0000 Subject: [PATCH] docs: #110 was closed by a commit message and is reopened (#110) GitHub closed #110 on 2026-08-27 when the commit that wrote fit-the-ups-battery.md said the switch's power move "is the one that closes #110" and the phrase was read as a close keyword. Nothing was racked, and every document said so; only the issue's state was wrong. Reopened on 2026-09-08 and recorded here so the roadmap's open entry and the issue's state stop disagreeing. Co-Authored-By: Claude Fable 5.1 --- README.md | 3 ++- docs/roadmap.md | 8 ++++++++ 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index bcaa542..ae12c30 100644 --- a/README.md +++ b/README.md @@ -332,7 +332,8 @@ self-test, and the card is set to test itself every fortnight ([#93](https://github.com/Gerrrt/HomeLab/issues/93)) — but the switch between the monitoring host and the network still has no battery at all, so both laptops stay running and go deaf on a mains cut -([#110](https://github.com/Gerrrt/HomeLab/issues/110)); and the config export +([#110](https://github.com/Gerrrt/HomeLab/issues/110), reopened on 2026-09-08 +after a commit message had closed it by accident); and the config export itself now leaves the monitoring host nightly, so the spare is what is left ([#92](https://github.com/Gerrrt/HomeLab/issues/92)). diff --git a/docs/roadmap.md b/docs/roadmap.md index cbc263c..d5419c9 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -342,6 +342,14 @@ what left this one unfireable for months. at the rack on 2026-08-21: 4-post, square holes, full 1U with rear support rather than a cantilever. The spare ProDesk from [#92](https://github.com/Gerrrt/HomeLab/issues/92) racks here too, powered off. + **Reopened 2026-09-08.** GitHub had closed the issue on 2026-08-27, when the + commit that wrote the runbook said the switch's power move "is the one that + closes #110" and the phrase was read as a close keyword. Nothing was racked; + this entry and every document beside it said so the whole time, and only the + issue's state was wrong. The lesson is the one ADR-0026 already draws — a + state nothing checks against the thing it describes drifts — with a + sharper edge: a commit message can close an issue about work it explicitly + says it did not do. → [runbook](runbooks/fit-the-ups-battery.md) - **[#251](https://github.com/Gerrrt/HomeLab/issues/251) Put the wiki on `oracle` into the repository, and back up its database.** ADR-0015 ratified a