x4 note: the pause process died mid-run (18:58:30), not after the runs

The log mtimes plus each run's own duration pin it: the first 'invalid internal
status' in the user journal is 18:58:30, while the F bench (launched 18:54:31)
was still loading, and the preceding llama-cli placement probe had just spilled
3.2 GB of '> ' prompts. The note had said 'after the experiment'; that was wrong
and is now recorded with the timestamp it can be checked against.

serverAppConfigs-docs/LLM/x4-pair-experiment.md

@@ -211,11 +211,14 @@ distinguishes a real split from a mislabelled sweep.
   runs, or `-st/--single-turn` with llama-cli. (`-no-cnv` is not a flag in this
   build.)
 - **A dead rootless podman pause process takes the whole host's container
-  management down.** After the experiment the pause process was gone and every
-  `podman` command for the user failed with `invalid internal status … could not
-  find any running process`. The trigger is **not** established: `journalctl -k`
-  holds no OOM kill for that window, so the tempting reading ("the 116 GiB runs
-  squeezed it out") is a guess and is recorded as one.
+  management down.** The first `invalid internal status` in the user journal is
+  **18:58:30**, from containers whose healthchecks shell out to the podman CLI —
+  i.e. the pause process died *while the last bench was still running*, not
+  after the runs finished. Every `podman` command for the user then failed with
+  `invalid internal status … could not find any running process`. The trigger is
+  **not** established: `journalctl -k` holds no OOM kill for that window, so the
+  tempting reading ("the 116 GiB runs squeezed it out") is a guess and is
+  recorded as one.
   `podman system migrate` — the remedy podman itself names — **panics**
   in 5.7.0 (`teardownNetworkBackend` nil deref). The rootless netns that holds
   podman's bridge addresses is gone with it, so `aardvark-dns` cannot bind