Register R325, so an assignment made while its build runs stays answered

hq issue 325: assign said no module of that name a minute after the merge
that asked for the module's build. Proved: fails on a759ac6, passes on b93dea8.

replays/register.go

@@ -210,6 +210,17 @@ var Register = []Replay{
 		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"}},
+	// An assignment answered as unknown while its module's build ran (2026-10-08): the merge adding `sensors`
+	// asked for its build (issue 300), and `assign g14 sensors` a minute later said "no module of that name",
+	// which read as a module nobody registered. A test in the controller, written with only what it had
+	// before the fix, laid over the commit before. The fix is still on its branch: proved against the main it
+	// branched from.
+	{ID: "R325", Issue: 325, Kind: InRepository, Repository: "mesh-controller", Fix: "b93dea8", Before: "a759ac6",
+		What: "a minute after the merge that added sensors asked for its build, assign g14 sensors answered no " +
+			"module of that name, and the same call worked minutes later",
+		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"}},
 	// 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.