Register R331, so a tool check refused as no link fails before a core merge

hq issue 331: every declared tool check read no link to the bus is open while the
node-engine's link was up. Proved: fails on 824911d^1, passes on 824911d.

replays/register.go

@@ -221,6 +221,16 @@ 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"}},
+	// A declared tool check never asked on a live machine (2026-10-08): the queue reached the bus through an
+	// assertion only OverNATS met, and the NATS link the node-engine attaches had no Ask, so every tool check
+	// read "no link to the bus is open" while the link was up. A test in the node-engine, written with only
+	// what it had before the fix; Home is its commit that added it.
+	{ID: "R331", Issue: 331, Kind: InRepository, Repository: "mesh-host", Fix: "824911d",
+		What: "the sensors module's tool check on the laptop read no link to the bus is open for hours while the " +
+			"node-engine's link was up and the same tool answered through the mesh MCP server",
+		Asserts: "a tool check on the NATS link the node-engine attaches reaches that link, and is not refused as no link",
+		Package: "./internal/link", Test: "TestReplay331", Files: []string{"internal/link/replay331_test.go"},
+		Home: "mesh-host", HomeRef: "5684a4579d92"},
 	// 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.