Register R330: a message a consumer gave up on is kept (hq issue 330)

replays/register.go

@@ -221,6 +221,17 @@ var Register = []Replay{
 		Asserts: "an assignment made while its module's build runs says the build, is kept, and is made when the " +
 			"build registers the module",
 		Package: "./cmd/mesh-controller", Test: "TestReplay325", Files: []string{"cmd/mesh-controller/replay325_test.go"}},
+	// Messages a consumer gave up on were kept nowhere (2026-10-06): a media server's consumer gave up on
+	// several downloads after five deliveries each, the controller's condition cleared within minutes, and
+	// EVENTS dropped them a week later; the dead-letter stream design 25 promised did not exist. A test in
+	// the controller, written with only what the link had before the fix, laid over the commit before. The
+	// fix is still on its branch: Fix is its pull request's head, proved against the main it is cut from.
+	{ID: "R330", Issue: 330, Kind: InRepository, Repository: "mesh-controller", Fix: "75e567a", Before: "a5f53ef",
+		What: "a media server's event consumer gave up on several messages after five deliveries each; the condition " +
+			"cleared within minutes and nothing kept which messages they were",
+		Asserts: "a consumer that never acknowledges an event gives it up, and the event is kept on the bus with " +
+			"its consumer, stream, subject, deliveries and when it was given up",
+		Package: "./internal/link", Test: "TestReplay330", Files: []string{"internal/link/replay330_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.