The assigner reads a change's manifests as the indexer does, so a value falling back to a predefined key no longer fails every composition touching it #36

Merged
mesh-tools merged 1 commits from fix/assigner-predefined-fallback into main 2026-10-24 14:09:58 +00:00
Member

The assigner (cmd/mesh-delivery-assigner/world.go:151) read each manifest of a change with the strict catalogue.ParseManifest without the catalogue's predefined.json, which it never holds; so any manifest with a value falling back to a predefined key (ADR 0348 §7) was 'unreadable' and the composition failed. pacman, xterm, dunst and claude-code carry such values: the R4g finish group (feat/r4g-finish) failed its composition on pacman at 14:52 (blocking fault of the running assigner, fixed under the milestone's issue 1297's area). It now reads with ParseManifestForInputs, as the indexer does (issue 1751); the catalogue's own checks and the controller still judge against the list. Test TestAManifestFallingBackToAPredefinedKeyIsReadable (xterm's real manifest) failed on main with the verdict's words. Try try-1792847000823792128 passed.

Reviewed-by: review-r4g-r3@shanks at 18b522184f
Pushed-by: lead-47@shanks

The assigner (cmd/mesh-delivery-assigner/world.go:151) read each manifest of a change with the strict catalogue.ParseManifest without the catalogue's predefined.json, which it never holds; so any manifest with a value falling back to a predefined key (ADR 0348 §7) was 'unreadable' and the composition failed. pacman, xterm, dunst and claude-code carry such values: the R4g finish group (feat/r4g-finish) failed its composition on pacman at 14:52 (blocking fault of the running assigner, fixed under the milestone's issue 1297's area). It now reads with ParseManifestForInputs, as the indexer does (issue 1751); the catalogue's own checks and the controller still judge against the list. Test TestAManifestFallingBackToAPredefinedKeyIsReadable (xterm's real manifest) failed on main with the verdict's words. Try try-1792847000823792128 passed. Reviewed-by: review-r4g-r3@shanks at 18b522184f734a9ce9111c6ec22a4f9daeaceb72 Pushed-by: lead-47@shanks
mesh-tools added 1 commit 2026-10-24 13:15:33 +00:00
Author
Member

Delivery novox/mesh-delivery@18b522184f73 — delivered since 2026-10-24T14:11:09Z

Delivery plan — builds mesh-delivery-assigner → ace; no bus step

  • tier 0: mesh-delivery-assigner
  • ace: receives mesh-delivery-assigner
  • 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 mesh-delivery-assigner is judged on its first machine

Machines

  • mesh-delivery-assigner on every machine running it: sent

Transitions

  • 2026-10-24 13:15 (new) → proposed (announced): novox/mesh-delivery#36's head announced
  • 2026-10-24 13:15 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-24 13:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-24 14:10 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-24 14:10 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-24 14:11 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-delivery@18b522184f73` — **delivered** since 2026-10-24T14:11:09Z **Delivery plan** — builds mesh-delivery-assigner → ace; no bus step - tier 0: mesh-delivery-assigner - ace: receives mesh-delivery-assigner - 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 mesh-delivery-assigner is judged on its first machine **Machines** - mesh-delivery-assigner on every machine running it: sent **Transitions** - 2026-10-24 13:15 (new) → proposed (announced): novox/mesh-delivery#36's head announced - 2026-10-24 13:15 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-24 13:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-24 14:10 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-24 14:10 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-24 14:11 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-tools merged commit fa46e7df7d into main 2026-10-24 14:09:58 +00:00
mesh-tools deleted branch fix/assigner-predefined-fallback 2026-10-24 14:09:58 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-delivery#36