Issue 1204: the builder records each build's source fingerprint, but no tool read it back. builds now prints a line source src1:… after the reuse key for every build that recorded one; every other line is unchanged (the rows moved into printBuild, writing to a writer a test reads).
Why now: design 47 milestone R3a (ADR 0437 clause 5) needs three fingerprints the live builder recorded, to prove the SDK's fingerprint function (issue 1203) gives the same ones.
Acceptance criteria 1204/AC1, AC2: TestBuildsSaysTheSourceFingerprint (cmd/mesh-controller/build_test.go). AC3 is proven live after the delivery.
Try: build-1792398670642600446 passed (4m16s).
Delivery: mesh-controller alone, to novox.
Issue 1204: the builder records each build's source fingerprint, but no tool read it back. `builds` now prints a line `source src1:…` after the reuse key for every build that recorded one; every other line is unchanged (the rows moved into printBuild, writing to a writer a test reads).
Why now: design 47 milestone R3a (ADR 0437 clause 5) needs three fingerprints the live builder recorded, to prove the SDK's fingerprint function (issue 1203) gives the same ones.
Acceptance criteria 1204/AC1, AC2: TestBuildsSaysTheSourceFingerprint (cmd/mesh-controller/build_test.go). AC3 is proven live after the delivery.
Try: build-1792398670642600446 passed (4m16s).
Delivery: mesh-controller alone, to novox.
Reviewed-by: reviewer-1204@shanks at 6e487fa01f630aa0ea9a32429bfda18f534bdc1f
mesh/merge-gate head 6e487fa01f63 merged into trunk 7a74cee83f88 — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang…
Deliverynovox/mesh-controller@6e487fa01f63 — delivered since 2026-10-19T08:45:22Z
Delivery plan — builds mesh-controller → novox; no bus step
tier 0: mesh-controller
novox: receives mesh-controller
Machines
mesh-controller on every machine running it: sent
Transitions
2026-10-19 08:35 (new) → proposed (announced): novox/mesh-controller#392's head announced
2026-10-19 08:42 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-19 08:42 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-19 08:43 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 08:43 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 08:45 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@6e487fa01f63` — **delivered** since 2026-10-19T08:45:22Z
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
**Machines**
- mesh-controller on every machine running it: sent
**Transitions**
- 2026-10-19 08:35 (new) → proposed (announced): novox/mesh-controller#392's head announced
- 2026-10-19 08:42 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-19 08:42 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-19 08:43 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 08:43 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 08:45 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`.
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 1204: the builder records each build's source fingerprint, but no tool read it back.
buildsnow prints a linesource src1:…after the reuse key for every build that recorded one; every other line is unchanged (the rows moved into printBuild, writing to a writer a test reads).Why now: design 47 milestone R3a (ADR 0437 clause 5) needs three fingerprints the live builder recorded, to prove the SDK's fingerprint function (issue 1203) gives the same ones.
Acceptance criteria 1204/AC1, AC2: TestBuildsSaysTheSourceFingerprint (cmd/mesh-controller/build_test.go). AC3 is proven live after the delivery.
Try: build-1792398670642600446 passed (4m16s).
Delivery: mesh-controller alone, to novox.
Reviewed-by: reviewer-1204@shanks at
6e487fa01fDelivery
novox/mesh-controller@6e487fa01f63— delivered since 2026-10-19T08:45:22ZDelivery plan — builds mesh-controller → novox; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
6e487fa0Judged: head
6e487fa01f63merged into trunk7a74cee83f88; read beside it: mesh-catalogb4527d9091e9, mesh-controller-main7a74cee83f88, mesh-host2474bf28330f, mesh-tools7412c5b6c9c5mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on shanks as
build-1792398942116698078(builds --log build-1792398942116698078).