docs(deferment): correct the open-issue count to 17 (written before #523 was closed)
v2-ci / build (push) Successful in 5m46s
v2-ci / unit-tests (push) Failing after 17m38s

The enumeration already listed the post-#523 set (17 items) while the count said
18 -- the number was written between closing #516/#518/#507 and closing #523.
Verified against the API rather than re-derived: 17 open.

Claude-Session: https://claude.ai/code/session_015p7wGqy3YpZNCpDzTpGMKo
This commit is contained in:
Joseph Doherty
2026-07-30 03:56:12 -04:00
parent 30528d8bea
commit dc9d947bca
+4 -4
View File
@@ -31,7 +31,7 @@ how much they should worry you:
|---|---|---|---|
| **1** | **Three subsystems are fully authored, persisted, and shipped — and never executed.** Node ACLs, `IRediscoverable`/`IHostConnectivityProbe`, and `DriverTypeRegistry`. | An operator can author a rule, save it, deploy it green, and have it do **nothing**. §3 | ◐ `IRediscoverable` now consumed; the other two are **documented as inert** and tracked (#520, #521, #522) rather than fixed |
| **2** | **AdminUI authoring-dispatch gaps.** Calculation is offered in the driver picker but has no config form; three drivers have no device form; CSV + browse-commit dispatch maps miss the new drivers. | The "registered but unauthorable" class that has now bitten twice. §1.2 | ✅ **Closed** — G-1…G-6 fixed and guarded; G-7 remains |
| **3** | **17 open issues, all confirmed still open**, several broader than filed. | §2 | ◐ 4 resolved + closed, 4 new filed (one since closed) → **18 open**, none stale |
| **3** | **17 open issues, all confirmed still open**, several broader than filed. | §2 | ◐ 4 resolved + closed, 4 new filed (one since closed) → **17 open**, none stale |
| **4** | **Bookkeeping drift.** 8 `.tasks.json` files show ~140 "pending" tasks for work that shipped; 5 CLAUDE.md status claims are stale. | Someone follows the tracker and rebuilds a shipped driver. §6, §7 | ✅ **Closed** — 13 plan files + 11 archreview gates written back |
Nothing here is a data-loss or outage defect. The sharpest edge is §3 — silent non-enforcement.
@@ -64,8 +64,8 @@ change:
| **#507** | **Superseded, not migrated** — the requested migration was impossible, since both of the path's inputs are structurally empty in v3. |
| **#523** | Done, with the consequence carried forward: **AbCip and FOCAS now have no tag-change signal at all.** |
**18 issues remain open**, all genuine: #519#522 (four judgement calls + a design consequence), #517,
the eight MQTT follow-ups, #491, #489, #481, #468.
**17 issues remain open**, all genuine: #519#522 (four judgement calls + a design consequence), #517,
the eight MQTT follow-ups (#508#515), #491, #489, #481, #468.
---
@@ -137,7 +137,7 @@ incomplete), 2 CANNOT VERIFY (correctly filed as hardware/fixture-gated).
> records that only its `IRediscoverable` half was fixed. Four new issues were filed from §3 and §9: **#520** (ACL
> enforcement), **#521** (`IHostConnectivityProbe`), **#522** (stability tiers), **#523** (remove the
> periodic re-browse). #523 has since been done and closed too. After closing the four resolved issues on
> 2026-07-30 the tracker shows **18 open, none stale**. Everything not marked below is unchanged.
> 2026-07-30 the tracker shows **17 open, none stale**. Everything not marked below is unchanged.
| # | Title (abbrev.) | Verdict | Key evidence | Kind |
|---|---|---|---|---|