Register R314: an answer larger than one message of the bus is paged, not lost (hq issue 314)

Proved by the prover: fails on the controller's main before the fix (the caller
times out), passes on mesh-controller 175b28e.

replays/register.go

@@ -178,6 +178,15 @@ var Register = []Replay{
 		Asserts: "where the base branch holds a merge-check.sh, its script judges the change's tree, and a head " +
 			"without one is never answered the warning",
 		Package: "./internal/builder", Test: "TestReplay310", Files: []string{"internal/builder/replay310_test.go"}},
+	// An answer larger than one message of the bus (2026-10-08): the controller's conditions and status
+	// outgrew the bus's max_payload once 689 stalled deliveries were open conditions, the client library
+	// refused every reply inside the controller, and every caller timed out while calls said answered.
+	{ID: "R314", Issue: 314, Kind: InRepository, Repository: "mesh-controller", Fix: "175b28e",
+		What: "conditions and status answered three times what one message of the bus carries; the reply was " +
+			"refused inside the controller and every caller waited 30 s and read that it did not answer",
+		Asserts: "an answer larger than one message arrives whole to a caller that pages, and one that does not " +
+			"is told so in a message that fits — never a timeout",
+		Package: "./internal/link", Test: "TestReplay314", Files: []string{"internal/link/replay314_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.