Name no node in mesh-mail-notifier's and memory-pressure's fixtures (issue 1838)

modules/memory-pressure/README.md

@@ -99,8 +99,8 @@ On the laptop:
 
 1. `systemctl --user disable --now mem-guard.service`, then delete
    `~/.config/systemd/user/mem-guard.service` and `~/scripts/mem-guard.sh`.
-2. `/etc/systemd/oomd.conf.d/g14-oomd.conf`: the same values as the module's drop-in.
-3. `/etc/sysctl.d/90-g14-zram.conf`: the same key as the module's file.
+2. `/etc/systemd/oomd.conf.d/node-b-oomd.conf`: the same values as the module's drop-in.
+3. `/etc/sysctl.d/90-node-b-zram.conf`: the same key as the module's file.
 
 The desktop had none of these.
 

modules/mesh-mail-notifier/cmd/mesh-mail-notifier/send_test.go

@@ -4,14 +4,14 @@ import "testing"
 
 // TestSendKeyNamesThisMachine proves Send asks its own machine's node-notifier, not the bare seat: a bare
 // "seat:node-notifier.send" is answered by whichever machine's node-notifier takes it first, so notices sent
-// from g14 and shanks were lost to "503 no responders" or another machine's desktop (novox/hq issue 865).
+// from node-b and node-d were lost to "503 no responders" or another machine's desktop (novox/hq issue 865).
 // desk-channel names the machine it asks the same way ("seat:node-notifier.send@"+machine,
 // modules/desk-channel/cmd/desk-channel/main.go); sendKey must read this machine's own name the same way the
 // SDK's own Emit does, from MESH_NODE, which the runtime sets.
 func TestSendKeyNamesThisMachine(t *testing.T) {
-	t.Setenv("MESH_NODE", "g14")
+	t.Setenv("MESH_NODE", "node-b")
 
-	if got, want := sendKey(), "seat:node-notifier.send@g14"; got != want {
+	if got, want := sendKey(), "seat:node-notifier.send@node-b"; got != want {
 		t.Fatalf("sendKey() = %q, want %q (it must name this machine, as desk-channel does)", got, want)
 	}
 }