Embedded Agent Toolkit 0.38.0

Toolkit 0.38.0 adds a documented route for the published nRF52840 watchdog model workflow. Simulation selects sim-runner 0.10.0, hil-runner 0.15.0 and embedded-trace 0.15.0, checking 99 payload files. Three short Skill routes lead to the packaged docs/simulation-watchdog.md guide.

Native sim owns the independent watchdog plan/report and nominal verdict. HIL preflights all cases and preserves fail-stop/cleanup; Trace retains exact model, raw reset, callback and guest spans. Stopped feeding and a disabled watchdog model remain failed nominal regressions even when their effects are observed. Missing or timeout evidence remains unknown. Filtering or importing saved evidence cannot replace that verdict. Modeled reset and CONFIG tags do not qualify physical reset, low-power behavior or protection.

Instruments retain lab-instruments 0.11.0 and hil-runner 0.12.0 while using the identical Trace 0.15.0 wheel/source (96 files); standalone Trace checks 28 files. Historical simulation/instrument candidate modes remain separate at 69/74 files. Older or mixed environments fail without fallback. The toolkit adds no executor, MCP registration, per-run flash confirmation or automatic physical fallback. Native workstation selection and bounded flashing sessions are unchanged.

Local Python 3.11/3.13 each ran 279 tests (276 passed, three existing platform skips), reproducible builds, candidate installations with all 74 files matching, and mode/version rejections. Each interpreter preserved 31 full watchdog evidence results and 52 views of 26 existing instrument bundles without repeating native capture. Warm in-process Python 3.13 static inspection medians were approximately 86/84/24 ms for simulation/instruments/standalone Trace, excluding startup, cold I/O and RSS; these are not an SLA.

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