Slice 1 of hq ADR 0275 / to-be 53 (03-DESIGN/01-to-be/53-the-issue-tracker.md); naming per hq #272 (module mesh-issues, seat issue-tracker).
Acceptance: an agent opens an issue and gets the next number; two agents opening at the same moment never get the same one.
What it is. A Go bundle, modules/mesh-issues, for the control-node. Declares and claims the seat issue-tracker (scope mesh) with verbs open, get, list, move, note, link, served as issue-tracker.<verb>. States issues (history 8) and counters, declared and made by the controller; the module makes no bus resource. Events opened, moved, noted, linked, each with the number, what changed, who and when. Settings (trusted, terminal only): first-number (365, after hq's highest issue on main and every open branch today) and owners, the registered list located-in may name (hq's repositories and every catalogue module).
Numbers. The counter is advanced by the SDK's compare-and-set State(...).Increment (mesh-sdk #16, go/v0.1.12), in bounded rounds with jitter; it is started once by Create at max(first-number - 1, highest issue kept). A refused open takes no number. An issue is written by Create, never over a kept key (a loud fault, number left unused); a write whose answer was lost is recognised as its own by the open's id. A number is never handed out twice; it may be skipped only when the bus fails between the counter and the issue, and the answer says which.
Cycle rules at the write (hq 00-META/checks/cycle.py): five statuses; located needs located-in; resolved needs located-in and fixed-by; a core issue (same regex as cycle.py) resolves with replay R<n> or replay-none; wontfix needs a reason. A refused move changes nothing. An issue opened with a record (its hq folder) keeps its status there; move refuses it.
Input. Unknown arguments refused; size limits on every field; no control or format characters in one-line fields; a folder name is a slug, not a path; design paths, link targets and numbers by strict shape; text shaped like a credential refused.
Who acted: not proven yet. ADR 0275 §5 records the caller from the bus credential. The runtime hands a module no caller on a tool call (SDK Tool.Run gets name and arguments; the tool runner is not told who called, hq issue 340), so every change is recorded as by unproven, and no argument can name a caller. This needs runtime and controller work before the actor is real.
Tests (go test -race ./..., run by merge-check):
TestFiftyOpensAtOnceFromTwoInstancesGetFiftyDistinctConsecutiveNumbers: an embedded JetStream server, two instances of the bundle (the test binary re-executed) speaking MCP to a runtime played by the test against the buckets the manifest declares; 50 opens at once give 365..414 once each, 50 issues, 50 events; it asserts writers actually collided (about 400-460 lost writes retried locally).
every verb over the bus, and in-process: each verb, the cycle rules one case per row (refused cases change nothing and say nothing), refused open takes no number, key never overwritten, lost answer, gaps said, events and their failure, caller cannot be named, strict arguments, concurrent notes all kept, manifest agrees with the code.
Mutation: the counter written without its revision check (get + put) fails the acceptance test (duplicate numbers, caught loudly by the issue's create).
Merge only after: mesh-sdk go/v0.1.12 is tagged (it is) and the runtime that serves mesh/state.create/update is live where this runs (mesh-tools #23). Not assigned to any node.
MESH_GATE=<controller> sh merge-check.sh passes locally; module check: ok, keeps state issues, counters.
Slice 1 of hq ADR 0275 / to-be 53 (`03-DESIGN/01-to-be/53-the-issue-tracker.md`); naming per hq #272 (module `mesh-issues`, seat `issue-tracker`).
**Acceptance:** an agent opens an issue and gets the next number; two agents opening at the same moment never get the same one.
**What it is.** A Go bundle, `modules/mesh-issues`, for the control-node. Declares and claims the seat `issue-tracker` (scope mesh) with verbs `open`, `get`, `list`, `move`, `note`, `link`, served as `issue-tracker.<verb>`. States `issues` (history 8) and `counters`, declared and made by the controller; the module makes no bus resource. Events `opened`, `moved`, `noted`, `linked`, each with the number, what changed, who and when. Settings (trusted, terminal only): `first-number` (365, after hq's highest issue on main and every open branch today) and `owners`, the registered list `located-in` may name (hq's repositories and every catalogue module).
**Numbers.** The counter is advanced by the SDK's compare-and-set `State(...).Increment` (mesh-sdk #16, **go/v0.1.12**), in bounded rounds with jitter; it is started once by `Create` at max(first-number - 1, highest issue kept). A refused open takes no number. An issue is written by `Create`, never over a kept key (a loud fault, number left unused); a write whose answer was lost is recognised as its own by the open's id. A number is never handed out twice; it may be skipped only when the bus fails between the counter and the issue, and the answer says which.
**Cycle rules at the write** (hq `00-META/checks/cycle.py`): five statuses; located needs located-in; resolved needs located-in and fixed-by; a core issue (same regex as cycle.py) resolves with replay `R<n>` or replay-none; wontfix needs a reason. A refused move changes nothing. An issue opened with a `record` (its hq folder) keeps its status there; move refuses it.
**Input.** Unknown arguments refused; size limits on every field; no control or format characters in one-line fields; a folder name is a slug, not a path; design paths, link targets and numbers by strict shape; text shaped like a credential refused.
**Who acted: not proven yet.** ADR 0275 §5 records the caller from the bus credential. The runtime hands a module no caller on a tool call (SDK `Tool.Run` gets name and arguments; the tool runner is not told who called, hq issue 340), so every change is recorded as by `unproven`, and no argument can name a caller. This needs runtime and controller work before the actor is real.
**Tests** (`go test -race ./...`, run by merge-check):
- `TestFiftyOpensAtOnceFromTwoInstancesGetFiftyDistinctConsecutiveNumbers`: an embedded JetStream server, two instances of the bundle (the test binary re-executed) speaking MCP to a runtime played by the test against the buckets the manifest declares; 50 opens at once give 365..414 once each, 50 issues, 50 events; it asserts writers actually collided (about 400-460 lost writes retried locally).
- every verb over the bus, and in-process: each verb, the cycle rules one case per row (refused cases change nothing and say nothing), refused open takes no number, key never overwritten, lost answer, gaps said, events and their failure, caller cannot be named, strict arguments, concurrent notes all kept, manifest agrees with the code.
**Mutation:** the counter written without its revision check (get + put) fails the acceptance test (duplicate numbers, caught loudly by the issue's create).
**Merge only after:** mesh-sdk go/v0.1.12 is tagged (it is) and the runtime that serves `mesh/state.create`/`update` is live where this runs (mesh-tools #23). Not assigned to any node.
`MESH_GATE=<controller> sh merge-check.sh` passes locally; `module check`: ok, keeps state issues, counters.
mesh/merge-gate pass: builds new: modules/mesh-issues, sent nowhere; no bus step; every machine composes with the change as it did without (4 of 4 compose)
The seat issue-tracker, held once for the mesh: open, get, list, move, note
and link. The counter is advanced by the SDK's compare-and-set Increment
(go/v0.1.12) and started once at the setting first-number (365, after hq's
highest), never below an issue kept. The cycle's issue rules are refused at
the write; every change is an event. The runtime does not yet say who called,
so every change is recorded as by "unproven" and no argument can name a caller.
Deliverynovox/mesh-catalog@6f2c76ee7139 — delivered since 2026-10-10T11:01:21Z
Delivery plan — builds new: modules/mesh-issues, sent nowhere; no bus step
Transitions
2026-10-10 10:56 (new) → proposed (announced): novox/mesh-catalog#172's head announced
2026-10-10 10:58 proposed → checked (checked): the verdict names this commit
2026-10-10 10:58 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 11: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-10 11:01 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-delivery:view -->
**Delivery** `novox/mesh-catalog@6f2c76ee7139` — **delivered** since 2026-10-10T11:01:21Z
**Delivery plan** — builds new: modules/mesh-issues, sent nowhere; no bus step
**Transitions**
- 2026-10-10 10:56 (new) → proposed (announced): novox/mesh-catalog#172's head announced
- 2026-10-10 10:58 proposed → checked (checked): the verdict names this commit
- 2026-10-10 10:58 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 11: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-10 11:01 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/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: new: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 new: modules/mesh-issues, sent nowhere; no bus step
Run by the build seat on shanks as build-1791629620498698704 (builds --log build-1791629620498698704).
--- the gate: new:modules/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-10T10:50:49Z 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-10T10:50:49Z
modules the change moves:
- mesh-issues (added)
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 0 module(s) in 0 tier(s)
--- 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 36921 strings of 634 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: 70, as kept
testing modules/mesh-issues
ok mesh-issues/cmd/mesh-issues 5.404s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `2493e3e0`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: new: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 new: modules/mesh-issues, sent nowhere; no bus step
Run by the build seat on shanks as `build-1791629620498698704` (`builds --log build-1791629620498698704`).
```
--- the gate: new:modules/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-10T10:50:49Z 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-10T10:50:49Z
modules the change moves:
- mesh-issues (added)
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 0 module(s) in 0 tier(s)
--- 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 36921 strings of 634 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: 70, as kept
testing modules/mesh-issues
ok mesh-issues/cmd/mesh-issues 5.404s
--- its merge-check-typescript.sh (typescript toolchain)
```
mesh/merge-gate pass: builds new: modules/mesh-issues, sent nowhere; no bus step; every machine composes with the change as it did without (4 of 4 compose)
From the review: a taken key that cannot be read back, or a write never
confirmed, now tells the caller to get the number before opening again; an
owner entry naming a module is owned only by that module registered; link
targets get the secret guard; line separators are refused in one-line fields;
the acceptance test now proves the counter's own updates were contended.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: new: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 new: modules/mesh-issues, sent nowhere; no bus step
Run by the build seat on shanks as build-1791629805925866626 (builds --log build-1791629805925866626).
--- the gate: new:modules/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-10T10:50:49Z 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-10T10:50:49Z
modules the change moves:
- mesh-issues (added)
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 0 module(s) in 0 tier(s)
--- 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 36930 strings of 634 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: 70, as kept
testing modules/mesh-issues
ok mesh-issues/cmd/mesh-issues 5.383s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `6f2c76ee`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: new: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 new: modules/mesh-issues, sent nowhere; no bus step
Run by the build seat on shanks as `build-1791629805925866626` (`builds --log build-1791629805925866626`).
```
--- the gate: new:modules/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-10T10:50:49Z 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-10T10:50:49Z
modules the change moves:
- mesh-issues (added)
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 0 module(s) in 0 tier(s)
--- 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 36930 strings of 634 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: 70, as kept
testing modules/mesh-issues
ok mesh-issues/cmd/mesh-issues 5.383s
--- its merge-check-typescript.sh (typescript toolchain)
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Slice 1 of hq ADR 0275 / to-be 53 (
03-DESIGN/01-to-be/53-the-issue-tracker.md); naming per hq #272 (modulemesh-issues, seatissue-tracker).Acceptance: an agent opens an issue and gets the next number; two agents opening at the same moment never get the same one.
What it is. A Go bundle,
modules/mesh-issues, for the control-node. Declares and claims the seatissue-tracker(scope mesh) with verbsopen,get,list,move,note,link, served asissue-tracker.<verb>. Statesissues(history 8) andcounters, declared and made by the controller; the module makes no bus resource. Eventsopened,moved,noted,linked, each with the number, what changed, who and when. Settings (trusted, terminal only):first-number(365, after hq's highest issue on main and every open branch today) andowners, the registered listlocated-inmay name (hq's repositories and every catalogue module).Numbers. The counter is advanced by the SDK's compare-and-set
State(...).Increment(mesh-sdk #16, go/v0.1.12), in bounded rounds with jitter; it is started once byCreateat max(first-number - 1, highest issue kept). A refused open takes no number. An issue is written byCreate, never over a kept key (a loud fault, number left unused); a write whose answer was lost is recognised as its own by the open's id. A number is never handed out twice; it may be skipped only when the bus fails between the counter and the issue, and the answer says which.Cycle rules at the write (hq
00-META/checks/cycle.py): five statuses; located needs located-in; resolved needs located-in and fixed-by; a core issue (same regex as cycle.py) resolves with replayR<n>or replay-none; wontfix needs a reason. A refused move changes nothing. An issue opened with arecord(its hq folder) keeps its status there; move refuses it.Input. Unknown arguments refused; size limits on every field; no control or format characters in one-line fields; a folder name is a slug, not a path; design paths, link targets and numbers by strict shape; text shaped like a credential refused.
Who acted: not proven yet. ADR 0275 §5 records the caller from the bus credential. The runtime hands a module no caller on a tool call (SDK
Tool.Rungets name and arguments; the tool runner is not told who called, hq issue 340), so every change is recorded as byunproven, and no argument can name a caller. This needs runtime and controller work before the actor is real.Tests (
go test -race ./..., run by merge-check):TestFiftyOpensAtOnceFromTwoInstancesGetFiftyDistinctConsecutiveNumbers: an embedded JetStream server, two instances of the bundle (the test binary re-executed) speaking MCP to a runtime played by the test against the buckets the manifest declares; 50 opens at once give 365..414 once each, 50 issues, 50 events; it asserts writers actually collided (about 400-460 lost writes retried locally).Mutation: the counter written without its revision check (get + put) fails the acceptance test (duplicate numbers, caught loudly by the issue's create).
Merge only after: mesh-sdk go/v0.1.12 is tagged (it is) and the runtime that serves
mesh/state.create/updateis live where this runs (mesh-tools #23). Not assigned to any node.MESH_GATE=<controller> sh merge-check.shpasses locally;module check: ok, keeps state issues, counters.Delivery
novox/mesh-catalog@6f2c76ee7139— delivered since 2026-10-10T11:01:21ZDelivery plan — builds new: modules/mesh-issues, sent nowhere; no bus step
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
2493e3e0mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: new: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 new: modules/mesh-issues, sent nowhere; no bus step
Run by the build seat on shanks as
build-1791629620498698704(builds --log build-1791629620498698704).Merge check at
6f2c76eemesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: new: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 new: modules/mesh-issues, sent nowhere; no bus step
Run by the build seat on shanks as
build-1791629805925866626(builds --log build-1791629805925866626).