Credential. The build seat wrote the forge credential to workspace/git-credentials, inside the workspace a check's toolchain container mounts as HOME. Now storeCredential (internal/builder/builder.go) writes it to a private os.MkdirTemp directory outside the workspace (refused if the temp dir is inside it), git reads it through credential.helper=store --file=<that path>, and a check removes it right after its last clone, before the facts are read and any container runs (deferred removal too). Builds use the same helper and remove it when done, and any workspace/git-credentials an older builder left is deleted, so a later check cannot find a leftover. A clone whose source URL carries userinfo (the checked repository, those beside it, a group's heads) gets git remote set-url origin without it, so no .git/config the container reads holds a credential (the -c credential.helper flags are never persisted).
Redaction.internal/builder/redact.go is a copy of the journal tool's redactor (mesh-catalog modules/systemd/cmd/systemd-tools/secrets.go): passwords in URI userinfo, password flags, NAME=value by a secret-like name, plus prefixed token shapes (gh*_, glpat-, xox*-, sk-ant-, JWTs, NATS seeds) and the forge credential's own password as a known secret. Every line a repository's own check sends to the build's log passes it, everything Check says goes through it with the known secret, and the verdict's report, summaries and Failed are redacted before they reach the forge or the controller. Sharing it through mesh-sdk is issue 471 (needs an SDK release and pin changes in three places, too large for this PR).
Tests (both failed on main for the reason named):
TestACheckContainerSeesNoForgeCredential: at the first container call, the workspace holds no git-credentials, no file with the forge password or a beside clone's userinfo token, and the offered store is outside the workspace and already gone. On main it listed workspace/git-credentials and mesh-catalog/.git/config.
TestACheckLinePublishedToTheLogIsRedacted: a line printing http://user:token@host/... and a ghp_ token is published as http://user:[redacted: a password in a URI]@host/.... On main both secrets were published as printed.
TestTheRedactorHidesTheForgeCredentialAndShapes, and the two build credential tests updated to the new location.
go vet ./... and go test ./internal/builder/ ./cmd/mesh-builder/ -count=1 pass. No files of #223, #225 or the 234 work are touched.
Fixes novox/hq issue 462.
**Credential.** The build seat wrote the forge credential to `workspace/git-credentials`, inside the workspace a check's toolchain container mounts as HOME. Now `storeCredential` (internal/builder/builder.go) writes it to a private `os.MkdirTemp` directory outside the workspace (refused if the temp dir is inside it), git reads it through `credential.helper=store --file=<that path>`, and a check removes it right after its last clone, before the facts are read and any container runs (deferred removal too). Builds use the same helper and remove it when done, and any `workspace/git-credentials` an older builder left is deleted, so a later check cannot find a leftover. A clone whose source URL carries userinfo (the checked repository, those beside it, a group's heads) gets `git remote set-url origin` without it, so no `.git/config` the container reads holds a credential (the `-c credential.helper` flags are never persisted).
**Redaction.** `internal/builder/redact.go` is a copy of the journal tool's redactor (mesh-catalog modules/systemd/cmd/systemd-tools/secrets.go): passwords in URI userinfo, password flags, NAME=value by a secret-like name, plus prefixed token shapes (gh*_, glpat-, xox*-, sk-ant-, JWTs, NATS seeds) and the forge credential's own password as a known secret. Every line a repository's own check sends to the build's log passes it, everything Check says goes through it with the known secret, and the verdict's report, summaries and Failed are redacted before they reach the forge or the controller. Sharing it through mesh-sdk is issue 471 (needs an SDK release and pin changes in three places, too large for this PR).
**Tests** (both failed on main for the reason named):
- `TestACheckContainerSeesNoForgeCredential`: at the first container call, the workspace holds no `git-credentials`, no file with the forge password or a beside clone's userinfo token, and the offered store is outside the workspace and already gone. On main it listed workspace/git-credentials and mesh-catalog/.git/config.
- `TestACheckLinePublishedToTheLogIsRedacted`: a line printing `http://user:token@host/...` and a `ghp_` token is published as `http://user:[redacted: a password in a URI]@host/...`. On main both secrets were published as printed.
- `TestTheRedactorHidesTheForgeCredentialAndShapes`, and the two build credential tests updated to the new location.
`go vet ./...` and `go test ./internal/builder/ ./cmd/mesh-builder/ -count=1` pass. No files of #223, #225 or the 234 work are touched.
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
The toolchain container mounts the workspace as HOME, so the credential kept
there, and a clone's recorded userinfo, were readable by any pull request; its
output is kept on the bus for days. The credential now lives in a private
directory outside the workspace only while cloning, clones record their URL
without userinfo, and every line said to the build's log and the verdict
passes a redactor copied from the journal tool (sharing it: issue 471).
Deliverynovox/mesh-controller@5c4fa43f8bab — delivered since 2026-10-11T10:41:00Z
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
Machines
mesh-controller on novox: passed — healthy 3 times over 3m37s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 3m23s
build-agent on the rest running it: sent
Transitions
2026-10-11 09:25 (new) → proposed (announced): novox/mesh-controller#226's head announced
2026-10-11 09:37 proposed → checked (checked): the verdict names this commit
2026-10-11 09:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 10:31 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 10:31 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 10:41 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-controller@5c4fa43f8bab` — **delivered** since 2026-10-11T10:41:00Z
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m37s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 3m23s
- build-agent on the rest running it: sent
**Transitions**
- 2026-10-11 09:25 (new) → proposed (announced): novox/mesh-controller#226's head announced
- 2026-10-11 09:37 proposed → checked (checked): the verdict names this commit
- 2026-10-11 09:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 10:31 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 10:31 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 10:41 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: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
A build wrote .npmrc into its source tree and never removed it, and its clone
recorded the URL's userinfo; a later check's container mounts the workspace as
HOME. The .npmrc and the tree now go when the build ends, clones record their
URL without userinfo, and a check first removes any .npmrc an older builder left.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on ace as build-1791710450041950342 (builds --log build-1791710450041950342).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
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-11T09:21:02Z 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-11T09:21:02Z
modules the change moves:
- mesh-controller (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 2 module(s) in 2 tier(s): build-agent, mesh-controller
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.036s
ok github.com/novox/mesh-controller/cmd/mesh-controller 203.018s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.012s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.011s
ok github.com/novox/mesh-controller/examples/route-proxy 1.097s
ok github.com/novox/mesh-controller/internal/artifacts 1.099s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.656s
ok github.com/novox/mesh-controller/internal/builder 13.958s
ok github.com/novox/mesh-controller/internal/catalogue 6.594s
ok github.com/novox/mesh-controller/internal/conditions 2.479s
ok github.com/novox/mesh-controller/internal/envfile 1.072s
ok github.com/novox/mesh-controller/internal/facts 1.119s
ok github.com/novox/mesh-controller/internal/identity 4.166s
ok github.com/novox/mesh-controller/internal/inventory 77.886s
ok github.com/novox/mesh-controller/internal/lease 17.751s
ok github.com/novox/mesh-controller/internal/licences 3.879s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.112s
ok github.com/novox/mesh-controller/internal/link 58.691s
ok github.com/novox/mesh-controller/internal/lint 2.147s
ok github.com/novox/mesh-controller/internal/outward 1.143s
ok github.com/novox/mesh-controller/internal/overlay 1.129s
ok github.com/novox/mesh-controller/internal/secrets 1.456s
ok github.com/novox/mesh-controller/internal/store 3.311s
ok github.com/novox/mesh-controller/internal/testbus 1.184s
ok github.com/novox/mesh-controller/internal/token 1.019s
**Merge check** at `c494ed03`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on ace as `build-1791710450041950342` (`builds --log build-1791710450041950342`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
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-11T09:21:02Z 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-11T09:21:02Z
modules the change moves:
- mesh-controller (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 2 module(s) in 2 tier(s): build-agent, mesh-controller
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.036s
ok github.com/novox/mesh-controller/cmd/mesh-controller 203.018s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.012s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.011s
ok github.com/novox/mesh-controller/examples/route-proxy 1.097s
ok github.com/novox/mesh-controller/internal/artifacts 1.099s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.656s
ok github.com/novox/mesh-controller/internal/builder 13.958s
ok github.com/novox/mesh-controller/internal/catalogue 6.594s
ok github.com/novox/mesh-controller/internal/conditions 2.479s
ok github.com/novox/mesh-controller/internal/envfile 1.072s
ok github.com/novox/mesh-controller/internal/facts 1.119s
ok github.com/novox/mesh-controller/internal/identity 4.166s
ok github.com/novox/mesh-controller/internal/inventory 77.886s
ok github.com/novox/mesh-controller/internal/lease 17.751s
ok github.com/novox/mesh-controller/internal/licences 3.879s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.112s
ok github.com/novox/mesh-controller/internal/link 58.691s
ok github.com/novox/mesh-controller/internal/lint 2.147s
ok github.com/novox/mesh-controller/internal/outward 1.143s
ok github.com/novox/mesh-controller/internal/overlay 1.129s
ok github.com/novox/mesh-controller/internal/secrets 1.456s
ok github.com/novox/mesh-controller/internal/store 3.311s
ok github.com/novox/mesh-controller/internal/testbus 1.184s
ok github.com/novox/mesh-controller/internal/token 1.019s
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: internal/builder/builder_test.go, internal/builder/check_credential_test.go, internal/builder/packages_test.go
Run by the build seat on novox as build-1791710725040335454 (builds --log build-1791710725040335454).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
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-11T09:21:02Z 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-11T09:21:02Z
modules the change moves:
- mesh-controller (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 2 module(s) in 2 tier(s): build-agent, mesh-controller
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.049s
ok github.com/novox/mesh-controller/cmd/mesh-controller 280.491s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.019s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.028s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.019s
ok github.com/novox/mesh-controller/examples/route-proxy 1.128s
ok github.com/novox/mesh-controller/internal/artifacts 1.060s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.125s
ok github.com/novox/mesh-controller/internal/builder 19.310s
ok github.com/novox/mesh-controller/internal/catalogue 7.836s
ok github.com/novox/mesh-controller/internal/conditions 2.688s
ok github.com/novox/mesh-controller/internal/envfile 1.031s
ok github.com/novox/mesh-controller/internal/facts 1.026s
ok github.com/novox/mesh-controller/internal/identity 14.492s
ok github.com/novox/mesh-controller/internal/inventory 112.964s
ok github.com/novox/mesh-controller/internal/lease 18.276s
ok github.com/novox/mesh-controller/internal/licences 13.229s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.019s
ok github.com/novox/mesh-controller/internal/link 69.982s
ok github.com/novox/mesh-controller/internal/lint 2.387s
ok github.com/novox/mesh-controller/internal/outward 1.041s
ok github.com/novox/mesh-controller/internal/overlay 1.028s
ok github.com/novox/mesh-controller/internal/secrets 1.439s
ok github.com/novox/mesh-controller/internal/store 10.539s
ok github.com/novox/mesh-controller/internal/testbus 1.190s
ok github.com/novox/mesh-controller/internal/token 1.014s
**Merge check** at `5c4fa43f`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: internal/builder/builder_test.go, internal/builder/check_credential_test.go, internal/builder/packages_test.go
Run by the build seat on novox as `build-1791710725040335454` (`builds --log build-1791710725040335454`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
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-11T09:21:02Z 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-11T09:21:02Z
modules the change moves:
- mesh-controller (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 2 module(s) in 2 tier(s): build-agent, mesh-controller
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.049s
ok github.com/novox/mesh-controller/cmd/mesh-controller 280.491s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.019s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.028s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.019s
ok github.com/novox/mesh-controller/examples/route-proxy 1.128s
ok github.com/novox/mesh-controller/internal/artifacts 1.060s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.125s
ok github.com/novox/mesh-controller/internal/builder 19.310s
ok github.com/novox/mesh-controller/internal/catalogue 7.836s
ok github.com/novox/mesh-controller/internal/conditions 2.688s
ok github.com/novox/mesh-controller/internal/envfile 1.031s
ok github.com/novox/mesh-controller/internal/facts 1.026s
ok github.com/novox/mesh-controller/internal/identity 14.492s
ok github.com/novox/mesh-controller/internal/inventory 112.964s
ok github.com/novox/mesh-controller/internal/lease 18.276s
ok github.com/novox/mesh-controller/internal/licences 13.229s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.019s
ok github.com/novox/mesh-controller/internal/link 69.982s
ok github.com/novox/mesh-controller/internal/lint 2.387s
ok github.com/novox/mesh-controller/internal/outward 1.041s
ok github.com/novox/mesh-controller/internal/overlay 1.028s
ok github.com/novox/mesh-controller/internal/secrets 1.439s
ok github.com/novox/mesh-controller/internal/store 10.539s
ok github.com/novox/mesh-controller/internal/testbus 1.190s
ok github.com/novox/mesh-controller/internal/token 1.014s
```
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.
Fixes novox/hq issue 462.
Credential. The build seat wrote the forge credential to
workspace/git-credentials, inside the workspace a check's toolchain container mounts as HOME. NowstoreCredential(internal/builder/builder.go) writes it to a privateos.MkdirTempdirectory outside the workspace (refused if the temp dir is inside it), git reads it throughcredential.helper=store --file=<that path>, and a check removes it right after its last clone, before the facts are read and any container runs (deferred removal too). Builds use the same helper and remove it when done, and anyworkspace/git-credentialsan older builder left is deleted, so a later check cannot find a leftover. A clone whose source URL carries userinfo (the checked repository, those beside it, a group's heads) getsgit remote set-url originwithout it, so no.git/configthe container reads holds a credential (the-c credential.helperflags are never persisted).Redaction.
internal/builder/redact.gois a copy of the journal tool's redactor (mesh-catalog modules/systemd/cmd/systemd-tools/secrets.go): passwords in URI userinfo, password flags, NAME=value by a secret-like name, plus prefixed token shapes (gh*_, glpat-, xox*-, sk-ant-, JWTs, NATS seeds) and the forge credential's own password as a known secret. Every line a repository's own check sends to the build's log passes it, everything Check says goes through it with the known secret, and the verdict's report, summaries and Failed are redacted before they reach the forge or the controller. Sharing it through mesh-sdk is issue 471 (needs an SDK release and pin changes in three places, too large for this PR).Tests (both failed on main for the reason named):
TestACheckContainerSeesNoForgeCredential: at the first container call, the workspace holds nogit-credentials, no file with the forge password or a beside clone's userinfo token, and the offered store is outside the workspace and already gone. On main it listed workspace/git-credentials and mesh-catalog/.git/config.TestACheckLinePublishedToTheLogIsRedacted: a line printinghttp://user:token@host/...and aghp_token is published ashttp://user:[redacted: a password in a URI]@host/.... On main both secrets were published as printed.TestTheRedactorHidesTheForgeCredentialAndShapes, and the two build credential tests updated to the new location.go vet ./...andgo test ./internal/builder/ ./cmd/mesh-builder/ -count=1pass. No files of #223, #225 or the 234 work are touched.Delivery
novox/mesh-controller@5c4fa43f8bab— delivered since 2026-10-11T10:41:00ZDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
c494ed03mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791710450041950342(builds --log build-1791710450041950342).Merge check at
5c4fa43fmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791710725040335454(builds --log build-1791710725040335454).mesh-admin referenced this pull request2026-10-11 16:14:01 +00:00
mesh-admin referenced this pull request2026-10-11 17:00:59 +00:00