Issue 300: a new module is not built at its merge #181

2026-10-07T20:40:23Z

mesh-admin commented

2026-10-07 20:40:23 +00:00

Records the case from 2026-10-07. The delivery plan for a catalogue merge said it would build a new module and send it nowhere. The merge built nothing, the module stayed unregistered, and assign refused it until someone built it by hand.

The merge handler dropped touchedBy's added answer. The planner gives that same answer to the check and to the delivery plan.

status: located
fixed-by: mesh-controller PR #122
This is a core issue, so it needs replay: or replay-none: at resolution.

The local runs of records, cycle, index and words, and sh merge-check.sh, all passed.

Records the case from 2026-10-07. The delivery plan for a catalogue merge said it would build a new module and send it nowhere. The merge built nothing, the module stayed unregistered, and `assign` refused it until someone built it by hand. The merge handler dropped `touchedBy`'s `added` answer. The planner gives that same answer to the check and to the delivery plan. - status: located - fixed-by: mesh-controller PR #122 - This is a core issue, so it needs `replay:` or `replay-none:` at resolution. The local runs of records, cycle, index and words, and `sh merge-check.sh`, all passed.

mesh-admin added 2 commits 2026-10-07 20:40:23 +00:00

Issue 300: a new module is not built at its merge 9b573f4ca0

The change plan said a merge adding a module builds it; the merge built
nothing, so the module stayed unregistered until a hand build.

Issue 300: say delivery plan, the glossary's word

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

aaaef91b7b

mesh-admin commented

2026-10-07 20:40:47 +00:00

Delivery novox/hq@aaaef91b7bac — delivered since 2026-10-07T21:02:07Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-07 20:40 (new) → proposed (announced): novox/hq#181's head announced
2026-10-07 20:41 proposed → checked (checked): the verdict names this commit
2026-10-07 20:41 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-07 21:02 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-07 21:02 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/hq@aaaef91b7bac` — **delivered** since 2026-10-07T21:02:07Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-07 20:40 (new) → proposed (announced): novox/hq#181's head announced - 2026-10-07 20:41 proposed → checked (checked): the verdict names this commit - 2026-10-07 20:41 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-07 21:02 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-07 21:02 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-admin merged commit eb54474519 into main

2026-10-07 21:01:42 +00:00

mesh-admin deleted branch issues/300-a-new-module-is-not-built-at-its-merge

2026-10-07 21:01:42 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#181