Embedded Agent Toolkit 0.37.0

Toolkit 0.37.0 adds a documented route for the published SPI0/LM74 sensor and fault evidence workflow. The simulation environment now selects sim-runner 0.9.0, hil-runner 0.14.0, and embedded-trace 0.14.0, verifying 97 payload files. Short Skill routes lead to docs/simulation-spi.md, which is included in the release package.

The workflow preserves signed Q4 temperature words, two-byte transfers, four model observations, native assertion outcomes, cleanup, and spi_frame_slip_span evidence. Model byte consumption by the fixed monitor Transmit operation is described as model behavior; it does not establish an electrical bus fault. Saved failed, unknown, sampled, and empty views retain their native meaning. The toolkit adds no second executor or automatic physical fallback.

Instruments retain lab-instruments 0.11.0 and hil-runner 0.12.0 while selecting the same published Trace 0.14.0 identity (96 files); standalone Trace verifies 28 files. Historical simulation and instrument candidate modes remain separate at 69 and 74 files. Older optional environments must use their matching toolkit or be upgraded; inspection does not silently fall back. Native workstation component selection, flashing session authorization, and component MCP ownership are unchanged.

Local Python 3.11 and 3.13 qualification ran 279 tests per interpreter (276 passed, three existing platform skips), reproducible builds, two candidate installations with all 73 files matching, and mode/version rejection checks. Each interpreter preserved 31 saved SPI/I2C/GPIO results and 52 views of 26 existing instrument bundles without repeating native capture. Warm in-process Python 3.13 static inspection medians were approximately 149/121/32 ms for simulation/instruments/standalone Trace; these exclude startup and cold I/O and are not an SLA.

The ZIP and standalone bootstrap are the two attested subjects, with checksum files for both. Bootstrap installs a versioned toolkit and verifies provenance; it does not activate the Codex plugin, install components, or modify PATH by default. Static readiness, provenance, and model evidence do not establish physical device state, firmware identity, or instrument qualification.