Pin R92 to today's genesis: main with every genesis fix, and the same without #91 (hq issue 92)

At the fix's merge no genesis got past step 6 (issue 146), so neither side of the replay reached the
push it replays. Fix is mesh-host main 0d11b4fc; Before is that main with #91 reverted, on the
unmerged branch replay/r92-before; the controller and catalogue at their mains on both sides.

replays/register.go

@@ -368,9 +368,14 @@ var Register = []Replay{
 	// lab never saw it: its base image trusts the documentation ranges before any bed starts. A bed here,
 	// whose anchor has that trust taken off before the installer runs, raised with the node-engine and its
 	// installer built at the commit; the control plane genesis builds and the catalogue it reads are pinned,
-	// the same on both sides. Fix is the merge of its pull request (mesh-host #91), proved against its first
-	// parent.
-	{ID: "R92", Issue: 92, Kind: Bed, Repository: "mesh-host", Fix: "dd9ab7927d967e236ef755bbe5fd6238d68f10df",
+	// the same on both sides.
+	//
+	// **Pinned to today's genesis, not to the fix's merge** (hq issues 146, 590, 596, 597): at the merge of
+	// the fix (mesh-host #91, dd9ab792) no genesis got past step 6, so neither side reached the push. Fix is
+	// mesh-host main with every genesis fix since; Before is the same main with #91 reverted, kept on the
+	// branch replay/r92-before and never merged.
+	{ID: "R92", Issue: 92, Kind: Bed, Repository: "mesh-host", Fix: "0d11b4fc930d6723f3dc54dc173175f66fb6b3b3",
+		Before: "9e233e1d87569273b4ed353c450b0bd27d21039b",
 		What: "the first real genesis pushed the control plane's image to the registry it had just raised and was " +
 			"refused, server gave HTTP response to HTTPS client: the runtime's trust of the registry was written " +
 			"by the docker module, six steps after the push",
@@ -379,10 +384,8 @@ var Register = []Replay{
 			"mesh's name too",
 		Test: "test/integration/replay92.test.ts",
 		With: []Also{
-			{Repository: "mesh-controller", Fix: "3cfc12167088e098eca7c58d3ff40d3029e1c3d1",
-				Before: "3cfc12167088e098eca7c58d3ff40d3029e1c3d1"},
-			{Repository: "mesh-catalog", Fix: "c5e1bc7bb4228a23957e2524e0ebf387b37a4871",
-				Before: "c5e1bc7bb4228a23957e2524e0ebf387b37a4871"},
+			{Repository: "mesh-controller", Fix: "49102e1645c920e42e453caf0aa0746d2b93ce90", Before: "49102e1645c920e42e453caf0aa0746d2b93ce90"},
+			{Repository: "mesh-catalog", Fix: "f88e3452f8b8b285ed86e1fe93e1a153f71faada", Before: "f88e3452f8b8b285ed86e1fe93e1a153f71faada"},
 		}},
 	// 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