Register R368: a moved path is no shrink, and a shrink at the new path still is (hq issue 368)

replays/register.go

@@ -289,6 +289,18 @@ var Register = []Replay{
 		Module: "modules/mesh-delivery", Package: "./cmd/mesh-delivery", Test: "TestReplay362",
 		Files: []string{"modules/mesh-delivery/cmd/mesh-delivery/replay362_test.go",
 			"modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go"}},
+	// A path change read as data loss (2026-10-10): the agent's home on the control-node moved from the
+	// operator's own home to the agent account's (ADR 0266), and data-shrank was raised because the fresh
+	// directory was read against the old one's size. A test in the controller, written with only what it had
+	// before the fix, the incident replayed through the store into D13's findings. Fix is the merge of its
+	// pull request (mesh-controller #204), proved against its first parent.
+	{ID: "R368", Issue: 368, Kind: InRepository, Repository: "mesh-controller", Fix: "798738c",
+		What: "agent-home of claude-code on the control-node was raised as shrunk to 490 B from 94.7 MB when its " +
+			"path moved to the agent account's fresh home; nothing was lost",
+		Asserts: "an item whose path moved raises no data-shrank, and a genuine shrink at its new path is still " +
+			"raised, urgent for what is irreplaceable",
+		Package: "./cmd/mesh-controller", Test: "TestAMovedPathIsNoShrinkAndAShrinkThereStillIs",
+		Files: []string{"cmd/mesh-controller/data_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.