mesh-issues: an issue knows whether its fix is delivered, says it ready to verify, and a fix stuck after its merge is said (hq ADR 0281) #185

Merged

mesh-admin merged 1 commits from feat/mesh-issues-delivery into main 2026-10-10 16:19:55 +00:00

Conversation 2 Commits 1 Files Changed 10

+792 -167

mesh-admin commented 2026-10-10 16:13:02 +00:00

Contributor

Copy Link

Copy Source

Builds hq ADR 0281 (hq #286), to-be 53 §11. One commit on main after #184.

• Per pull request in fixed-by, Fixes keeps the delivery's last state, why, merged and when — from mesh-delivery.transition (every state; out-of-order and older events skipped; delivered stays delivered) and seat:mesh-delivery.checks once at the tracker's own moved for an unheard PR (≤3 per handling; failure redelivers; empty answer asked again; uses the delivery's own since). Never set by a verb.
• get/list carry delivery, a derived line (failed/stopped, held + why, merged not delivered, not merged, nothing heard, delivered / covered).
• Delivered ≠ resolved: every fix of an unresolved issue delivered → note (first, deduplicated) → claim VerifyFor → event ready-to-verify, once.
• Stuck: Sweep every 5 min; a merged fix not delivered after stuck-after (2h) → one note + operator-channel.notify warning (key issue-tracker.fix-stuck.N); StuckOpen cleared on delivery / unnamed / wontfix, retried on failure. Not a controller condition (bundle-only module; ADR 0240 rule 8), stated in ADR and README.
• move to the same status is taken when a field's value changes (name fixed-by while located); refused when nothing changes.
• Manifest: emits ready-to-verify; invokes seat:operator-channel.notify; setting stuck-after.

Reviewed twice by an independent reviewer (approved at 638076f; this head adds only the since nit). Tests: delivery_test.go (line per state, ready-to-verify once and not for resolved, covered, stuck once/cleared/retried/bound setting, out-of-order, unnamed fix, empty checks, same-status move).

Builds hq ADR 0281 (hq #286), to-be 53 §11. One commit on main after #184. - Per pull request in fixed-by, `Fixes` keeps the delivery's last state, why, merged and when — from `mesh-delivery.transition` (every state; out-of-order and older events skipped; delivered stays delivered) and `seat:mesh-delivery.checks` once at the tracker's own `moved` for an unheard PR (≤3 per handling; failure redelivers; empty answer asked again; uses the delivery's own `since`). Never set by a verb. - `get`/`list` carry `delivery`, a derived line (failed/stopped, held + why, merged not delivered, not merged, nothing heard, delivered / covered). - Delivered ≠ resolved: every fix of an unresolved issue delivered → note (first, deduplicated) → claim `VerifyFor` → event `ready-to-verify`, once. - Stuck: Sweep every 5 min; a merged fix not delivered after `stuck-after` (2h) → one note + `operator-channel.notify` warning (key issue-tracker.fix-stuck.N); `StuckOpen` cleared on delivery / unnamed / wontfix, retried on failure. Not a controller condition (bundle-only module; ADR 0240 rule 8), stated in ADR and README. - `move` to the same status is taken when a field's value changes (name fixed-by while located); refused when nothing changes. - Manifest: emits ready-to-verify; invokes seat:operator-channel.notify; setting stuck-after. Reviewed twice by an independent reviewer (approved at 638076f; this head adds only the `since` nit). Tests: delivery_test.go (line per state, ready-to-verify once and not for resolved, covered, stuck once/cleared/retried/bound setting, out-of-order, unnamed fix, empty checks, same-status move).

mesh-admin added 1 commit 2026-10-10 16:13:03 +00:00

mesh-issues: an issue knows whether its fix is delivered, says it ready to verify, and a fix stuck after its merge is said (hq ADR 0281) ... 01bde68f96

The operator approved measuring from the delivery's own events whether each fix an
issue names reached the machines; delivered is not resolved, and a merged fix that
does not arrive is said on the issue and the operator's channel instead of found.

mesh-admin commented 2026-10-10 16:13:41 +00:00

Author

Contributor

Copy Link

Copy Source

Delivery novox/mesh-catalog@01bde68f9673 — delivered since 2026-10-10T16:24:49Z

Delivery plan — builds mesh-issues → novox; no bus step

• tier 0: mesh-issues
• novox: receives mesh-issues

Machines

• mesh-issues on novox: passed — healthy 3 times over 2m26s
• mesh-issues on the rest running it: sent

Transitions

• 2026-10-10 16:13 (new) → proposed (announced): novox/mesh-catalog#185's head announced
• 2026-10-10 16:15 proposed → checked (checked): the verdict names this commit
• 2026-10-10 16:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-10 16:21 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-10 16:21 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-10 16:24 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-catalog@01bde68f9673` — **delivered** since 2026-10-10T16:24:49Z **Delivery plan** — builds mesh-issues → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues **Machines** - mesh-issues on novox: passed — healthy 3 times over 2m26s - mesh-issues on the rest running it: sent **Transitions** - 2026-10-10 16:13 (new) → proposed (announced): novox/mesh-catalog#185's head announced - 2026-10-10 16:15 proposed → checked (checked): the verdict names this commit - 2026-10-10 16:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 16:21 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 16:21 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-10 16:24 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-admin commented 2026-10-10 16:15:42 +00:00

Author

Contributor

Copy Link

Copy Source

Merge check at 01bde68f

• mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-issues)
• mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds mesh-issues → novox; no bus step

• tier 0: mesh-issues
• novox: receives mesh-issues
• read by no module's build: modules/mesh-issues/README.md, modules/mesh-issues/cmd/mesh-issues/delivery_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go, modules/mesh-issues/cmd/mesh-issues/triage_test.go

Run by the build seat on shanks as build-1791648812051793601 (builds --log build-1791648812051793601).

--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, keeps state issues, counters, grooming
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T16:09:15Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-10T16:09:15Z

modules the change moves:
  - mesh-issues (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues

notes:
  - modules/mesh-issues/README.md, modules/mesh-issues/cmd/mesh-issues/delivery_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go and modules/mesh-issues/cmd/mesh-issues/triage_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.003s
words: 12 retired words and 70 daemons' lines, none in the 38989 strings of 649 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.012s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/mesh-issues
ok  	mesh-issues/cmd/mesh-issues	6.228s
--- its merge-check-typescript.sh (typescript toolchain)

**Merge check** at `01bde68f` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-issues) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds mesh-issues → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues - read by no module's build: modules/mesh-issues/README.md, modules/mesh-issues/cmd/mesh-issues/delivery_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go, modules/mesh-issues/cmd/mesh-issues/triage_test.go Run by the build seat on shanks as `build-1791648812051793601` (`builds --log build-1791648812051793601`). ``` --- the gate: mesh-issues mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, keeps state issues, counters, grooming long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T16:09:15Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-10T16:09:15Z modules the change moves: - mesh-issues (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues notes: - modules/mesh-issues/README.md, modules/mesh-issues/cmd/mesh-issues/delivery_test.go, modules/mesh-issues/cmd/mesh-issues/manifest_test.go and modules/mesh-issues/cmd/mesh-issues/triage_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.003s words: 12 retired words and 70 daemons' lines, none in the 38989 strings of 649 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 69, as kept testing modules/mesh-issues ok mesh-issues/cmd/mesh-issues 6.228s --- its merge-check-typescript.sh (typescript toolchain) ```

mesh-admin merged commit 7e7dfbfb1a into main 2026-10-10 16:19:55 +00:00

mesh-admin deleted branch feat/mesh-issues-delivery 2026-10-10 16:19:55 +00:00

mesh-tools referenced this pull request 2026-11-09 08:24:41 +00:00

Gate record of mesh-catalog's forge-made merges (issue 1966, recovery) #639

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#185