Register R318: a wait for a person's new login passes the gate and stalls no walk (hq issue 318)

replays/register.go

@@ -197,6 +197,17 @@ var Register = []Replay{
 		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"}},
+	// One module's wait for a new login held every other module's walk (2026-10-08): the walk of the builds
+	// waiting for a gate sent the laptop three moves in one send, the lighting module's account said relogin
+	// needed and its daemon's unit failed in that account's manager, and the gate failed the send at its bound,
+	// put the module back (taking its account group back) and stopped every walk behind it. A test in the
+	// controller, reading the statements as the node-engine's JSON, so it is laid over the commit before.
+	{ID: "R318", Issue: 318, Kind: InRepository, Repository: "mesh-controller", Fix: "9b86fa9",
+		What: "a send of three modules to the laptop failed its gate after ten minutes because one module's account " +
+			"needed a new login; the module was put back and the walks of the other modules stopped behind it",
+		Asserts: "a wait for a person's new login passes the gate with the wait carried and said as the module's " +
+			"relogin-needed condition; nothing is put back, and the walk goes on to the next machine",
+		Package: "./cmd/mesh-controller", Test: "TestReplay318", Files: []string{"cmd/mesh-controller/replay318_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.