rig updates

rig/ctrl/check.sh

@@ -46,13 +46,10 @@ mb_of() {
                     END      { if (!found) printf "0" }' "${MEMINFO:-/proc/meminfo}"
 }
 
-# What one node costs, measured rather than guessed. On 2026-09-11 a minimal
-# control-plane node ran at 620 MiB idle and ~728 MiB with a small mock, plus
-# 16 MiB for the local registry — ~745 MiB of working set. 800 rounds that up,
-# and agrees with the 800 MB observed independently on a larger rig. Worker
-# nodes carry no etcd or apiserver and are lighter, so for a multi-node shape
-# this errs high. It is the cluster alone: whatever you deploy comes on top.
-NODE_MB=800
+# NODE_MB — what one node costs — comes from load_config (lib/config.sh), where
+# its measurement is recorded. It lives there, not here, because the memory tool
+# and every standalone kit need the same number: a copy of it is how rigmini.sh
+# came to say 2 GB per node long after rig had measured 800 MB.
 
 # Every running container's working set in MB, tagged with the kind cluster it
 # belongs to ('-' when it is not kind). docker stats reports usage minus page