wiki: rewrite Home.md per visual-first 14-section template

- Run npm run wiki:all (wiki:contract + wiki:datamodel both wrote cleanly)
- Remove section 10 (State chart) — measurement is stateless, no FSM
- Renumber sections 11→10, 12→11, 13→12, 14→13 for correct 13-section layout
- Update banner git hash from afc304b to 125f964

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

wiki/Home.md

@@ -1,6 +1,6 @@
 # measurement
 
-> **Reflects code as of `afc304b` · regenerated `2026-05-11` via `npm run wiki:all`**
+> **Reflects code as of `125f964` · regenerated `2026-05-11` via `npm run wiki:all`**
 > If this banner is stale, the page may be out of date. Treat as informative, not authoritative.
 
 ## 1. What this node is
@@ -219,11 +219,7 @@ flowchart TB
 | Outlier detection | `outlierDetection.enabled` | varies | bool | `Channel._isOutlier` |
 | Simulation enabled | `simulation.enabled` | `false` | bool | `tick()` step |
 
-## 10. State chart
-
-**Skipped** — measurement is a pure pipeline. There is no FSM. The only mode switch (analog vs digital) is decided once at `configure()` time and never transitions thereafter; see section 4 for the static branching diagram.
-
-## 11. Examples
+## 10. Examples
 
 | Tier | File | What it shows | Status |
 |---|---|---|---|
@@ -233,7 +229,7 @@ flowchart TB
 
 Tier 1/2/3 visual-first example flows are still TODO (see `MEMORY.md` "TODO: Example Flows"). Screenshots will land under `wiki/_partial-screenshots/measurement/` when the new flows ship.
 
-## 12. Debug recipes
+## 11. Debug recipes
 
 | Symptom | First thing to check | Where to look |
 |---|---|---|
@@ -246,13 +242,13 @@ Tier 1/2/3 visual-first example flows are still TODO (see `MEMORY.md` "TODO: Exa
 
 > Never ship `enableLog: 'debug'` in a demo — fills the container log within seconds and obscures real errors.
 
-## 13. When you would NOT use this node
+## 12. When you would NOT use this node
 
 - Don't use measurement to **fuse** signals from multiple sensors — it's per-channel only. Aggregate at the parent.
 - Don't use measurement for **control output** — it's read-only signal conditioning. Use `rotatingMachine` / `valve` for actuation.
 - Don't use measurement for **alarm logic** — there is no threshold-trip output. Build that on top of the emitted reading at the parent or in a dashboard rule.
 
-## 14. Known limitations / current issues
+## 13. Known limitations / current issues
 
 | # | Issue | Tracked in |
 |---|---|---|