docs: the pause-process trigger is unproven — say so, everywhere

I had written 'memory pressure from the 116 GiB iGPU runs' as the cause of the
pause-process death. journalctl -k records no OOM kill for that window and the
kernel says nothing else about it, so the claim was a guess wearing a finding's
clothes — in AGENTS.md, the x4 note, and the log. All three now state the
trigger is not established, and the note's 'co-tenants' patience' bullet no
longer asserts that causality either. AGENTS.md also gains the real lesson:
journalctl -k is the check, and an unknown cause does not need a story.

serverAppConfigs-docs/log.md

@@ -687,8 +687,9 @@ timestamp: 2026-09-14
   their experts with them (1.62 GiB per layer), the 12 attention layers are spread
   every 4th across the depth, and the 32.8 GiB PLE must stay on the main device —
   so KV cannot be consolidated on the 3090.
-- **Incident, same evening:** the rootless podman pause process died (memory
-  pressure from the 116 GiB iGPU runs is the plausible cause). Every `podman`
+- **Incident, same evening:** the rootless podman pause process died — trigger
+  NOT established (no OOM kill in `journalctl -k` for that window, so "the
+  116 GiB runs squeezed it out" is a guess, not a finding). Every `podman`
   command then failed (`invalid internal status … could not find any running
   process`), every container start failed on aardvark-dns binding `10.89.x.1:53`
   (the rootless netns holding the bridges was gone), and all 28 quadlets looped.