Issue 876: the merge gate refused every moved module as "marked moved and names no template" (mesh-catalog #328, 29 problems), because it inlined the templates before its stand-in build, so Resolve never made the module's handed record and the strict re-read refused it.
Fix: the gate keeps the manifest as written, reads its templates from the tree, and its stand-in build carries their texts in the templates archive, as a real build does; Resolve then hands the module. The gate's earlier judging of the inlined manifest is unchanged.
Tests (unit, no database): TestReplay876 calls the gate (shelfWithChange) on a moved module and fails with the old call; a moved module naming no template is still refused. Packages run in 0.03 s.
Local head 0f3f3d18 (tree f97886c5). Review (Opus): round 1 APPROVE at c3afdf1a, round 2 on 0f3f3d18. Not a member of the 57-config-and-provisioning group (own branch name). Follow-up outside feature 57: issue 892 (module add).
Issue 876: the merge gate refused every moved module as "marked moved and names no template" (mesh-catalog #328, 29 problems), because it inlined the templates before its stand-in build, so Resolve never made the module's handed record and the strict re-read refused it.
Fix: the gate keeps the manifest as written, reads its templates from the tree, and its stand-in build carries their texts in the templates archive, as a real build does; Resolve then hands the module. The gate's earlier judging of the inlined manifest is unchanged.
Tests (unit, no database): TestReplay876 calls the gate (shelfWithChange) on a moved module and fails with the old call; a moved module naming no template is still refused. Packages run in 0.03 s.
Local head 0f3f3d18 (tree f97886c5). Review (Opus): round 1 APPROVE at c3afdf1a, round 2 on 0f3f3d18. Not a member of the 57-config-and-provisioning group (own branch name). Follow-up outside feature 57: issue 892 (module add).
mesh/merge-gate head efc5f901afb7 merged into trunk cf897e89fe31 — pass: [release feat/57-config-and-provisioning, judged by its controller 93b947cc53b5] t…
mesh/repo-check head efc5f901afb7 merged into trunk cf897e89fe31 — pass: [release feat/57-config-and-provisioning, judged by its controller 93b947cc53b5] i…
Deliverynovox/mesh-controller@efc5f901afb7 — delivered since 2026-10-16T08:14:09Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-16 08:08 (new) → proposed (announced): novox/mesh-controller#353's head announced
2026-10-16 08:13 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-16 08:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-16 08:14 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 08:14 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-delivery:view -->
**Delivery** `novox/mesh-controller@efc5f901afb7` — **delivered** since 2026-10-16T08:14:09Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-16 08:08 (new) → proposed (announced): novox/mesh-controller#353's head announced
- 2026-10-16 08:13 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-16 08:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-16 08:14 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 08:14 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`.
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 876: the merge gate refused every moved module as "marked moved and names no template" (mesh-catalog #328, 29 problems), because it inlined the templates before its stand-in build, so Resolve never made the module's handed record and the strict re-read refused it.
Fix: the gate keeps the manifest as written, reads its templates from the tree, and its stand-in build carries their texts in the templates archive, as a real build does; Resolve then hands the module. The gate's earlier judging of the inlined manifest is unchanged.
Tests (unit, no database): TestReplay876 calls the gate (shelfWithChange) on a moved module and fails with the old call; a moved module naming no template is still refused. Packages run in 0.03 s.
Local head 0f3f3d18 (tree
f97886c5). Review (Opus): round 1 APPROVE at c3afdf1a, round 2 on 0f3f3d18. Not a member of the 57-config-and-provisioning group (own branch name). Follow-up outside feature 57: issue 892 (module add).Delivery
novox/mesh-controller@efc5f901afb7— delivered since 2026-10-16T08:14:09ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.ready at
efc5f901afReview (Opus): round 1 APPROVE (c3afdf1a), round 2 APPROVE (0f3f3d18, tree
f97886c5= this head's tree).