mesh-files holds node-files: file work on a node with trash, owned paths and an act log, no shell needed (issue 900, ADR 0394) #332

2026-10-16T13:10:52Z

mesh-tools commented

2026-10-16 13:10:52 +00:00

Issue 900, ADR 0394. The module mesh-files holds the seat node-files (mesh-controller, same group feat/900-node-files): reads with a sudo fallback, writes, copy and move that overwrite into the trash, delete into the trash, restore with a reason and override, owned paths guarded, and an act log. The work's commits are folded into one so no build output reaches the forge.

Built and reviewed locally (independent review, larger model) before this push; go test ./... in modules/mesh-files passes. Follow-ups: issues 903 (copy between nodes) and 904.

Issue 900, ADR 0394. The module mesh-files holds the seat node-files (mesh-controller, same group feat/900-node-files): reads with a sudo fallback, writes, copy and move that overwrite into the trash, delete into the trash, restore with a reason and override, owned paths guarded, and an act log. The work's commits are folded into one so no build output reaches the forge. Built and reviewed locally (independent review, larger model) before this push; `go test ./...` in modules/mesh-files passes. Follow-ups: issues 903 (copy between nodes) and 904.

mesh-tools added 1 commit 2026-10-16 13:10:52 +00:00

mesh-files: the holder of node-files, reads and writes with trash, owned paths and an act log, so file work on a node needs no shell (issue 900, ADR 0394)

mesh/delivery-group group feat/900-node-files checking: composed check out of date: novox/mesh-controller@210f7cf5e64b was judged against trunk 611e2275cf7c, t…

Details

mesh/merge-gate out of date: judged against trunk 3db85a0dde83, the trunk is now 8b53a3663244; judged again on a recheck or when it is merged

Details

mesh/repo-check out of date: judged against trunk 3db85a0dde83, the trunk is now 8b53a3663244; judged again on a recheck or when it is merged

Details

mesh/delivery superseded: a newer head of the same pull request

Details

5d98bcc0db

mesh-tools commented

2026-10-16 13:10:59 +00:00

Delivery novox/mesh-catalog@d4a9260847ec — delivered since 2026-10-16T14:25:14Z

Delivery plan — builds new: modules/mesh-files, sent nowhere; no bus step

Group feat/900-node-files, in order: novox/mesh-controller@f4ddddd59d → novox/mesh-catalog@d4a9260847

novox/mesh-controller@f4ddddd59d before novox/mesh-catalog@d4a9260847: version skew
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

Transitions

2026-10-16 14:16 (new) → proposed (announced): novox/mesh-catalog#332's head announced
2026-10-16 14:19 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-16 14:19 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-16 14:25 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-16 14:25 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.

**Delivery** `novox/mesh-catalog@d4a9260847ec` — **delivered** since 2026-10-16T14:25:14Z **Delivery plan** — builds new: modules/mesh-files, sent nowhere; no bus step **Group** `feat/900-node-files`, in order: novox/mesh-controller@f4ddddd59d9a → novox/mesh-catalog@d4a9260847ec - novox/mesh-controller@f4ddddd59d9a before novox/mesh-catalog@d4a9260847ec: version skew - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Transitions** - 2026-10-16 14:16 (new) → proposed (announced): novox/mesh-catalog#332's head announced - 2026-10-16 14:19 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 14:19 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 14:25 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-16 14:25 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-tools commented

2026-10-16 13:18:55 +00:00

Merge check at 5d98bcc0
Judged: head 5d98bcc0db5d merged into trunk 3db85a0dde83; read beside it: mesh-controller 0ceafb3fcf4d, mesh-controller-main 611e2275cf7c, mesh-host cd13f7726ef0, mesh-tools 7412c5b6c9c5
Siblings read beside it: novox/mesh-controller#360 210f7cf5e64b merged onto 611e2275cf7c (main); judged by sibling novox/mesh-controller#360 merge 0ceafb3fcf4d

mesh/merge-gate: PASS — every machine composes with the change as it did without (3 of 4 compose) (modules: new:modules/mesh-files)
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-files, sent nowhere; no bus step

read by no module's build: .gitignore

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

--- the gate: new:modules/mesh-files
mesh-files: ok, invokes seat:operator-channel.tell
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-16T13:14:38Z says they run
composing every machine as the mesh is
the bus's user list leaves out 6 user(s) the mesh has minted no credential for: controller, node.f35, provisioner.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 6 user(s) the mesh has minted no credential for: controller, node.f35, provisioner.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 6 user(s) the mesh has minted no credential for: controller, node.f35, provisioner.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 6 user(s) the mesh has minted no credential for: controller, node.f35, provisioner.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 (3 of 4 compose)
judged by controller development build against the facts of 2026-10-16T13:14:38Z

modules the change moves:
  - mesh-files (added)

machines:
  - a machine (f35): does not compose
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, 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)

notes:
  - a machine (f35) does not compose on the mesh today either: mesh-provisioner-client on f35 has no bus credential: nothing was issued for provisioner.f35, and a push would seal a placeholder its process cannot read (ygcyr/hq issue 203). `module issue mesh-provisioner-client --node f35`, then push again
  - mesh-files could not be tried on a machine: mesh-provisioner-client on f35 has no bus credential: nothing was issued for provisioner.f35, and a push would seal a placeholder its process cannot read (novox/hq issue 203). `module issue mesh-provisioner-client --node f35`, then push again
  - .gitignore 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 53512 strings of 801 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/mailstore	0.009s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.014s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.264s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.016s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.012s
templates: no module keeps a file's text inline but the 0 listed
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: 61, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.224s
testing modules/mesh-files
ok  	mesh-files/cmd/mesh-files	1.951s
--- its merge-check-typescript.sh (typescript toolchain)

**Merge check** at `5d98bcc0` Judged: head `5d98bcc0db5d` merged into trunk `3db85a0dde83`; read beside it: mesh-controller `0ceafb3fcf4d`, mesh-controller-main `611e2275cf7c`, mesh-host `cd13f7726ef0`, mesh-tools `7412c5b6c9c5` Siblings read beside it: novox/mesh-controller#360 `210f7cf5e64b` merged onto `611e2275cf7c` (main); judged by sibling novox/mesh-controller#360 merge 0ceafb3fcf4d - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (3 of 4 compose) (modules: new:modules/mesh-files) - `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-files, sent nowhere; no bus step - read by no module's build: .gitignore Run by the build seat on shanks as `build-1792156415588032656` (`builds --log build-1792156415588032656`). ``` --- the gate: new:modules/mesh-files mesh-files: ok, invokes seat:operator-channel.tell 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-16T13:14:38Z says they run composing every machine as the mesh is the bus's user list leaves out 6 user(s) the mesh has minted no credential for: controller, node.f35, provisioner.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 6 user(s) the mesh has minted no credential for: controller, node.f35, provisioner.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 6 user(s) the mesh has minted no credential for: controller, node.f35, provisioner.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 6 user(s) the mesh has minted no credential for: controller, node.f35, provisioner.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 (3 of 4 compose) judged by controller development build against the facts of 2026-10-16T13:14:38Z modules the change moves: - mesh-files (added) machines: - a machine (f35): does not compose - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, 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) notes: - a machine (f35) does not compose on the mesh today either: mesh-provisioner-client on f35 has no bus credential: nothing was issued for provisioner.f35, and a push would seal a placeholder its process cannot read (ygcyr/hq issue 203). `module issue mesh-provisioner-client --node f35`, then push again - mesh-files could not be tried on a machine: mesh-provisioner-client on f35 has no bus credential: nothing was issued for provisioner.f35, and a push would seal a placeholder its process cannot read (novox/hq issue 203). `module issue mesh-provisioner-client --node f35`, then push again - .gitignore 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 53512 strings of 801 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/mailstore 0.009s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/secrets 0.014s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.264s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.016s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.012s templates: no module keeps a file's text inline but the 0 listed 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: 61, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.224s testing modules/mesh-files ok mesh-files/cmd/mesh-files 1.951s --- its merge-check-typescript.sh (typescript toolchain) ```

mesh-tools referenced this pull request from novox/mesh-controller

2026-10-16 13:19:22 +00:00

The seat node-files: write, copy, move and delete a file on a node through the mesh, with trash and owned paths (issue 900, ADR 0394) #360

mesh-tools added the mesh/ready label 2026-10-16 14:13:57 +00:00

mesh-tools commented

2026-10-16 14:13:57 +00:00

ready at 5d98bcc0db

Reviewed by review-900@shanks: Approved at 5d98bcc0: one commit on main, mesh-files tree the same as the reviewed head, .gitignore adds two lines and drops none, its tests pass. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

ready at 5d98bcc0db5d9b6daefae26101f1e3eacf55bc07 Reviewed by review-900@shanks: Approved at 5d98bcc0: one commit on main, mesh-files tree the same as the reviewed head, .gitignore adds two lines and drops none, its tests pass. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

jschoubben added 1 commit 2026-10-16 14:16:05 +00:00

Merge remote-tracking branch 'origin/main' into feat/900-node-files

mesh/merge-gate head d4a9260847ec merged into trunk 8b53a3663244 beside mesh-controller#360@f4ddddd5 — pass: builds new: modules/mesh-files, sent nowhere; …

Details

mesh/repo-check head d4a9260847ec merged into trunk 8b53a3663244 beside mesh-controller#360@f4ddddd5 — pass: its merge-check.sh passed, each part in its to…

Details

mesh/delivery delivered

Details

mesh/delivery-group group feat/900-node-files delivered: every member is delivered

Details

d4a9260847

mesh-tools removed the mesh/ready label 2026-10-16 14:17:47 +00:00

mesh-tools commented

2026-10-16 14:17:47 +00:00

mesh-delivery: the label mesh/ready is taken off: no "ready at" comment by a listed account follows both the label's last addition and the last push; the head is now d4a9260847. Review it and mark that head with mesh-delivery.mark-ready, which writes label and comment in the order the forge counts.

mesh-delivery: the label mesh/ready is taken off: no "ready at" comment by a listed account follows both the label's last addition and the last push; the head is now d4a9260847ec9958e2c1c3a5128fc01ce67d4587. Review it and mark that head with `mesh-delivery.mark-ready`, which writes label and comment in the order the forge counts.

mesh-tools commented

2026-10-16 14:19:06 +00:00

Merge check at d4a92608
Judged: head d4a9260847ec merged into trunk 8b53a3663244; read beside it: mesh-controller d2c16e99b7a8, mesh-controller-main f45b4cb21301, mesh-host cd13f7726ef0, mesh-tools 7412c5b6c9c5
Siblings read beside it: novox/mesh-controller#360 f4ddddd59d9a merged onto f45b4cb21301 (main); judged by sibling novox/mesh-controller#360 merge d2c16e99b7a8

mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: new:modules/mesh-files)
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-files, sent nowhere; no bus step

read by no module's build: .gitignore

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

--- the gate: new:modules/mesh-files
mesh-files: ok, invokes seat:operator-channel.tell
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-16T14:14:07Z 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-16T14:14:07Z

modules the change moves:
  - mesh-files (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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, 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)

notes:
  - .gitignore 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 53587 strings of 801 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/mailstore	0.009s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.014s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.259s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.016s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.012s
templates: no module keeps a file's text inline but the 0 listed
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: 61, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.220s
testing modules/mesh-files
ok  	mesh-files/cmd/mesh-files	1.975s
--- its merge-check-typescript.sh (typescript toolchain)

**Merge check** at `d4a92608` Judged: head `d4a9260847ec` merged into trunk `8b53a3663244`; read beside it: mesh-controller `d2c16e99b7a8`, mesh-controller-main `f45b4cb21301`, mesh-host `cd13f7726ef0`, mesh-tools `7412c5b6c9c5` Siblings read beside it: novox/mesh-controller#360 `f4ddddd59d9a` merged onto `f45b4cb21301` (main); judged by sibling novox/mesh-controller#360 merge d2c16e99b7a8 - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: new:modules/mesh-files) - `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-files, sent nowhere; no bus step - read by no module's build: .gitignore Run by the build seat on shanks as `build-1792160167844776952` (`builds --log build-1792160167844776952`). ``` --- the gate: new:modules/mesh-files mesh-files: ok, invokes seat:operator-channel.tell 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-16T14:14:07Z 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-16T14:14:07Z modules the change moves: - mesh-files (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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, 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) notes: - .gitignore 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 53587 strings of 801 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/mailstore 0.009s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/secrets 0.014s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.259s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.016s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.012s templates: no module keeps a file's text inline but the 0 listed 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: 61, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.220s testing modules/mesh-files ok mesh-files/cmd/mesh-files 1.975s --- its merge-check-typescript.sh (typescript toolchain) ```

mesh-tools referenced this pull request from novox/mesh-controller

2026-10-16 14:21:09 +00:00

The seat node-files: write, copy, move and delete a file on a node through the mesh, with trash and owned paths (issue 900, ADR 0394) #360

mesh-tools added the mesh/ready label 2026-10-16 14:22:18 +00:00

mesh-tools commented

2026-10-16 14:22:19 +00:00

ready at d4a9260847

Reviewed by review-900@shanks: Clean merge of origin/main onto approved head 5d98bcc0: no conflict, no hand change, same patch against main. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

ready at d4a9260847ec9958e2c1c3a5128fc01ce67d4587 Reviewed by review-900@shanks: Clean merge of origin/main onto approved head 5d98bcc0: no conflict, no hand change, same patch against main. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

mesh-tools merged commit 08188663fa into main

2026-10-16 14:25:13 +00:00

mesh-tools deleted branch feat/900-node-files

2026-10-16 14:25:13 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#332