i3status-rust, docker-compose: each module declares the packages it needs (issue 628) #271

Closed
mesh-admin wants to merge 2 commits from fix/628-modules-declare-every-package-they-need into main
Contributor

Part of novox/hq issue 628 (the controller's comments are novox/mesh-controller, branch fix/628-packages-are-shared).

Several modules may declare one package (ADR 0303). Declaring a package says the module needs the program; what one module owns alone is its files, paths and units, and a seat held once.

  • i3status-rust declares pacman-contrib, which its update block runs (checkupdates). It relied on the pacman module because its README said two modules declaring one package is refused.
  • docker-compose's README no longer says the package is given back when the module goes: the node-engine never removes a package a declaration stopped naming (ADR 0303 §2).

Nothing changes on disk: pacman-contrib is already installed wherever pacman is assigned.

Acceptance: assigning i3status-rust beside pacman on a node is accepted, and mesh-controller.plan for that node lists pacman-contrib from both modules.

Part of novox/hq issue 628 (the controller's comments are novox/mesh-controller, branch fix/628-packages-are-shared). Several modules may declare one package (ADR 0303). Declaring a package says the module needs the program; what one module owns alone is its files, paths and units, and a seat held once. - i3status-rust declares `pacman-contrib`, which its update block runs (`checkupdates`). It relied on the pacman module because its README said two modules declaring one package is refused. - docker-compose's README no longer says the package is given back when the module goes: the node-engine never removes a package a declaration stopped naming (ADR 0303 §2). Nothing changes on disk: pacman-contrib is already installed wherever pacman is assigned. Acceptance: assigning i3status-rust beside pacman on a node is accepted, and `mesh-controller.plan` for that node lists pacman-contrib from both modules.
mesh-admin added 1 commit 2026-10-13 11:52:51 +00:00
i3status-rust, docker-compose: each module declares the packages it needs (issue 628)
mesh/merge-gate out of date: judged against trunk 19ecad261cf2, the trunk is now 8922c890595b; judged again on a recheck or when it is merged
mesh/repo-check out of date: judged against trunk 19ecad261cf2, the trunk is now 8922c890595b; judged again on a recheck or when it is merged
mesh/delivery superseded: a newer head of the same pull request
e79197d5a1
i3status-rust left pacman-contrib to the pacman module because two modules declaring one package was once refused; ADR 0303 allows it, so the bar declares what its update block runs. docker-compose's README said the package goes with the module, which the node-engine never does.
Author
Contributor

Delivery novox/mesh-catalog@ea73e713f503 — closed since 2026-10-25T17:26:57Z

Transitions

  • 2026-10-13 11:59 (new) → proposed (announced): novox/mesh-catalog#271's head announced
  • 2026-10-13 12:02 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-13 12:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-13 12:07 ready → proposed (trunk moved): out of date: judged against trunk cd23928320, the trunk is now 0d723484a84a; judged again on a recheck or when it is merged
  • 2026-10-23 08:09 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-23 08:09 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
  • 2026-10-25 15:32 rejected → proposed (recheck): its mesh/check judged it again: failed: shanks: the check of novox/mesh-catalog#271 failed: beside novox/mesh-controller: git fetch: error: | ea73e713f…
  • 2026-10-25 15:32 proposed → rejected (refused): a verdict names this commit and the trunk's head as its trunk commit, and the gate failed or could not run, or the repository's own check failed
  • 2026-10-25 17:26 rejected → closed (closed): the pull request closed unmerged

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@ea73e713f503` — **closed** since 2026-10-25T17:26:57Z **Transitions** - 2026-10-13 11:59 (new) → proposed (announced): novox/mesh-catalog#271's head announced - 2026-10-13 12:02 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-13 12:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-13 12:07 ready → proposed (trunk moved): out of date: judged against trunk cd239283207a, the trunk is now 0d723484a84a; judged again on a recheck or when it is merged - 2026-10-23 08:09 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-23 08:09 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-25 15:32 rejected → proposed (recheck): its mesh/check judged it again: failed: shanks: the check of novox/mesh-catalog#271 failed: beside novox/mesh-controller: git fetch: error: | ea73e713f… - 2026-10-25 15:32 proposed → rejected (refused): a verdict names this commit and the trunk's head as its trunk commit, and the gate failed or could not run, or the repository's own check failed - 2026-10-25 17:26 rejected → closed (closed): the pull request closed unmerged The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at e79197d5
Judged: head e79197d5a1dd merged into trunk 19ecad261cf2; read beside it: mesh-controller 584aa2d7d7a5, mesh-controller-main 584aa2d7d7a5, mesh-host 7a41e120635b, mesh-tools 954e1a53eef9

  • mesh/merge-gate: FAIL — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "i3status-rust.updates": id already used by resource 194. Two resources with one identity cannot both be tracked (modules: docker-compose, i3status-rust)
  • mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestItClaimsTheBarSeatAndRequiresTheXDisplay (0.00s); and TestItOwnsItsFilesAsWrittenInTheModule

Delivery plan — builds docker-compose, i3status-rust → g14, shanks; no bus step

  • tier 0: docker-compose, i3status-rust
  • g14: receives docker-compose, i3status-rust
  • shanks: receives docker-compose, i3status-rust
  • grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before docker-compose, i3status-rust is judged on its first machine

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

--- the gate: docker-compose, i3status-rust
docker-compose: ok, 9 tool(s)
i3status-rust: ok, 4 tool(s)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 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-13T11:13:29Z 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: FAIL — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "i3status-rust.updates": id already used by resource 194. Two resources with one identity cannot both be tracked
judged by controller development build against the facts of 2026-10-13T11:13:29Z

fails:
  - a machine (f35): nothing could be sent to it with this change — resource "i3status-rust.updates": id already used by resource 194. Two resources with one identity cannot both be tracked
  - a machine (yvbpsm): nothing could be sent to it with this change — resource "i3status-rust.updates": id already used by resource 170. Two resources with one identity cannot both be tracked

modules the change moves:
  - i3status-rust (changed)

machines:
  - a machine (f35): does not compose; the change adds 1 resource(s) and removes 0 (+package:i3status-rust.updates)
  - 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): does not compose; the change adds 1 resource(s) and removes 0 (+package:i3status-rust.updates)

a merge would rebuild 2 module(s) in 1 tier(s): docker-compose, i3status-rust
mesh-controller: the change fails the merge gate
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.042s
words: 12 retired words and 70 daemons' lines, none in the 46255 strings of 714 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/secrets	0.013s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
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: 66, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.273s
testing modules/docker-compose
ok  	docker-compose/cmd/docker-compose-tools	1.317s
testing modules/i3status-rust
--- FAIL: TestItClaimsTheBarSeatAndRequiresTheXDisplay (0.00s)
    manifest_test.go:27: packages: [i3status-rust pacman-contrib], absent []
--- FAIL: TestItOwnsItsFilesAsWrittenInTheModule (0.00s)
    manifest_test.go:38: updates is a package, not a file
FAIL
FAIL	i3statusrust/cmd/i3status-rust-tools	0.314s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestItClaimsTheBarSeatAndRequiresTheXDisplay (0.00s)
    manifest_test.go:27: packages: [i3status-rust pacman-contrib], absent []
--- FAIL: TestItOwnsItsFilesAsWrittenInTheModule (0.00s)
    manifest_test.go:38: updates is a package, not a file
FAIL	i3statusrust/cmd/i3status-rust-tools	0.314s
**Merge check** at `e79197d5` Judged: head `e79197d5a1dd` merged into trunk `19ecad261cf2`; read beside it: mesh-controller `584aa2d7d7a5`, mesh-controller-main `584aa2d7d7a5`, mesh-host `7a41e120635b`, mesh-tools `954e1a53eef9` - `mesh/merge-gate`: **FAIL** — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "i3status-rust.updates": id already used by resource 194. Two resources with one identity cannot both be tracked (modules: docker-compose, i3status-rust) - `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestItClaimsTheBarSeatAndRequiresTheXDisplay (0.00s); and TestItOwnsItsFilesAsWrittenInTheModule **Delivery plan** — builds docker-compose, i3status-rust → g14, shanks; no bus step - tier 0: docker-compose, i3status-rust - g14: receives docker-compose, i3status-rust - shanks: receives docker-compose, i3status-rust - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before docker-compose, i3status-rust is judged on its first machine Run by the build seat on novox as `build-1791892392389908921` (`builds --log build-1791892392389908921`). ``` --- the gate: docker-compose, i3status-rust docker-compose: ok, 9 tool(s) i3status-rust: ok, 4 tool(s) long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 2 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-13T11:13:29Z 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: FAIL — 2 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "i3status-rust.updates": id already used by resource 194. Two resources with one identity cannot both be tracked judged by controller development build against the facts of 2026-10-13T11:13:29Z fails: - a machine (f35): nothing could be sent to it with this change — resource "i3status-rust.updates": id already used by resource 194. Two resources with one identity cannot both be tracked - a machine (yvbpsm): nothing could be sent to it with this change — resource "i3status-rust.updates": id already used by resource 170. Two resources with one identity cannot both be tracked modules the change moves: - i3status-rust (changed) machines: - a machine (f35): does not compose; the change adds 1 resource(s) and removes 0 (+package:i3status-rust.updates) - 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): does not compose; the change adds 1 resource(s) and removes 0 (+package:i3status-rust.updates) a merge would rebuild 2 module(s) in 1 tier(s): docker-compose, i3status-rust mesh-controller: the change fails the merge gate --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.042s words: 12 retired words and 70 daemons' lines, none in the 46255 strings of 714 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/secrets 0.013s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) 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: 66, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.273s testing modules/docker-compose ok docker-compose/cmd/docker-compose-tools 1.317s testing modules/i3status-rust --- FAIL: TestItClaimsTheBarSeatAndRequiresTheXDisplay (0.00s) manifest_test.go:27: packages: [i3status-rust pacman-contrib], absent [] --- FAIL: TestItOwnsItsFilesAsWrittenInTheModule (0.00s) manifest_test.go:38: updates is a package, not a file FAIL FAIL i3statusrust/cmd/i3status-rust-tools 0.314s FAIL --- what failed, picked from the whole of its output (the whole is in the build's log) --- FAIL: TestItClaimsTheBarSeatAndRequiresTheXDisplay (0.00s) manifest_test.go:27: packages: [i3status-rust pacman-contrib], absent [] --- FAIL: TestItOwnsItsFilesAsWrittenInTheModule (0.00s) manifest_test.go:38: updates is a package, not a file FAIL i3statusrust/cmd/i3status-rust-tools 0.314s ```
mesh-admin added 1 commit 2026-10-13 11:59:33 +00:00
i3status-rust: name the pacman-contrib package apart from the update script, and expect it in the test (issue 628)
mesh/merge-gate out of date: judged against trunk cd239283207a, the trunk is now 0d723484a84a; judged again on a recheck or when it is merged
mesh/repo-check out of date: judged against trunk cd239283207a, the trunk is now 0d723484a84a; judged again on a recheck or when it is merged
mesh/delivery closed: the pull request closed unmerged
mesh/check failed: shanks: novox/mesh-catalog#271 does not merge into the trunk: files in conflict: modules/i3status-rust/README.md | ea73e713f503 on …
ea73e713f5
The package took the id `updates`, which the update script already holds, so the node-engine refused two resources with one identity.
Author
Contributor

Merge check at ea73e713
Judged: head ea73e713f503 merged into trunk cd239283207a; read beside it: mesh-controller 584aa2d7d7a5, mesh-controller-main 584aa2d7d7a5, mesh-host 7a41e120635b, mesh-tools 954e1a53eef9

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: docker-compose, i3status-rust)
  • 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 docker-compose, i3status-rust → g14, shanks; no bus step

  • tier 0: docker-compose, i3status-rust
  • g14: receives docker-compose, i3status-rust
  • shanks: receives docker-compose, i3status-rust
  • grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before docker-compose, i3status-rust is judged on its first machine

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

--- the gate: docker-compose, i3status-rust
docker-compose: ok, 9 tool(s)
i3status-rust: ok, 4 tool(s)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 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-13T11:13:29Z 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-13T11:13:29Z

modules the change moves:
  - i3status-rust (changed)

machines:
  - a machine (f35): composes; the change adds 1 resource(s) and removes 0 (+package:i3status-rust.checkupdates)
  - 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; the change adds 1 resource(s) and removes 0 (+package:i3status-rust.checkupdates)

a merge would rebuild 2 module(s) in 1 tier(s): docker-compose, i3status-rust
--- 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 46281 strings of 715 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/secrets	0.012s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
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: 66, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.218s
testing modules/docker-compose
ok  	docker-compose/cmd/docker-compose-tools	1.318s
testing modules/i3status-rust
ok  	i3statusrust/cmd/i3status-rust-tools	1.280s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `ea73e713` Judged: head `ea73e713f503` merged into trunk `cd239283207a`; read beside it: mesh-controller `584aa2d7d7a5`, mesh-controller-main `584aa2d7d7a5`, mesh-host `7a41e120635b`, mesh-tools `954e1a53eef9` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: docker-compose, i3status-rust) - `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 docker-compose, i3status-rust → g14, shanks; no bus step - tier 0: docker-compose, i3status-rust - g14: receives docker-compose, i3status-rust - shanks: receives docker-compose, i3status-rust - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before docker-compose, i3status-rust is judged on its first machine Run by the build seat on shanks as `build-1791892793118237180` (`builds --log build-1791892793118237180`). ``` --- the gate: docker-compose, i3status-rust docker-compose: ok, 9 tool(s) i3status-rust: ok, 4 tool(s) long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 2 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-13T11:13:29Z 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-13T11:13:29Z modules the change moves: - i3status-rust (changed) machines: - a machine (f35): composes; the change adds 1 resource(s) and removes 0 (+package:i3status-rust.checkupdates) - 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; the change adds 1 resource(s) and removes 0 (+package:i3status-rust.checkupdates) a merge would rebuild 2 module(s) in 1 tier(s): docker-compose, i3status-rust --- 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 46281 strings of 715 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/secrets 0.012s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) 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: 66, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.218s testing modules/docker-compose ok docker-compose/cmd/docker-compose-tools 1.318s testing modules/i3status-rust ok i3statusrust/cmd/i3status-rust-tools 1.280s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-tools closed this pull request 2026-10-25 17:26:54 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#271