mesh-issues: take every condition key the controller raises and every delivery id mesh-delivery gives (hq issue 475) #218

Merged
mesh-admin merged 2 commits from fix/475-a-delivery-condition-can-be-tracked into main 2026-10-11 17:28:34 +00:00
Contributor

Fixes novox/hq issue 475 (the tracker refuses to link a condition whose key holds a slash, as delivery conditions' keys do). The delivery link kind had the same fault and is fixed here too.

Cause. checkTarget held its own patterns instead of the owners' rules:

  • condition: ^[a-z0-9][a-z0-9._:=@-]{0,199}$. A delivery's condition key carries its repository as owner/name, so delivery.novox/mesh-controller_d2e9dc61590f.stalled (the key exactly as mesh-controller.status named it) was refused, no issue could track a delivery's condition, and the operator's alert kept saying "No issue tracks this yet" (ADR 0285).
  • delivery: ^[A-Za-z0-9][A-Za-z0-9._:-]{0,99}$. Every delivery id is owner/repo@commit12, so no delivery could be linked at all.

Fix: condition keys. The tracker mirrors the controller's rule, cited in the code: mesh-controller internal/conditions/condition.go, Key composes <scope>.<id>.<kind> with the id split on its dots and every token made of A-Za-z0-9_=/- (anything else becomes _), and Observation.check refuses a scope not in Scopes. A condition link now takes at least three dot-separated tokens, the first one of the controller's 13 scopes, each token non-empty and of A-Za-z0-9_=/-, at most 255 bytes (the controller sets no bound; the tracker keeps a link one line). It now refuses what the controller never raises: : and @ (the controller makes them _), an unknown scope, a key without an id, an empty token, a wildcard.

Fix: delivery ids. The tracker mirrors mesh-delivery's IDOf (modules/mesh-delivery/cmd/mesh-delivery/model.go): the repository as owner/name, lower-cased, then @, then at most 12 characters of the commit. The check is ^[a-z0-9][a-z0-9._-]{0,99}/[a-z0-9][a-z0-9._-]{0,99}@[0-9a-f]{1,12}$. The link tool's description gives an example id.

Router. messenger matches the key verbatim from the condition event against the tracker's answer, so a slash already worked there; a new test proves it end to end (decoded event with the real delivery key, message says "Tracked as issue 475").

Tests.

  • conditionkey_test.go links real condition keys (the delivery key from issue 475; machine.novox.telegram.telegram-token.secret-given, module.openrazer.shanks.relogin-needed, mesh.hand-acts.plans_go.healer-wanted, delivery.leaf.over-budget from mesh-controller.conditions on 2026-10-11) and real delivery ids (novox/mesh-controller@0f853e93fa11, novox/mesh-catalog@7714f164c33f, novox/hq@34bdb1a34f5a, novox/mesh-media-catalog@dd3f0abb3f78, novox/mesh-tools@82aefe1988c2 from mesh-delivery.deliveries on 2026-10-11; all 231 live ids have this shape), and lists shapes neither owner produces. All three tracker tests failed on main.
  • Three existing test targets no owner could produce (healer-wanted.ace.backup, token=abcdefgh123, d-2026-10-10.3) were changed to real-shaped ones; the secret-shape case still proves the secret refusal.

go vet ./... and go test -race ./... -count=1 pass in mesh-issues and messenger; the words check passes.

Fixes novox/hq issue 475 (the tracker refuses to link a condition whose key holds a slash, as delivery conditions' keys do). The `delivery` link kind had the same fault and is fixed here too. **Cause.** `checkTarget` held its own patterns instead of the owners' rules: - condition: `^[a-z0-9][a-z0-9._:=@-]{0,199}$`. A delivery's condition key carries its repository as owner/name, so `delivery.novox/mesh-controller_d2e9dc61590f.stalled` (the key exactly as `mesh-controller.status` named it) was refused, no issue could track a delivery's condition, and the operator's alert kept saying "No issue tracks this yet" (ADR 0285). - delivery: `^[A-Za-z0-9][A-Za-z0-9._:-]{0,99}$`. Every delivery id is `owner/repo@commit12`, so no delivery could be linked at all. **Fix: condition keys.** The tracker mirrors the controller's rule, cited in the code: mesh-controller `internal/conditions/condition.go`, `Key` composes `<scope>.<id>.<kind>` with the id split on its dots and every token made of `A-Za-z0-9_=/-` (anything else becomes `_`), and `Observation.check` refuses a scope not in `Scopes`. A condition link now takes at least three dot-separated tokens, the first one of the controller's 13 scopes, each token non-empty and of `A-Za-z0-9_=/-`, at most 255 bytes (the controller sets no bound; the tracker keeps a link one line). It now refuses what the controller never raises: `:` and `@` (the controller makes them `_`), an unknown scope, a key without an id, an empty token, a wildcard. **Fix: delivery ids.** The tracker mirrors mesh-delivery's `IDOf` (modules/mesh-delivery/cmd/mesh-delivery/model.go): the repository as owner/name, lower-cased, then `@`, then at most 12 characters of the commit. The check is `^[a-z0-9][a-z0-9._-]{0,99}/[a-z0-9][a-z0-9._-]{0,99}@[0-9a-f]{1,12}$`. The link tool's description gives an example id. **Router.** messenger matches the key verbatim from the condition event against the tracker's answer, so a slash already worked there; a new test proves it end to end (decoded event with the real delivery key, message says "Tracked as issue 475"). **Tests.** - `conditionkey_test.go` links real condition keys (the delivery key from issue 475; `machine.novox.telegram.telegram-token.secret-given`, `module.openrazer.shanks.relogin-needed`, `mesh.hand-acts.plans_go.healer-wanted`, `delivery.leaf.over-budget` from `mesh-controller.conditions` on 2026-10-11) and real delivery ids (`novox/mesh-controller@0f853e93fa11`, `novox/mesh-catalog@7714f164c33f`, `novox/hq@34bdb1a34f5a`, `novox/mesh-media-catalog@dd3f0abb3f78`, `novox/mesh-tools@82aefe1988c2` from `mesh-delivery.deliveries` on 2026-10-11; all 231 live ids have this shape), and lists shapes neither owner produces. All three tracker tests failed on main. - Three existing test targets no owner could produce (`healer-wanted.ace.backup`, `token=abcdefgh123`, `d-2026-10-10.3`) were changed to real-shaped ones; the secret-shape case still proves the secret refusal. `go vet ./...` and `go test -race ./... -count=1` pass in mesh-issues and messenger; the words check passes.
mesh-admin added 1 commit 2026-10-11 17:22:33 +00:00
mesh-issues: take every condition key the controller raises, a delivery's with its slash among them (hq issue 475)
mesh/delivery superseded: a newer head of the same pull request
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)
7714f164c3
The tracker's own pattern refused the slash a delivery's id carries, so no issue
could track a delivery's condition and the operator's alert kept saying no issue
tracks it. Mirror the controller's key rule instead of a pattern of our own; a
router test proves a slashed key is matched and named end to end.
Author
Contributor

Delivery novox/mesh-catalog@98d494619f5a — delivered since 2026-10-11T17:34:13Z

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

Transitions

  • 2026-10-11 17:24 (new) → proposed (announced): novox/mesh-catalog#218's head announced
  • 2026-10-11 17:27 proposed → checked (checked): the verdict names this commit
  • 2026-10-11 17:27 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-11 17:30 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 17:30 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 17:34 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@98d494619f5a` — **delivered** since 2026-10-11T17:34:13Z **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 2m22s - mesh-issues on the rest running it: sent **Transitions** - 2026-10-11 17:24 (new) → proposed (announced): novox/mesh-catalog#218's head announced - 2026-10-11 17:27 proposed → checked (checked): the verdict names this commit - 2026-10-11 17:27 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-11 17:30 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 17:30 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 17:34 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`.
jschoubben added 1 commit 2026-10-11 17:24:25 +00:00
mesh-issues: take a delivery's id as mesh-delivery forms it, owner/repo@commit (hq issue 475)
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
98d494619f
The delivery link's own pattern refused the slash and the @ every delivery id
carries, so no delivery could be linked either. Mirror mesh-delivery's IDOf.
mesh-admin changed title from mesh-issues: take every condition key the controller raises, a delivery's with its slash (hq issue 475) to mesh-issues: take every condition key the controller raises and every delivery id mesh-delivery gives (hq issue 475) 2026-10-11 17:24:42 +00:00
Author
Contributor

Merge check at 7714f164

  • 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/cmd/mesh-issues/conditionkey_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/messenger/cmd/messenger/tracking_delivery_test.go

Run by the build seat on novox as build-1791739364850445083 (builds --log build-1791739364850445083).

--- 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, mesh-knowledge.knowledge_highest, 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T17:21:39Z 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-11T17:21:39Z

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/cmd/mesh-issues/conditionkey_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go and modules/messenger/cmd/messenger/tracking_delivery_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 41859 strings of 678 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.007s
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.677s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `7714f164` - `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/cmd/mesh-issues/conditionkey_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/messenger/cmd/messenger/tracking_delivery_test.go Run by the build seat on novox as `build-1791739364850445083` (`builds --log build-1791739364850445083`). ``` --- 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, mesh-knowledge.knowledge_highest, 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T17:21:39Z 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-11T17:21:39Z 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/cmd/mesh-issues/conditionkey_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go and modules/messenger/cmd/messenger/tracking_delivery_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 41859 strings of 678 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.007s 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.677s --- its merge-check-typescript.sh (typescript toolchain) ```
Author
Contributor

Merge check at 98d49461

  • 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/cmd/mesh-issues/conditionkey_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/messenger/cmd/messenger/tracking_delivery_test.go

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

--- 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, mesh-knowledge.knowledge_highest, 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T17:21:39Z 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-11T17:21:39Z

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/cmd/mesh-issues/conditionkey_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go and modules/messenger/cmd/messenger/tracking_delivery_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 41859 strings of 678 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.532s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `98d49461` - `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/cmd/mesh-issues/conditionkey_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/messenger/cmd/messenger/tracking_delivery_test.go Run by the build seat on shanks as `build-1791739487739744037` (`builds --log build-1791739487739744037`). ``` --- 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, mesh-knowledge.knowledge_highest, 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T17:21:39Z 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-11T17:21:39Z 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/cmd/mesh-issues/conditionkey_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go and modules/messenger/cmd/messenger/tracking_delivery_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 41859 strings of 678 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.532s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-admin merged commit 9f63231db9 into main 2026-10-11 17:28:34 +00:00
mesh-admin deleted branch fix/475-a-delivery-condition-can-be-tracked 2026-10-11 17:28:34 +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#218