disk-load measures the items the node-engine keeps for its node, and composes nothing (ADR 0577)

It watches its node's keys of mesh-host_data instead of composing every module's items from
about 370 resolved keys per round, so a round no longer takes 30 to 45 minutes across the tunnel
and a manifest its mesh-sdk cannot judge no longer silences it. A changed key measures its module
at once; each round writes how far it got to the per-node state rounds, said by disk_round.
Pins mesh-sdk feat/data-items.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

modules/disk-load/module.json

@@ -9,6 +9,7 @@
     "disk_devices",
     "cpu_top",
     "disk_readings",
+    "disk_round",
     "disk_measure"
   ],
   "build": {
@@ -27,14 +28,13 @@
     ]
   },
   "state": [
-    "readings"
+    "readings",
+    {
+      "name": "rounds",
+      "per-machine": true
+    }
   ],
   "reads": [
-    "mesh-config.resolved",
-    "mesh-delivery-assigner.placement",
-    "mesh-delivery-builder.builds",
-    "mesh-delivery-indexer.manifests",
-    "mesh-delivery-indexer.modules",
-    "node-engine.have"
+    "mesh-host.data"
   ]
 }