Issue 1208, found by issue 1204's delivery: #392 made builds print a source src1:… line, but no build showed one, because chainBuildList (internal/inventory/chain_builds.go:620) copied each build field by field and left the fingerprint out. It now carries it.
Acceptance criteria 1208/AC1, AC2: TestTheBuildsListCarriesTheSourceFingerprint (internal/inventory/builds_test.go, integration; it records through RecordBuild and reads through inv.Builds, the path the seat verb takes). AC3 (and 1204/AC3) is proven live after the delivery.
Try: build-1792399663052584559 passed (4m13s).
Delivery: mesh-controller alone, to novox.
Issue 1208, found by issue 1204's delivery: #392 made builds print a `source src1:…` line, but no build showed one, because chainBuildList (internal/inventory/chain_builds.go:620) copied each build field by field and left the fingerprint out. It now carries it.
Acceptance criteria 1208/AC1, AC2: TestTheBuildsListCarriesTheSourceFingerprint (internal/inventory/builds_test.go, integration; it records through RecordBuild and reads through inv.Builds, the path the seat verb takes). AC3 (and 1204/AC3) is proven live after the delivery.
Try: build-1792399663052584559 passed (4m13s).
Delivery: mesh-controller alone, to novox.
Reviewed-by: reviewer-1204@shanks at 3ac8657a49bfb90460f4fc9e4ba9405fa485f643
mesh/merge-gate head 3ac8657a49bf merged into trunk 230f0a1a18f2 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every …
Deliverynovox/mesh-controller@3ac8657a49bf — delivered since 2026-10-19T09:07:32Z
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
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 build-agent is judged on its first machine
Machines
mesh-controller on every machine running it: sent
build-agent on every machine running it: sent
Transitions
2026-10-19 08:52 (new) → proposed (announced): novox/mesh-controller#393's head announced
2026-10-19 08:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-19 08:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-19 09:00 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-19 09:00 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-19 09:07 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@3ac8657a49bf` — **delivered** since 2026-10-19T09:07:32Z
**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
- 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 build-agent is judged on its first machine
**Machines**
- mesh-controller on every machine running it: sent
- build-agent on every machine running it: sent
**Transitions**
- 2026-10-19 08:52 (new) → proposed (announced): novox/mesh-controller#393's head announced
- 2026-10-19 08:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-19 08:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-19 09:00 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-19 09:00 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-19 09:07 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`.
Merge check at 3ac8657a
Judged: head 3ac8657a49bf merged into trunk 230f0a1a18f2; read beside it: mesh-catalog b4527d9091e9, mesh-controller-main 230f0a1a18f2, mesh-host 2474bf28330f, mesh-tools 7412c5b6c9c5
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
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 build-agent is judged on its first machine
read by no module's build: internal/inventory/builds_test.go
Run by the build seat on shanks as build-1792399929920392993 (builds --log build-1792399929920392993).
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.
Issue 1208, found by issue 1204's delivery: #392 made builds print a
source src1:…line, but no build showed one, because chainBuildList (internal/inventory/chain_builds.go:620) copied each build field by field and left the fingerprint out. It now carries it.Acceptance criteria 1208/AC1, AC2: TestTheBuildsListCarriesTheSourceFingerprint (internal/inventory/builds_test.go, integration; it records through RecordBuild and reads through inv.Builds, the path the seat verb takes). AC3 (and 1204/AC3) is proven live after the delivery.
Try: build-1792399663052584559 passed (4m13s).
Delivery: mesh-controller alone, to novox.
Reviewed-by: reviewer-1204@shanks at
3ac8657a49Delivery
novox/mesh-controller@3ac8657a49bf— delivered since 2026-10-19T09:07:32ZDelivery 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
3ac8657aJudged: head
3ac8657a49bfmerged into trunk230f0a1a18f2; read beside it: mesh-catalogb4527d9091e9, mesh-controller-main230f0a1a18f2, mesh-host2474bf28330f, mesh-tools7412c5b6c9c5mesh/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 shanks as
build-1792399929920392993(builds --log build-1792399929920392993).