mesh-delivery-gate: an answer stands only for the ask it answers, so the approved release merges (issue 1730) #562

2026-10-30T10:45:30Z

mesh-tools commented

2026-10-30 10:45:30 +00:00

The operator approved delivery group feat/774-l3-reland on Telegram at 11:14 CET; it never merged. Six members still carry the Decline of the earlier ask (09:36Z, its check had failed) beside the new Approve, and the gate skips any delivery with a Decline recorded (ready.go:200; merge_again refuses at group_merge.go:338). This was fixed on 2026-10-29 in add6f143 (hq#495) and dropped when the whole L3 merge was reverted (c8240c38). This pull request is that commit again, cherry-picked onto main with an identical diff (checked: git diff add6f143^ add6f143 equals git diff d6a069ae^ d6a069ae). Once the gate runs it, an answer counts only for the ask it answers, and the 10:14Z Approve hands the group at the next look.

Quick vs thorough: quick, to unblock the release now; the thorough part (an Approve not handed within 60 s is an event and an urgent condition; sessions can wait on every ask's asked/decided families) is on branch fix/turn-handed-on-approve, delivered after the release. The kind "a revert of a whole merge drops unrelated fixes" is noted on issue 1730.

Bent rule (rules-are-weighed): no separate reviewer round; the change is byte-identical to add6f143, which was reviewed and merged on 2026-10-29. The lead checked the identity.

Reviewed-by: lead-47@shanks at d6a069ae49

The operator approved delivery group feat/774-l3-reland on Telegram at 11:14 CET; it never merged. Six members still carry the Decline of the earlier ask (09:36Z, its check had failed) beside the new Approve, and the gate skips any delivery with a Decline recorded (ready.go:200; merge_again refuses at group_merge.go:338). This was fixed on 2026-10-29 in add6f143 (hq#495) and dropped when the whole L3 merge was reverted (c8240c38). This pull request is that commit again, cherry-picked onto main with an identical diff (checked: git diff add6f143^ add6f143 equals git diff d6a069ae^ d6a069ae). Once the gate runs it, an answer counts only for the ask it answers, and the 10:14Z Approve hands the group at the next look. Quick vs thorough: quick, to unblock the release now; the thorough part (an Approve not handed within 60 s is an event and an urgent condition; sessions can wait on every ask's asked/decided families) is on branch fix/turn-handed-on-approve, delivered after the release. The kind "a revert of a whole merge drops unrelated fixes" is noted on issue 1730. Bent rule (rules-are-weighed): no separate reviewer round; the change is byte-identical to add6f143, which was reviewed and merged on 2026-10-29. The lead checked the identity. Reviewed-by: lead-47@shanks at d6a069ae49591e915f6a29340552edf99f70b66a

mesh-tools added 1 commit 2026-10-30 10:45:30 +00:00

mesh-delivery-gate: an answer stands only for the ask it answers, and a merge never handed says why

mesh/check being carried to d6a069ae4959 on 1aa22efb0d78 | from 12c2574c9d54

mesh/delivery merged: source.main moved to novox/mesh-catalog@1aa22efb0d78

Details

d6a069ae49

On 2026-10-29 the group feat/774-vault-mints-l2 was approved and never handed: hq#495 kept a Decline of an earlier ask beside the Approve of the next, readyAsks skipped it and handTurn returned nil for every member, with no log line. The Approve and a new ask now clear an earlier Decline, a run's answer names its ask (answered_ask), an approved merge that waits for nothing and is not handed logs why once and is a stalled line, and delivery_turns lists no unwritten turn while the check gates no merge.

mesh-tools commented

2026-10-30 10:45:36 +00:00

Delivery novox/mesh-catalog@d6a069ae4959 — merged since 2026-10-30T11:01:17Z

Source — source.main moved to novox/mesh-catalog@1aa22efb0d. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-10-30 10:45 (new) → proposed (announced): novox/mesh-catalog#562's head announced
2026-10-30 10:45 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-10-30 11:01 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@d6a069ae4959` — **merged** since 2026-10-30T11:01:17Z **Source** — source.main moved to novox/mesh-catalog@1aa22efb0d78. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-30 10:45 (new) → proposed (announced): novox/mesh-catalog#562's head announced - 2026-10-30 10:45 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-10-30 11:01 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 1aa22efb0d into main

2026-10-30 11:01:15 +00:00

mesh-tools deleted branch fix/gate-answer-stands-for-its-ask

2026-10-30 11:01:15 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#562