WASM schema and Studio

How firmware supplies a versioned Controller config contract to Studio validation and autocomplete.

The authoritative JSON Schema is not hard-coded in Studio. During a WASM build, firmware embeds the complete Controller config contract and exposes it through getControllerConfigContractJson().

flowchart LR
  P["Firmware parsers 0.12.11"] --> C["Controller config contract"]
  C --> W["WASM artifact"]
  W --> S["Studio Config Editor"]
  C --> D["This documentation"]
  S --> M["Monaco autocomplete"]
  S --> V["Ajv pre-write validation"]

Version changes

After another WASM is activated, Studio reads the contract again, re-registers the schema for the Controller Config Editor model and recompiles its validator. Autocomplete and accepted keywords therefore follow the active WASM artifact, not the Studio release.

Fail-closed behavior

Config writes are disabled when:

the WASM contract is missing or has an unsupported version,
JSON cannot be parsed,
a value does not match the JSON Schema,
a cross-section rule fails, such as multiple I2C entries, an unknown I/O label in a segment or a reversed DALI temperature range.

Reading config, history, copying and exporting remain available.

Machine-readable files

Generated from the versioned Spectoda/firmware contract for FW 0.12.11. Do not maintain these tables separately from the firmware contract.