governance + unit-self-describing demand + dashboard fixes

Two governance items from the 2026-05-14 quality review:
- test/_output-manifest.md enumerates every Port 0/1/2 key MGC emits, its
  source, type, range, and which tests cover it in populated/degraded states
  (per .claude/rules/output-coverage.md).
- src/control/strategies.js extracts computeEqualFlowDistribution as a pure
  function so the equal-flow algorithm is testable without an MGC fixture.
  test/basic/equalFlowDistribution.basic.test.js (6 tests) covers all three
  demand branches and pins the legacy quirk where the default branch counts
  active machines but iterates priority-ordered first-N (documented in the
  test so the future cleanup is a deliberate change).

Plus rolled-up session work that landed alongside:
- set.demand is now unit-self-describing ({value, unit:'m3/h'|'l/s'|'%'|...}
  or bare number = %); setScaling/scaling.current removed from MGC, commands,
  editor (mgc.html), specificClass.
- _optimalControl + equalFlowControl now compute eta = (Q*dP)/P_shaft rather
  than Q/P, keeping the metric in the same scale as each child's cog.
- groupEfficiency.calcRelativeDistanceFromPeak returns undefined (was 1) when
  pumps are homogeneous (|max-min| < 1e-9). Dashboard treats undefined as
  '-' instead of showing a misleading 100% / 0% reading.
- examples/02-Dashboard.json: auto-init inject so the dashboard populates at
  deploy, NCog formatter normalizes the SUM emitted by MGC by
  machineCountActive, Q-H fanout trims the flat-Q tail so the H axis isn't
  stretched to 40m by curve-envelope clamp points, num/pct treat null AND
  undefined as no-data (closes the +null === 0 trap).
- new test/integration/dashboard-fanout.integration.test.js (17 tests),
  bep-distance-demand-sweep.integration.test.js (3 tests),
  group-bep-cascade.integration.test.js -- total suite now 108/108 green.
- .gitignore: wiki/test.gif (143 MB screen recording, kept locally only).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

mgc.html

@@ -22,8 +22,7 @@
       dbaseOutputFormat: { value: "influxdb" },
 
       // Control strategy
-      mode:    { value: "optimalControl" }, // optimalControl | priorityControl | prioritypercentagecontrol | maintenance
-      scaling: { value: "normalized" },     // normalized (0–100 %) | absolute (m³/h)
+      mode:    { value: "optimalControl" }, // optimalControl | priorityControl | maintenance
 
       //define asset properties
       uuid: { value: "" },
@@ -94,17 +93,15 @@
     <select id="node-input-mode" style="width:60%;">
       <option value="optimalControl">optimalControl &mdash; pick the best valid pump combination by BEP-gravitation / NCog</option>
       <option value="priorityControl">priorityControl &mdash; sequential equal-flow control by priority list</option>
-      <option value="prioritypercentagecontrol">prioritypercentagecontrol &mdash; sequential percentage control (requires normalized scaling)</option>
       <option value="maintenance">maintenance &mdash; monitoring only, no dispatch</option>
     </select>
   </div>
-  <div class="form-row">
-    <label for="node-input-scaling"><i class="fa fa-arrows-h"></i> Scaling</label>
-    <select id="node-input-scaling" style="width:60%;">
-      <option value="normalized">normalized &mdash; demand interpreted as 0&ndash;100 % of group capacity</option>
-      <option value="absolute">absolute &mdash; demand interpreted as m³/h, capped by group min/max</option>
-    </select>
-  </div>
+  <p style="margin-top:8px;color:#666;font-size:11px;">
+    Demand is self-describing per <code>set.demand</code> message: a bare number is
+    treated as % of group capacity; <code>{value, unit}</code> with a flow unit
+    (<code>m3/h</code>, <code>l/s</code>, <code>m3/s</code>, &hellip;) is dispatched
+    in absolute terms. Negative value stops all pumps.
+  </p>
 
   <h3>Output Formats</h3>
   <div class="form-row">