From ef20ed041cf087efc6ceada8a6f21b6681b411ad Mon Sep 17 00:00:00 2001 From: Pieter Viljoen Date: Sun, 23 Aug 2026 17:18:36 -0700 Subject: [PATCH] Fix Findings-Table Count Mismatch in TODO.md The intro said three findings were open, but the table carried a fourth, resolved row (#633) kept for the record. Counted it separately instead of folding it into the open count. --- TODO.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TODO.md b/TODO.md index 5e380cb..e9809de 100644 --- a/TODO.md +++ b/TODO.md @@ -117,7 +117,7 @@ Reconverged 2026-08-05, and the run is written up in [`reports/Blog/audit.md`](. **Measured against hub `main` `3b802b9eb9a841c0149d018f4db6ffa1b9419051`**, and the ref is named because `main` moves, which is the trap below. Every verbatim unit now matches: the re-vendor of `repo-config/configure.sh` this record previously owed, for the jq portability defect reported as [#549][issue-549] and fixed at the hub in [#553][pr-553], landed with this change. The links above are pinned to that same ref rather than to `main`, so this record stays checkable after the hub moves again. -Three findings are open at the hub, recorded here rather than only in the issues because each changes what a fleet audit of this repo means. The first two are not work this repo can do. The third is, once the change answering it is ground truth, and what it will ask is stated below the table. +Three findings are open at the hub, plus one already resolved and kept for the record, each recorded here rather than only in the issues because it changes what a fleet audit of this repo means. Of the three open, the first two are not work this repo can do. The third is, once the change answering it is ground truth, and what it will ask is stated below the table. | Issue | What it means here | | --- | --- |