Tests Control

test-scripts/control-harness.js — the first harness exercising two node types talking through the registry seam: a real control node driving a real inline recorder.

Group	Why it exists
X1 — receipt vs delivery	The node's key semantic as a test: dump puts the incident on the recorder's outputs while the control emits a receipt — ok flag, command, target, the result attached, and inReplyTo correlation to the triggering message.
X2 — command tolerance	PAUSE and Resume work — case-insensitive, whitespace-tolerant, per the house command style.
X3 — mark & clear	msg.annotation rides into the mark on the tape; clear's receipt carries the count and the recorder emits its own cleared event.
X4 — query	The snapshot lands on the recorder's query output and the receipt carries it too.
X5 — unknown commands	Warn, red status, ok: false receipt with reason — and the recorder is provably untouched.
X6 — bad payloads	Numbers, objects, and missing payloads nack without throwing — the command port never crashes on garbage.
X7 — bad targets	No target configured, and a target id that was never deployed: distinct, named reasons in the nack.
X8 — lazy resolution	Commands work while the target is deployed and degrade to a clean "not deployed" nack after it closes — proving per-command resolution (no stale handle caching) and that the registry cleans up.