feat(mgc): editor defaults, compact status badge, mode-case fix, real example flows + dashboard

Editor (mgc.html)
- Drag-in defaults now expose mode (optimalControl) and scaling (normalized)
  via dropdowns in the edit dialog. Was: no control fields in the UI at all,
  so users had to send set.mode/set.scaling after deploy or live with the
  hidden schema defaults.

Wire-up (src/nodeClass.js)
- buildDomainConfig now bridges the flat editor fields (mode, scaling) into
  the nested schema shape (mode.current, scaling.current). Was: returned {}
  so the editor's mode/scaling never reached the runtime.

Mode-case bug fix (src/specificClass.js)
- Schema enum values are camelCase (optimalControl, priorityControl) but the
  runtime switch in _runDispatch matched lowercase only. With the default
  config, dispatch silently fell through to the warning branch and nothing
  ran. Normalise via String(this.mode).toLowerCase() so both forms work.

Status badge (src/io/output.js)
- Compacted from ~80 chars (mode | Ⓝ: 💨=Q/Qmax | ⚡=P | N machine(s)) to
  ~50 chars (mode | norm | Q=Q/Qmax m³/h | P=P kW | active/total x).
  Drops emoji glyphs that rendered inconsistently across themes; uses the
  same dot+fill convention as pumpingStation.

Output extension (src/io/output.js)
- getOutput() now also emits flowCapacityMin/Max, machineCount,
  machineCountActive. Was: only group-level totals + dist-from-peak +
  mode/scaling, so dashboards couldn't show capacity / active count
  without subscribing to each rotatingMachine individually.

Examples
- Drop pre-refactor stubs (basic.flow.json, integration.flow.json,
  edge.flow.json). They had a single MGC + inject + debug, no children,
  and never dispatched anything.
- 01-Basic.json: 1 MGC + 3 rotatingMachine pumps + Setup once-fires
  virtualControl + cmd.startup on all pumps via fan-out function. Numbered
  driver groups for Control mode / Scaling / Operator demand. Pumps
  register with MGC via Port 2 (child.register, automatic).
- 02-Dashboard.json: same plumbing + FlowFuse Dashboard 2.0 page with
  Controls (mode + scaling buttons, demand slider 0–100, stop + init
  buttons), Status (7 ui-text rows), Trends (3 charts: flow + capacity,
  power, BEP rel %), and a raw-output ui-template dumping every Port 0
  field. Fan-out function caches last-known values so deltas don't blank.

Wiki + README
- examples/README.md rewritten for the two-file set with canonical command
  surface table and "what to try" recipes.
- wiki/Home.md §11 (Examples) updated; §14 #4 (TODO flow item) replaced
  with the actual current limitation (no per-pump fan-out on Port 0).

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

examples/README.md

@@ -1,8 +1,51 @@
-# machineGroupControl Example Flows
+# machineGroupControl - Example Flows
 
-Import-ready Node-RED examples for machineGroupControl.
+Import-ready Node-RED examples for `machineGroupControl` (MGC). MGC is not a standalone node — it needs at least one `rotatingMachine` child to dispatch demand to. Both flows below ship three child pumps.
 
 ## Files
-- basic.flow.json
-- integration.flow.json
-- edge.flow.json
+
+| File | Tier | What it shows |
+|---|---|---|
+| `01-Basic.json` | 1 | One MGC + three `rotatingMachine` pumps driven by inject buttons. Setup once-fires `virtualControl` + `cmd.startup` on all three pumps; mode / scaling / demand are then driven by buttons. |
+| `02-Dashboard.json` | 2 | Same command surface driven by a FlowFuse Dashboard 2.0 page — mode + scaling buttons, demand slider, live status rows, three trend charts, and a raw-output table. |
+
+## Prerequisites
+
+- Node-RED with the EVOLV package installed (`machineGroupControl` and `rotatingMachine` registered).
+- For `02-Dashboard.json`: `@flowfuse/node-red-dashboard` (Dashboard 2.0).
+
+## Load a flow
+
+```bash
+curl -X POST -H 'Content-Type: application/json' \
+  --data @nodes/machineGroupControl/examples/01-Basic.json \
+  http://localhost:1880/flows
+```
+
+Or in the editor: Menu → Import → drag the file → Import.
+
+## Canonical command surface
+
+| Topic | Aliases | Payload | What it does |
+|---|---|---|---|
+| `set.mode` | `setMode` | `"optimalControl"`, `"priorityControl"`, `"prioritypercentagecontrol"`, `"maintenance"` | Switch dispatch strategy |
+| `set.scaling` | `setScaling` | `"normalized"`, `"absolute"` | Interpret demand as 0–100 % vs m³/h |
+| `set.demand` | `Qd` | number | Operator demand setpoint |
+| `child.register` | `registerChild` | child node id (string) | Manually register a child (Port 2 wiring does this automatically) |
+
+## 01-Basic — what to try
+
+1. Deploy. After ~1.5 s the Setup group auto-fires, putting all three pumps in `virtualControl` mode + sending `cmd.startup` to each.
+2. Click `set.demand = 50 %` — MGC's `optimalControl` picks the best pump combination by BEP-gravitation and dispatches `flowmovement` to the selected pumps.
+3. Click `set.demand = 100 %` — MGC switches to a higher combination, possibly engaging an extra pump.
+4. Switch mode to `priorityControl` and try the same demands — pumps now run equal-flow by priority order.
+5. Switch scaling to `absolute` — set.demand is now interpreted as m³/h (capped at the group min / max).
+6. `set.demand = 0` — MGC calls `turnOffAllMachines`, all pumps shut down.
+
+## 02-Dashboard — what to try
+
+1. Deploy → open `http://localhost:1880/dashboard/mgc-basic`.
+2. The dashboard auto-initialises the pumps; the `Initialize pumps` button on the page re-runs the setup manually.
+3. Drag the **Demand** slider — MGC dispatches and the Flow / Power / BEP charts react.
+4. Switch modes and scalings via the buttons; the Mode / Scaling rows in the Status panel reflect the change.
+5. Inspect the **Raw output** table for the full Port 0 surface (every field MGC emits, including `flowCapacityMax`, `machineCountActive`, `absDistFromPeak`, `relDistFromPeak`).