Grooming: five issues were fixed and never closed, and one is not #187

2026-09-29T20:26:15Z

jschoubben commented

2026-09-29 20:26:15 +00:00

A grooming pass over the issue folder, reading what the code repositories' commits actually cite rather than trusting the statuses.

Five were fixed and never closed. Each names a commit that is on main and cites the issue by number:

088 the forge's address follows a moved port, as a file already did (mesh-controller, #46)
089 a route names the endpoint it serves, and the machine-port redirection is applied to contributions (mesh-controller bdf965d, portOfEndpoint, AtPublishedPort)
120 every credential provider says whether it still holds a consumer (mesh-catalog, #84)
128 the mesh writes into a marked block of a text file instead of over it (mesh-host)
130 undeclaring gives a unit back the state it was found in (mesh-host)

Each carries a short Closed section saying it was closed by reading commits rather than by a run, so nobody reads a green that was never measured.

129 stays located on purpose. ca-trust is merged and no machine holds it, so the symptom it opened on — every internal name failing verification everywhere — is still true. Closing it on a module that exists would be closing it on an intention.

006 gets a note rather than a status change. The knowledge base it is about is the predecessor's and is unreachable since the cut-over (issue 147), so its answer is no longer "index this repository" and the honest fix is the README that claims the property.

A grooming pass over the issue folder, reading what the code repositories' commits actually cite rather than trusting the statuses. **Five were fixed and never closed.** Each names a commit that is on `main` and cites the issue by number: - **088** the forge's address follows a moved port, as a file already did (mesh-controller, #46) - **089** a route names the endpoint it serves, and the machine-port redirection is applied to contributions (mesh-controller `bdf965d`, `portOfEndpoint`, `AtPublishedPort`) - **120** every credential provider says whether it still holds a consumer (mesh-catalog, #84) - **128** the mesh writes into a marked block of a text file instead of over it (mesh-host) - **130** undeclaring gives a unit back the state it was found in (mesh-host) Each carries a short *Closed* section saying it was closed by reading commits rather than by a run, so nobody reads a green that was never measured. **129 stays `located` on purpose.** `ca-trust` is merged and no machine holds it, so the symptom it opened on — every internal name failing verification everywhere — is still true. Closing it on a module that exists would be closing it on an intention. **006 gets a note rather than a status change.** The knowledge base it is about is the predecessor's and is unreachable since the cut-over (issue 147), so its answer is no longer "index this repository" and the honest fix is the README that claims the property.

jschoubben added 2 commits 2026-09-29 20:26:15 +00:00

Grooming: five issues were fixed and never closed, and one is not 14be8576f8

088, 089, 120, 128 and 130 each name a commit that is on main and cites them —
the forge's address following a moved port, a route naming its endpoint, a
provisioner asking the backend what is there, the hosts file written into a
marked block, and undeclaring giving a unit back the state it was found in.
Each says it was closed by reading commits rather than by a run, so nobody
reads a green that was never measured.

129 stays located on purpose: ca-trust is merged and no machine holds it, so
the symptom it opened on is still true everywhere.

Grooming: issue 006's knowledge base is the predecessor's, and is gone 9a1dc4665c

The record catches README claiming this repository is indexed into a knowledge
base. Nothing indexed it, and since the cut-over there is nothing to index it
into — the surface that answered is on the transport the mesh removed (issue
147). Noted where the record is, so the next reader does not go looking for a
search that cannot exist.

jschoubben added 1 commit 2026-09-29 20:26:16 +00:00

Grooming: issue 006's knowledge base is the predecessor's, and is gone 9a1dc4665c

The record catches README claiming this repository is indexed into a knowledge
base. Nothing indexed it, and since the cut-over there is nothing to index it
into — the surface that answered is on the transport the mesh removed (issue
147). Noted where the record is, so the next reader does not go looking for a
search that cannot exist.

jschoubben merged commit 9dc49cd831 into main

2026-09-29 21:37:04 +00:00

jschoubben deleted branch grooming/stale-issues

2026-09-29 21:37:04 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#187