Register R362: two merges seconds apart are delivered by one walk without a person
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript), replays/merge-check.sh (go)
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/delivery superseded: a newer head of the same pull request

Proved with cmd/prove: fails on 52f34d3, passes on f8c4bc5 (mesh-catalog #171).
This commit is contained in:
jochen
2026-10-10 12:55:51 +02:00
parent d9173d49b8
commit bdb6efa8c6
+14
View File
@@ -275,6 +275,20 @@ var Register = []Replay{
"the operator naming what waits and the call that ends it, and it clears once the machine is sent the " +
"new bus",
Package: "./cmd/mesh-controller", Test: "TestReplay336", Files: []string{"cmd/mesh-controller/replay336_test.go"}},
// Two merges seconds apart left their delivery waiting for a person (2026-10-10): two catalogue merges 18 s
// apart were walked by one walk at the later commit, which superseded the first; mesh-delivery tied it to the
// delivery the supersession had ended, so nothing gave it its word for 58 minutes. A test in mesh-delivery,
// written with only what it had before the fix, as the controller of that night said its walks. The fix is
// still on its branch (mesh-catalog #171): proved against the main it branched from.
{ID: "R362", Issue: 362, Kind: InRepository, Repository: "mesh-catalog", Fix: "f8c4bc5",
Before: "52f34d3",
What: "claude-code and dunst merged 18 s apart; the one walk at the dunst commit was tied to the dunst " +
"delivery its supersession had ended, never let go, and claude-code was held for a person after ten minutes",
Asserts: "the walk at the later commit is let go once and delivers both merges without a person — dunst " +
"delivered, claude-code covered by it — whichever of the controller's two records arrives first",
Module: "modules/mesh-delivery", Package: "./cmd/mesh-delivery", Test: "TestReplay362",
Files: []string{"modules/mesh-delivery/cmd/mesh-delivery/replay362_test.go",
"modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go"}},
// Not a core incident, and the first of its kind: a module's. The crash loop was found by a person
// reading the agent server's log for another reason (issue 268); research 032 measured it, and ADR
// 0240 makes the node-engine judge it and the gate fail it.