mesh-issues: import hq's issue folders at their own numbers (hq ADR 0275, to-be 53 slice 3) #180

Merged
mesh-admin merged 1 commits from feat/mesh-issues-import into main 2026-10-10 14:04:24 +00:00
Contributor

Slice 3 of the issue tracker (hq ADR 0275, to-be 53 §8): issue-tracker.import.

  • Reads every 04-ISSUES/NNN-slug/00-report.md of hq through the records module over the bus (records_status, records_list, records_read via the SDK's Ask), at the commit the records module's checkout stands at; refuses a run during which the checkout moved, and a commit argument it does not stand at.
  • Writes each as an issue at its own number: create-if-absent on the key, the counter untouched; record is the folder, the title the heading, the report the text, status/opened/located-in/fixed-by/amended-design/replay/replay-none the frontmatter's as written (status one to one, no cycle rule applied). Issues and decisions the report names become links.
  • Never overwrites: an issue held differently is differs (fields named), one held the same is same; a second run changes nothing and says so. Fills the status of an issue opened with a folder before this slice (status empty), or open when hq holds no folder for it. Refuses the whole run when a folder is numbered past the counter; refuses alone a folder at/past first-number with no issue in the tracker.
  • Who/when: opened-by: import, opened the report's date, imported: {at, by, commit, from}; one imported event per issue (declared in the manifest).
  • An owner hq named that the registered list does not know is kept as written and marked located-in-unverified (issue 366 owns the list); move with a new located-in clears it.
  • move no longer refuses an issue with a folder; open with record gives status open and takes located-in.
  • dry-run: true reads everything and writes nothing; mesh-issues dry-run <checkout> <settings.json> at the terminal does the same over a checkout before the rollout.

Dry run over hq main at 1ea678c6bd48f62a45db3b5e4b21b9c46867d31a (terminal, empty tracker): 361 folders, would create 361, refused 0; 27 open, 1 diagnosing, 48 located, 284 resolved, 1 wontfix; 12 odd (all amended-design naming a decision record, kept as written).

Tests: frontmatter parsing on seven real reports in testdata/hq (bracketed list with commas in parentheses, quoted block items, an apostrophe in prose, a resolved: date, a replay, an empty list, a wontfix); create-at-number with the counter untouched; a second run changing nothing; an issue held differently left alone; the folder-backed fill once; refusals (past the counter, past first-number, another commit, a moving record, a failed write); dry run writes nothing; unreadable reports refused alone with why; strict arguments. go test -race ./... green; the catalogue's merge-check green (gate part not run locally).

hq side: novox/hq PR process/issue-status-lives-in-the-tracker (playbook 03, cycle.py, notes in ADR 0019, 0080, 0275). Order: merge and roll out this, run issue-tracker.import once, then merge the hq PR.

Slice 3 of the issue tracker (hq ADR 0275, to-be 53 §8): `issue-tracker.import`. - Reads every `04-ISSUES/NNN-slug/00-report.md` of hq **through the records module over the bus** (`records_status`, `records_list`, `records_read` via the SDK's `Ask`), at the commit the records module's checkout stands at; refuses a run during which the checkout moved, and a `commit` argument it does not stand at. - Writes each as an issue **at its own number**: create-if-absent on the key, the counter untouched; `record` is the folder, the title the heading, the report the text, status/opened/located-in/fixed-by/amended-design/replay/replay-none the frontmatter's as written (status one to one, no cycle rule applied). Issues and decisions the report names become links. - Never overwrites: an issue held differently is `differs` (fields named), one held the same is `same`; a second run changes nothing and says so. Fills the status of an issue opened with a folder before this slice (status empty), or `open` when hq holds no folder for it. Refuses the whole run when a folder is numbered past the counter; refuses alone a folder at/past `first-number` with no issue in the tracker. - Who/when: `opened-by: import`, `opened` the report's date, `imported: {at, by, commit, from}`; one `imported` event per issue (declared in the manifest). - An owner hq named that the registered list does not know is kept as written and marked `located-in-unverified` (issue 366 owns the list); `move` with a new `located-in` clears it. - `move` no longer refuses an issue with a folder; `open` with `record` gives status `open` and takes `located-in`. - `dry-run: true` reads everything and writes nothing; `mesh-issues dry-run <checkout> <settings.json>` at the terminal does the same over a checkout before the rollout. **Dry run over hq main at `1ea678c6bd48f62a45db3b5e4b21b9c46867d31a`** (terminal, empty tracker): 361 folders, would create 361, refused 0; 27 open, 1 diagnosing, 48 located, 284 resolved, 1 wontfix; 12 odd (all `amended-design` naming a decision record, kept as written). Tests: frontmatter parsing on seven real reports in `testdata/hq` (bracketed list with commas in parentheses, quoted block items, an apostrophe in prose, a `resolved:` date, a replay, an empty list, a wontfix); create-at-number with the counter untouched; a second run changing nothing; an issue held differently left alone; the folder-backed fill once; refusals (past the counter, past first-number, another commit, a moving record, a failed write); dry run writes nothing; unreadable reports refused alone with why; strict arguments. `go test -race ./...` green; the catalogue's merge-check green (gate part not run locally). hq side: novox/hq PR `process/issue-status-lives-in-the-tracker` (playbook 03, cycle.py, notes in ADR 0019, 0080, 0275). Order: merge and roll out this, run `issue-tracker.import` once, then merge the hq PR.
mesh-admin added 1 commit 2026-10-10 14:00:57 +00:00
mesh-issues: import hq's issue folders at their own numbers, and an issue with a folder is whole in the tracker (hq ADR 0275, to-be 53 slice 3)
mesh/merge-gate pass: builds mesh-issues → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered
d05308a419
Author
Contributor

Delivery novox/mesh-catalog@d05308a419b2 — delivered since 2026-10-10T14:11:01Z

Delivery plan — builds mesh-issues → novox; no bus step

  • tier 0: mesh-issues
  • novox: receives mesh-issues

Machines

  • mesh-issues on novox: passed — healthy 3 times over 2m25s
  • mesh-issues on the rest running it: sent

Transitions

  • 2026-10-10 14:01 (new) → proposed (announced): novox/mesh-catalog#180's head announced
  • 2026-10-10 14:03 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 14:03 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 14:07 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-10 14:07 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
  • 2026-10-10 14:11 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@d05308a419b2` — **delivered** since 2026-10-10T14:11:01Z **Delivery plan** — builds mesh-issues → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues **Machines** - mesh-issues on novox: passed — healthy 3 times over 2m25s - mesh-issues on the rest running it: sent **Transitions** - 2026-10-10 14:01 (new) → proposed (announced): novox/mesh-catalog#180's head announced - 2026-10-10 14:03 proposed → checked (checked): the verdict names this commit - 2026-10-10 14:03 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 14:07 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 14:07 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-10 14:11 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at d05308a4

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-issues)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds mesh-issues → novox; no bus step

  • tier 0: mesh-issues
  • novox: receives mesh-issues
  • read by no module's build: modules/mesh-issues/README.md, modules/mesh-issues/cmd/mesh-issues/import_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/report_test.go, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/007-an-installed-package-is-not-a-capability/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/043-a-module-cannot-be-given-the-meshs-own-queues/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/080-a-cache-grant-lets-the-consumer-flush-the-server/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/150-a-route-is-contributed-before-its-module-is-taken/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/236-the-catalogue-check-passes-a-manifest-the-host-refuses/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/345-a-reminder-window-shows-transparent-and-empty/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/362-two-merges-seconds-apart-left-their-delivery-waiting-for-a-person/00-report.md, modules/mesh-issues/cmd/mesh-issues/tracker_test.go

Run by the build seat on ace as build-1791640863933934027 (builds --log build-1791640863933934027).

--- the gate: mesh-issues
mesh-issues: ok, keeps state issues, counters
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T13:56:57Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-10T13:56:57Z

modules the change moves:
  - mesh-issues (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues

notes:
  - modules/mesh-issues/README.md, modules/mesh-issues/cmd/mesh-issues/import_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/report_test.go, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/007-an-installed-package-is-not-a-capability/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/043-a-module-cannot-be-given-the-meshs-own-queues/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/080-a-cache-grant-lets-the-consumer-flush-the-server/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/150-a-route-is-contributed-before-its-module-is-taken/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/236-the-catalogue-check-passes-a-manifest-the-host-refuses/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/345-a-reminder-window-shows-transparent-and-empty/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/362-two-merges-seconds-apart-left-their-delivery-waiting-for-a-person/00-report.md and modules/mesh-issues/cmd/mesh-issues/tracker_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words and 70 daemons' lines, none in the 37822 strings of 639 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.011s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/mesh-issues
ok  	mesh-issues/cmd/mesh-issues	5.620s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `d05308a4` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-issues) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds mesh-issues → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues - read by no module's build: modules/mesh-issues/README.md, modules/mesh-issues/cmd/mesh-issues/import_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/report_test.go, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/007-an-installed-package-is-not-a-capability/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/043-a-module-cannot-be-given-the-meshs-own-queues/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/080-a-cache-grant-lets-the-consumer-flush-the-server/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/150-a-route-is-contributed-before-its-module-is-taken/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/236-the-catalogue-check-passes-a-manifest-the-host-refuses/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/345-a-reminder-window-shows-transparent-and-empty/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/362-two-merges-seconds-apart-left-their-delivery-waiting-for-a-person/00-report.md, modules/mesh-issues/cmd/mesh-issues/tracker_test.go Run by the build seat on ace as `build-1791640863933934027` (`builds --log build-1791640863933934027`). ``` --- the gate: mesh-issues mesh-issues: ok, keeps state issues, counters long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T13:56:57Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-10T13:56:57Z modules the change moves: - mesh-issues (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues notes: - modules/mesh-issues/README.md, modules/mesh-issues/cmd/mesh-issues/import_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/report_test.go, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/007-an-installed-package-is-not-a-capability/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/043-a-module-cannot-be-given-the-meshs-own-queues/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/080-a-cache-grant-lets-the-consumer-flush-the-server/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/150-a-route-is-contributed-before-its-module-is-taken/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/236-the-catalogue-check-passes-a-manifest-the-host-refuses/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/345-a-reminder-window-shows-transparent-and-empty/00-report.md, modules/mesh-issues/cmd/mesh-issues/testdata/hq/04-ISSUES/362-two-merges-seconds-apart-left-their-delivery-waiting-for-a-person/00-report.md and modules/mesh-issues/cmd/mesh-issues/tracker_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words and 70 daemons' lines, none in the 37822 strings of 639 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.011s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 70, as kept testing modules/mesh-issues ok mesh-issues/cmd/mesh-issues 5.620s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-admin merged commit aabb83d6c9 into main 2026-10-10 14:04:24 +00:00
mesh-admin deleted branch feat/mesh-issues-import 2026-10-10 14:04:25 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#180