Register R335, so a passed gate failed by later reports fails before a core merge

hq issue 335: a build that passed its gate was failed and put back when the
first machine's later reports went quiet. Proved: fails on 8170fc5^1,
passes on 8170fc5.

replays/register.go

@@ -252,6 +252,17 @@ var Register = []Replay{
 			"process that dialled it, and hundreds of such connections an hour hid any client reconnecting",
 		Asserts: "a verb that only reads, served by the serving controller, opens no connection of its own",
 		Package: "./cmd/mesh-controller", Test: "TestReplay327", Files: []string{"cmd/mesh-controller/replay327_test.go"}},
+	// A passed build put back half an hour after its pass (2026-10-08): dunst passed its gate on the laptop,
+	// its send to the rest waited on another walk, that walk sent the laptop a declaration it did not report
+	// on, and the plan read the silence as the passed build never applied: failed at its gate with the pass's
+	// own words, and put back. A test in the controller, written with only what it had before the fix, laid
+	// over the commit before. Fix is the merge of the fix.
+	{ID: "R335", Issue: 335, Kind: InRepository, Repository: "mesh-controller", Fix: "8170fc5",
+		What: "a build that passed its gate on the laptop (healthy 3 times over 2m5s) was marked failed at its " +
+			"gate 28 minutes later, with those words as the reason, and put back",
+		Asserts: "once a build passed its gate, the first machine's later reports neither fail it nor hold the rest, " +
+			"and a walk stopped after the pass keeps it",
+		Package: "./cmd/mesh-controller", Test: "TestReplay335", Files: []string{"cmd/mesh-controller/replay335_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.