Record hygiene: resolve issues 310, 312, 313, 314, 318, 325, 327, 330 and 337, whose fixes are merged and live #239

2026-10-09T00:19:27Z

mesh-admin commented

2026-10-09 00:19:27 +00:00

Record hygiene. Do not merge without review.

Nine issues still read located although their fixes merged on 2026-10-08 and are delivered. Each now reads resolved, and its diagnosis (or, for 325, its report) gains a dated section naming the merged pull requests and what was read live on 2026-10-09 to show the fix works.

issue	fixed by	seen live
310	mesh-controller#135, mesh-lab#65 (R310)	the media catalogue's main now requires both checks, override off (its open half)
312	mesh-catalog#120	`disk_load` answers on the control node and the laptop
313	mesh-catalog#121, mesh-controller#136 (fixed-by filled)	held history reads `retired`; `retire-history` answers
314	mesh-controller#138, mesh-tools#22, mesh-lab#66 (R314)	unfiltered `conditions` answers
318	mesh-host#55, mesh-controller#142, mesh-lab#67 (R318)	`relogin-needed` held as a wait, nothing put back, nothing waiting
325	mesh-controller#150, mesh-lab#68 (R325)	controller delivered through #170, no machine behind
327	mesh-controller#161, mesh-catalog#139, mesh-lab#71 (R327)	`nats_closed_connections`: every connection named, none dropped
330	mesh-controller#159, mesh-tools#24, mesh-lab#70 (R330), mesh-host#60	`dead-letters` answers
337	mesh-catalog#143 (fixed-by filled; replay-none already there)	`postgres_reader_grants` on both stores: nothing readable

One new observation, recorded in 327: mesh-controller verb node closed 84 connections in an hour. node is not one of the verbs ADR 0265 serves on the serving connection, and who calls it that often is not known.

Not changed, on purpose:

315, 320, 321, 322, 324, 332: fixes merged and live, but each is a core issue by cycle.py (its located-in names the controller, the node-engine or the forge's module), and none has a replay or a replay-none:. They stay located until one is registered or written.
311: the live proof the issue names (the first media-catalogue pull request touching a module after #14) has not happened; #14 is still the newest pull request there.
339: mesh-host #64 and #65 are still open.
316, 317, 319, 323, 326, 328, 329: no fix merged.
333, 334, 336, 338: on open branches or left alone.

Checks run locally from a fresh clone: records.py, index.py, cycle.py and words.py (with a fresh mesh-catalog checkout as MESH_CATALOG_DIR) all pass.

Record hygiene. Do not merge without review. Nine issues still read `located` although their fixes merged on 2026-10-08 and are delivered. Each now reads `resolved`, and its diagnosis (or, for 325, its report) gains a dated section naming the merged pull requests and what was read live on 2026-10-09 to show the fix works. | issue | fixed by | seen live | |---|---|---| | 310 | mesh-controller#135, mesh-lab#65 (R310) | the media catalogue's main now requires both checks, override off (its open half) | | 312 | mesh-catalog#120 | `disk_load` answers on the control node and the laptop | | 313 | mesh-catalog#121, mesh-controller#136 (fixed-by filled) | held history reads `retired`; `retire-history` answers | | 314 | mesh-controller#138, mesh-tools#22, mesh-lab#66 (R314) | unfiltered `conditions` answers | | 318 | mesh-host#55, mesh-controller#142, mesh-lab#67 (R318) | `relogin-needed` held as a wait, nothing put back, nothing waiting | | 325 | mesh-controller#150, mesh-lab#68 (R325) | controller delivered through #170, no machine behind | | 327 | mesh-controller#161, mesh-catalog#139, mesh-lab#71 (R327) | `nats_closed_connections`: every connection named, none dropped | | 330 | mesh-controller#159, mesh-tools#24, mesh-lab#70 (R330), mesh-host#60 | `dead-letters` answers | | 337 | mesh-catalog#143 (fixed-by filled; replay-none already there) | `postgres_reader_grants` on both stores: nothing readable | One new observation, recorded in 327: `mesh-controller verb node` closed 84 connections in an hour. `node` is not one of the verbs ADR 0265 serves on the serving connection, and who calls it that often is not known. Not changed, on purpose: - 315, 320, 321, 322, 324, 332: fixes merged and live, but each is a core issue by `cycle.py` (its `located-in` names the controller, the node-engine or the forge's module), and none has a replay or a `replay-none:`. They stay `located` until one is registered or written. - 311: the live proof the issue names (the first media-catalogue pull request touching a module after #14) has not happened; #14 is still the newest pull request there. - 339: mesh-host #64 and #65 are still open. - 316, 317, 319, 323, 326, 328, 329: no fix merged. - 333, 334, 336, 338: on open branches or left alone. Checks run locally from a fresh clone: records.py, index.py, cycle.py and words.py (with a fresh mesh-catalog checkout as MESH_CATALOG_DIR) all pass.

mesh-admin added 1 commit 2026-10-09 00:19:27 +00:00

Issues 310, 312, 313, 314, 318, 325, 327, 330, 337: resolved, their fixes merged and seen live

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

120cdcd25a

Each fix's pull requests are merged and delivered; each issue now says
what was read live on 2026-10-09 to show it, so the record stops
listing fixed faults as located.

mesh-admin commented

2026-10-09 00:19:48 +00:00

Delivery novox/hq@120cdcd25ab0 — delivered since 2026-10-09T07:23:37Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-09 00:19 (new) → proposed (announced): novox/hq#239's head announced
2026-10-09 00:20 proposed → checked (checked): the verdict names this commit
2026-10-09 00:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 07:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 07:23 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@120cdcd25ab0` — **delivered** since 2026-10-09T07:23:37Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-09 00:19 (new) → proposed (announced): novox/hq#239's head announced - 2026-10-09 00:20 proposed → checked (checked): the verdict names this commit - 2026-10-09 00:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 07:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-09 07:23 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin merged commit a5656b9cce into main

2026-10-09 07:23:32 +00:00

mesh-admin deleted branch issues/hygiene-resolve-merged-fixes

2026-10-09 07:23:32 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#239