Overview

The reconciliation point for the per-suite test documents. The harness (test-scripts/test-harness.js, run via npm test) prints a total that must equal the sum of the per-suite counts below; a mismatch means a suite document has drifted from the code.

Suite	Name	Document	Kind	Checks
1	Output routing & envelope shape	Test Suite 1 — Output routing & envelope shape	Sync	27
2	Aggregation functions	Test Suite 2 — Aggregation functions	Sync	9
3	Boolean mode	Test Suite 3 — Boolean mode	Sync	15
4	Commands	Test Suite 4 — Commands	Sync	22
5	Threshold set-commands & release-follows-trigger	Test Suite 5 — Threshold set-commands & release-follows-trigger	Sync	22
6	Status labels	Test Suite 6 — Status labels	Sync	7
7	Staleness, quorum policies, heartbeat	Test Suite 7 — Staleness, quorum policies, heartbeat	Async	24
8	Persistence	Test Suite 8 — Persistence	Async	18
			Total	144

Conventions shared by every suite document (stated in each, since they are self-contained): the Check column carries the harness's literal PASS/FAIL strings for verbatim searchability; pattern rows (e.g. Suite 1's eleven envelope fields) show a pattern once with the substitutions listed; the Protects column names the design rule the check defends. Each document declares its own baseline config and any per-scenario deviations.

House rule: these documents move with the harness — a new, renamed, or removed check lands in its suite document (and this index's counts) in the same change. A stale line is a defect.

Real-environment items no suite can verify (per the design doc's Testing section): editor status rendering (Suite 6 proves the strings, not the canvas), and restore timing in a live Node-RED runtime.