mesh-issues: the tracker hands out decision and research numbers (hq issue 424) #204

Merged
mesh-admin merged 2 commits from fix/424-the-tracker-hands-out-decision-and-research-numbers into main 2026-10-11 02:59:56 +00:00
Contributor

Fixes hq issue 424 (the issue tracker does not hand out decision and research numbers, so sessions still take them by reading hq). Implements hq ADR 0275 rule 8 and ADR 0290 rule 5.

Closes the contract issue-tracker.reserve {kind, for} -> {kind, number} relied on by issue 425.

What changed

  • New verb issue-tracker.reserve, arguments {"kind": "decision"|"research", "for": "<optional one line>"}, answers {"kind", "number"} (an integer), plus prefix (0292 / 046), for, by, at, said, announced.
  • One counter per sequence in the existing counters state, keys decision and research, advanced by the SDK's compare-and-set Increment like issue.
  • Start: a counter that does not exist is created once at max(highest number hq holds in 02-DECISIONS / 01-RESEARCH read via records.records_list, the setting decision-floor / research-floor, the reservations kept). The first reserve of a kind is refused, spending nothing, while hq cannot be read.
  • Each reserve reads hq again and raises a counter that stands below hq's highest (a number taken by hand), written only at the revision read; once started, an unreadable hq leaves the counter as it stands.
  • Open branches: the existing forge tools cannot list a folder on a branch (gitea_get_file refuses a directory), so open branches are covered by the new settings decision-floor (293: 0293 is on an open branch today) and research-floor (45), read once when the counter starts. Documented in the README.
  • Each reservation kept in a new declared state reservations (key decision-0292, research-046) with by (from the caller as every verb: unproven until the runtime names the caller, hq issue 340; never an argument), at, for; event reserved. A reservation whose write cannot be confirmed is refused and its number stays spent.
  • Manifest: reserve in seat and claim serves, reserved in emits, records.records_list in invokes, reservations in state, the two floors in the settings.
  • README: the verb, a section on decision and research numbers, the settings, the tests.

How it is tested

Tests written first; on main they fail (the verb, kinds and state do not exist). go test -race ./... in modules/mesh-issues passes:

  • TestFortyReservationsAtOnceFromTwoInstancesGetFortyDistinctConsecutiveNumbers: two bundle instances on a JetStream server in the test, 40 concurrent reserves, 40 distinct consecutive numbers from 292, contention proven (279 counter updates lost and retried in the run), a reservation and an event each, the issue counter untouched.
  • reserve_test.go: start above hq (0291 -> 292, 045 -> 46), above the floor, above a reservation kept, a counter behind hq raised, the floor read once, 80 concurrent reserves across both kinds, a refused kind / bad for spends nothing and reads nothing, first reserve refused while hq is unreadable, reservation kept with who/when/for, event failure said, an unkept reservation leaves its number spent, strict arguments (by refused).
  • manifest_test.go updated for serves/claims/emits/invokes/state.
  • MESH_GATE=<mesh-controller main> MESH_CHECK_MODULES=mesh-issues sh merge-check.sh passes (words, agent home, paths, module check with 69 resources without health as kept, module tests).

Not merged by the author; needs an independent review.

Fixes hq issue 424 (the issue tracker does not hand out decision and research numbers, so sessions still take them by reading hq). Implements hq ADR 0275 rule 8 and ADR 0290 rule 5. Closes the contract `issue-tracker.reserve {kind, for} -> {kind, number}` relied on by issue 425. ## What changed - New verb `issue-tracker.reserve`, arguments `{"kind": "decision"|"research", "for": "<optional one line>"}`, answers `{"kind", "number"}` (an integer), plus `prefix` (0292 / 046), `for`, `by`, `at`, `said`, `announced`. - One counter per sequence in the existing `counters` state, keys `decision` and `research`, advanced by the SDK's compare-and-set Increment like `issue`. - Start: a counter that does not exist is created once at max(highest number hq holds in `02-DECISIONS` / `01-RESEARCH` read via `records.records_list`, the setting `decision-floor` / `research-floor`, the reservations kept). The first reserve of a kind is refused, spending nothing, while hq cannot be read. - Each reserve reads hq again and raises a counter that stands below hq's highest (a number taken by hand), written only at the revision read; once started, an unreadable hq leaves the counter as it stands. - Open branches: the existing forge tools cannot list a folder on a branch (`gitea_get_file` refuses a directory), so open branches are covered by the new settings `decision-floor` (293: 0293 is on an open branch today) and `research-floor` (45), read once when the counter starts. Documented in the README. - Each reservation kept in a new declared state `reservations` (key `decision-0292`, `research-046`) with `by` (from the caller as every verb: `unproven` until the runtime names the caller, hq issue 340; never an argument), `at`, `for`; event `reserved`. A reservation whose write cannot be confirmed is refused and its number stays spent. - Manifest: `reserve` in seat and claim `serves`, `reserved` in `emits`, `records.records_list` in `invokes`, `reservations` in `state`, the two floors in the settings. - README: the verb, a section on decision and research numbers, the settings, the tests. ## How it is tested Tests written first; on main they fail (the verb, kinds and state do not exist). `go test -race ./...` in modules/mesh-issues passes: - `TestFortyReservationsAtOnceFromTwoInstancesGetFortyDistinctConsecutiveNumbers`: two bundle instances on a JetStream server in the test, 40 concurrent reserves, 40 distinct consecutive numbers from 292, contention proven (279 counter updates lost and retried in the run), a reservation and an event each, the issue counter untouched. - `reserve_test.go`: start above hq (0291 -> 292, 045 -> 46), above the floor, above a reservation kept, a counter behind hq raised, the floor read once, 80 concurrent reserves across both kinds, a refused kind / bad `for` spends nothing and reads nothing, first reserve refused while hq is unreadable, reservation kept with who/when/for, event failure said, an unkept reservation leaves its number spent, strict arguments (`by` refused). - `manifest_test.go` updated for serves/claims/emits/invokes/state. - `MESH_GATE=<mesh-controller main> MESH_CHECK_MODULES=mesh-issues sh merge-check.sh` passes (words, agent home, paths, module check with 69 resources without health as kept, module tests). Not merged by the author; needs an independent review.
mesh-admin added 1 commit 2026-10-11 02:26:06 +00:00
mesh-issues: hand out decision and research numbers, so sessions stop taking them by reading hq (hq issue 424)
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 superseded: a newer head of the same pull request
350a597c47
A new verb, issue-tracker.reserve {kind, for} -> {kind, number}: one counter
per sequence beside the issue counter, advanced the same way, started above
what hq's record holds, a floor setting for open branches and the
reservations kept, and raised when hq holds a higher number. A reserved
number is spent forever, kept with who, when and for what, and said as the
event reserved (hq ADR 0275 rule 8, ADR 0290 rule 5).
Author
Contributor

Delivery novox/mesh-catalog@9d4d9d5cd2e2 — delivered since 2026-10-11T03:05:06Z

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 2m17s
  • mesh-issues on the rest running it: sent

Transitions

  • 2026-10-11 02:30 (new) → proposed (announced): novox/mesh-catalog#204's head announced
  • 2026-10-11 02:32 proposed → checked (checked): the verdict names this commit
  • 2026-10-11 02:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-11 03:01 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-11 03:01 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-11 03:05 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@9d4d9d5cd2e2` — **delivered** since 2026-10-11T03:05:06Z **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 2m17s - mesh-issues on the rest running it: sent **Transitions** - 2026-10-11 02:30 (new) → proposed (announced): novox/mesh-catalog#204's head announced - 2026-10-11 02:32 proposed → checked (checked): the verdict names this commit - 2026-10-11 02:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-11 03:01 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-11 03:01 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-11 03:05 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 350a597c

  • 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/bus_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/reserve_test.go

Run by the build seat on shanks as build-1791685592569872613 (builds --log build-1791685592569872613).

--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_list, keeps state issues, counters, grooming, reservations
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-11T02:23:28Z 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-11T02:23:28Z

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/bus_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go and modules/mesh-issues/cmd/mesh-issues/reserve_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.003s
words: 12 retired words and 70 daemons' lines, none in the 39577 strings of 657 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.012s
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: 69, as kept
testing modules/mesh-issues
ok  	mesh-issues/cmd/mesh-issues	8.474s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `350a597c` - `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/bus_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/reserve_test.go Run by the build seat on shanks as `build-1791685592569872613` (`builds --log build-1791685592569872613`). ``` --- the gate: mesh-issues mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_list, keeps state issues, counters, grooming, reservations 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-11T02:23:28Z 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-11T02:23:28Z 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/bus_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go and modules/mesh-issues/cmd/mesh-issues/reserve_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.003s words: 12 retired words and 70 daemons' lines, none in the 39577 strings of 657 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s 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: 69, as kept testing modules/mesh-issues ok mesh-issues/cmd/mesh-issues 8.474s --- its merge-check-typescript.sh (typescript toolchain) ```
jschoubben added 1 commit 2026-10-11 02:30:31 +00:00
mesh-issues: say in reserve's answer when hq could not be read, and grant the import its records calls (review of #204)
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
9d4d9d5cd2
A number handed out unchecked against hq is a failure that must be loud, so
the answer carries a warning, not only the log. The import already calls
records_status and records_read; invokes now names them.
Author
Contributor

Merge check at 9d4d9d5c

  • 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/bus_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/reserve_test.go

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

--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_status, records.records_list, records.records_read, keeps state issues, counters, grooming, reservations
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-11T02:23:28Z 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-11T02:23:28Z

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/bus_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go and modules/mesh-issues/cmd/mesh-issues/reserve_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.003s
words: 12 retired words and 70 daemons' lines, none in the 39587 strings of 657 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.012s
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: 69, as kept
testing modules/mesh-issues
ok  	mesh-issues/cmd/mesh-issues	7.997s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `9d4d9d5c` - `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/bus_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/reserve_test.go Run by the build seat on ace as `build-1791685832352354359` (`builds --log build-1791685832352354359`). ``` --- the gate: mesh-issues mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_status, records.records_list, records.records_read, keeps state issues, counters, grooming, reservations 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-11T02:23:28Z 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-11T02:23:28Z 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/bus_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go and modules/mesh-issues/cmd/mesh-issues/reserve_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.003s words: 12 retired words and 70 daemons' lines, none in the 39587 strings of 657 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s 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: 69, as kept testing modules/mesh-issues ok mesh-issues/cmd/mesh-issues 7.997s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-admin merged commit 9afc253e85 into main 2026-10-11 02:59:56 +00:00
mesh-admin deleted branch fix/424-the-tracker-hands-out-decision-and-research-numbers 2026-10-11 02:59:57 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#204