RuntimeCourier Class

Detailed Description

Bridges a single Runtime instance (Agent-side) and a SyncSection (typically `"fixo-runtime"` with LOCAL_AUTHORITATIVE ownership) so Remote can subscribe to discover the active preset, stanza sets, per-stanza input metadata, runtime status, and sensor readbacks without bespoke wire-protocol code.

The path layout follows the spec at 11-channels-and-coexistence.md — Phase 16 renamed `setCount` / `sets/<i>` to `channelCount` / `channels/<i>`. The full ABI + codegen rename (16b) follows. fixo-runtime/preset fixo-runtime/status fixo-runtime/channelCount fixo-runtime/channels/<i>/active // quint32 firmware-numeric id fixo-runtime/channels/<i>/activeStanzaIdStr // string id (§SIA-H-4) fixo-runtime/channels/<i>/stanzaCount fixo-runtime/channels/<i>/stanzas/<j>/{id,name,lobeType,namedActivity} fixo-runtime/channels/<i>/stanzas/<j>/inputs/<k>/{name,kind,min,max,default} fixo-runtime/sceneCount // populated when scenes present fixo-runtime/scenes/<s>/{id,name,assignments} fixo-runtime/lastAppliedScene // reserved for phase 17a; defaulted empty fixo-runtime/sensorCount fixo-runtime/sensors/<i>/{name,value,unit}

This class is intentionally not a Courier subclass — the wire transport is provided by ConfigSyncCourier already, which carries any registered SyncSection. RuntimeCourier is the publisher that pumps Runtime state into the section.

Inbound writes from Remote (active-stanza selection, input slider values) are picked up via the section's valueChanged signal and forwarded to Runtime::activate / setInput.