move to diagnosing or fixing needs by, the issue's worker as who@node (lower case, at most 120 bytes, refused with a secret's shape). The issue keeps worker {by, since, active} while at either status; any other status ends it (released on the event). by or take-over on another status is refused.
Another worker is refused while the worker is current, naming the worker, since and last active; take-over with a reason takes it over and notes it. A worker with no move, note, link or set by a caller for worker-stale-after (setting, default 24h) is stale: list rows say stale, get says worker-stale, and a take-over needs no reason (still noted). The tracker's own writes (triage, duplicate check, delivery notes) keep no worker current.
resolved is reached only from fixing (or resolved, to correct what it holds).
The moved event carries by (the worker, or who acted when the move names none), since, caller, and took-over-from / take-over / released when they apply.
unresolved (duplicate check, triage, ready-to-verify) counts fixing as not closed.
Verb descriptions of move, get, list say all this; README and the settings default (worker-stale-after: 24h) updated.
Tests: worker_test.go (one test per refusal: another worker at diagnosing and at fixing, take-over noted, stale with a moving clock including a caller note vs the tracker's own, the bound is the setting, a move on ends the work, fixing not closed, the verb's arguments and schema) and new rows in the cycle-rules table test (resolved from open, located, diagnosing refused; by missing, malformed, with a secret, on another status; take-over on another status or with nobody to take from). go test -race ./... passes; the words check passes.
hq issue 399, decided in hq ADR 0283 (hq#295).
- New status `fixing` between `located` and `resolved`.
- `move` to `diagnosing` or `fixing` needs `by`, the issue's worker as who@node (lower case, at most 120 bytes, refused with a secret's shape). The issue keeps `worker` {by, since, active} while at either status; any other status ends it (`released` on the event). `by` or `take-over` on another status is refused.
- Another worker is refused while the worker is current, naming the worker, since and last active; `take-over` with a reason takes it over and notes it. A worker with no move, note, link or set by a caller for `worker-stale-after` (setting, default 24h) is stale: `list` rows say `stale`, `get` says `worker-stale`, and a take-over needs no reason (still noted). The tracker's own writes (triage, duplicate check, delivery notes) keep no worker current.
- `resolved` is reached only from `fixing` (or `resolved`, to correct what it holds).
- The `moved` event carries `by` (the worker, or who acted when the move names none), `since`, `caller`, and `took-over-from` / `take-over` / `released` when they apply.
- `unresolved` (duplicate check, triage, ready-to-verify) counts `fixing` as not closed.
- Verb descriptions of `move`, `get`, `list` say all this; README and the settings default (`worker-stale-after: 24h`) updated.
Tests: `worker_test.go` (one test per refusal: another worker at diagnosing and at fixing, take-over noted, stale with a moving clock including a caller note vs the tracker's own, the bound is the setting, a move on ends the work, fixing not closed, the verb's arguments and schema) and new rows in the cycle-rules table test (resolved from open, located, diagnosing refused; by missing, malformed, with a secret, on another status; take-over on another status or with nobody to take from). `go test -race ./...` passes; the words check passes.
Two agents could start on one issue without seeing each other, and an issue
could be resolved without anyone having said they started its fix. A move to
diagnosing or fixing now names by, the worker as who@node; get and list show
the worker with since and stale; another worker is refused while it is
current unless take-over says why (noted); a worker untouched for
worker-stale-after (24h) may be taken over from without a reason. Resolved is
reached only from fixing. The moved event carries by, since and caller.
Fixing counts as not closed for the triage and the duplicate check.
hq ADR 0283.
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Machines
mesh-issues on novox: passed — healthy 3 times over 2m30s
mesh-sdk on every machine running it: sent
mesh-issues on the rest running it: sent
Transitions
2026-10-10 19:10 (new) → proposed (announced): novox/mesh-catalog#189's head announced
2026-10-10 19:12 proposed → checked (checked): the verdict names this commit
2026-10-10 19:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 19:15 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 19:21 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 19:24 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@a73b04843dd1` — **delivered** since 2026-10-10T19:24:34Z
**Delivery plan** — builds mesh-issues → novox; no bus step
- tier 0: mesh-issues
- novox: receives mesh-issues
**Group** `feat/399-fixing-status`, in order: novox/hq@8cdc9706e1c0 → novox/mesh-catalog@a73b04843dd1
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Machines**
- mesh-issues on novox: passed — healthy 3 times over 2m30s
- mesh-sdk on every machine running it: sent
- mesh-issues on the rest running it: sent
**Transitions**
- 2026-10-10 19:10 (new) → proposed (announced): novox/mesh-catalog#189's head announced
- 2026-10-10 19:12 proposed → checked (checked): the verdict names this commit
- 2026-10-10 19:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 19:15 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 19:21 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 19:24 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/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/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/triage_test.go, modules/mesh-issues/cmd/mesh-issues/worker_test.go
Run by the build seat on ace as build-1791659287204606226 (builds --log build-1791659287204606226).
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, keeps state issues, counters, grooming
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-10T19:01:59Z 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-10T19:01:59Z
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/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/triage_test.go and modules/mesh-issues/cmd/mesh-issues/worker_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 39054 strings of 650 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s
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 5.740s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `11afde55`
- `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/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/triage_test.go, modules/mesh-issues/cmd/mesh-issues/worker_test.go
Run by the build seat on ace as `build-1791659287204606226` (`builds --log build-1791659287204606226`).
```
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, keeps state issues, counters, grooming
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-10T19:01:59Z 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-10T19:01:59Z
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/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/triage_test.go and modules/mesh-issues/cmd/mesh-issues/worker_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 39054 strings of 650 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s
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 5.740s
--- its merge-check-typescript.sh (typescript toolchain)
```
The note's by is who acted as the runtime proves it (ADR 0275 §5); the
note's text names both workers. Tests for a resolved issue corrected, link
and set keeping the worker current, and a take-over reason with a secret's
shape. The ready-to-verify note says an issue resolves from fixing.
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/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/triage_test.go, modules/mesh-issues/cmd/mesh-issues/worker_test.go
Run by the build seat on ace as build-1791659457066602099 (builds --log build-1791659457066602099).
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, keeps state issues, counters, grooming
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-10T19:01:59Z 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-10T19:01:59Z
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/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/triage_test.go and modules/mesh-issues/cmd/mesh-issues/worker_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 39054 strings of 650 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: 69, as kept
testing modules/mesh-issues
ok mesh-issues/cmd/mesh-issues 4.771s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `a73b0484`
- `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/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/triage_test.go, modules/mesh-issues/cmd/mesh-issues/worker_test.go
Run by the build seat on ace as `build-1791659457066602099` (`builds --log build-1791659457066602099`).
```
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, keeps state issues, counters, grooming
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-10T19:01:59Z 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-10T19:01:59Z
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/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/triage_test.go and modules/mesh-issues/cmd/mesh-issues/worker_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 39054 strings of 650 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: 69, as kept
testing modules/mesh-issues
ok mesh-issues/cmd/mesh-issues 4.771s
--- 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.
hq issue 399, decided in hq ADR 0283 (hq#295).
fixingbetweenlocatedandresolved.movetodiagnosingorfixingneedsby, the issue's worker as who@node (lower case, at most 120 bytes, refused with a secret's shape). The issue keepsworker{by, since, active} while at either status; any other status ends it (releasedon the event).byortake-overon another status is refused.take-overwith a reason takes it over and notes it. A worker with no move, note, link or set by a caller forworker-stale-after(setting, default 24h) is stale:listrows saystale,getsaysworker-stale, and a take-over needs no reason (still noted). The tracker's own writes (triage, duplicate check, delivery notes) keep no worker current.resolvedis reached only fromfixing(orresolved, to correct what it holds).movedevent carriesby(the worker, or who acted when the move names none),since,caller, andtook-over-from/take-over/releasedwhen they apply.unresolved(duplicate check, triage, ready-to-verify) countsfixingas not closed.move,get,listsay all this; README and the settings default (worker-stale-after: 24h) updated.Tests:
worker_test.go(one test per refusal: another worker at diagnosing and at fixing, take-over noted, stale with a moving clock including a caller note vs the tracker's own, the bound is the setting, a move on ends the work, fixing not closed, the verb's arguments and schema) and new rows in the cycle-rules table test (resolved from open, located, diagnosing refused; by missing, malformed, with a secret, on another status; take-over on another status or with nobody to take from).go test -race ./...passes; the words check passes.Delivery
novox/mesh-catalog@a73b04843dd1— delivered since 2026-10-10T19:24:34ZDelivery plan — builds mesh-issues → novox; no bus step
Group
feat/399-fixing-status, in order: novox/hq@8cdc9706e1 → novox/mesh-catalog@a73b04843dMachines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
11afde55mesh/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
Run by the build seat on ace as
build-1791659287204606226(builds --log build-1791659287204606226).Merge check at
a73b0484mesh/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
Run by the build seat on ace as
build-1791659457066602099(builds --log build-1791659457066602099).