Test Suite 6 — Status labels

Harness function	suite6() in test-scripts/test-harness.js
Checks	7 (the # column below reconciles)
Kind	Synchronous

Proves the on-canvas status label against the design doc's table — fill, shape, and exact text for every label state. Assertions compare the full status string, so any drift in wording, counts, or number formatting fails loudly.

Baseline config (applies unless a scenario says otherwise): plain numeric node — mean aggregation, Above-mode, trigger 60 / release 55, quorum 2, staleness disabled, Emit aggregate on change only checked, heartbeat off, persistence off.

Traceability convention: the Check column is the harness's literal PASS/FAIL string — a failing line in the test output can be searched in this document verbatim. This document moves with the harness: a new, renamed, or removed check lands here in the same change.

---

6.1 Numeric label walk

One node walked through every state: fresh deploy → one source → quorum satisfied → triggered → disabled → enabled → quorum lost via remove.

#	Check	Protects
1	new node: grey dot Waiting F/Q	Fresh deploy shows Waiting (fresh/quorum: 0/2), grey dot
2	waiting counts update	The F/Q pair tracks incoming sources (1/2)
3	running: green dot with aggregate + fresh counts	Evaluated + untriggered: 52 (2/2 fresh), green dot; integers render without decimals
4	triggered: blue dot with Triggered prefix	Triggered: 65 (2/2 fresh), blue dot
5	`disabled: grey ring with Disabled	prefix`
6	`quorum lost while latched (Hold): yellow ring, Triggered	No quorum`

6.2 Boolean counts

A boolean node with one true and one false source.

#	Check	Protects
7	boolean status shows T/F of N counts	Boolean mode renders the aggregate as 1T/1F of 2, not a raw fraction