Skip to content

Embedded Agent Toolkit 0.23.0

Latest
Latest

Choose a tag to compare

View all tags
@Nitmi Nitmi released this 13 Oct 17:56
· 2 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.23.0
d9995c7

Toolkit 0.23.0 adds JUnit XML export from fresh, offline hardware-test evidence evaluation.

python scripts/test_contract.py junit test-contract.json --run test-run.json --output test-results.xml --json
  • Reuse the contract evaluator to recheck input, contract/run and evidence hashes. Export the contract gate, each bound input, stage evidence check, assertion and cleanup requirement as distinct CI testcases.
  • Represent evaluated mismatches as failure, and missing/drifted/invalid/unevaluable evidence as error. Failed or incomplete evaluation still writes XML and exits 2; passing evaluation exits 0. Never skip missing evidence or overwrite an existing report.
  • Bind XML bytes, counts and SHA-256 in embedded-agent-toolkit.test-junit.v1. Keep no-hardware/no-component-execution/no-authorization scope, and do not invent target execution timings.
  • Escape XML and preserve control/surrogate characters as JSON literal escapes. Bound diagnostics with visible truncation, XML to 4 MiB and testcases to 263; keep native JSON for full context.
  • Update hardware-test Skill with optional CI reporting guidance, preserve nonzero status and provide a GitLab artifact example. Correct outdated installation-document component versions.

Validation includes 186 tests, plugin layout/release contract and four Skill validators, matching local builds, and independent source/installed CLI scenarios for passing, failed, missing and drifted evidence. The tagged workflow tests, builds twice and attests ZIP plus Bootstrap to refs/tags/v0.23.0.

The initial Windows CI exposed a test fixture comparing equivalent short/long evidence paths without resolving them. A test-only follow-up fixes that comparison and exercises an alternate path spelling; Windows and Ubuntu CI pass. Every packaged source file is identical between the immutable tag and the repaired CI commit. The tag and attested assets were retained unchanged.

The component catalog is unchanged. Existing station and project locks remain active; no component reinstall or hardware test is required for this file-only feature. No component MCP server or new runtime dependency is added. Verify the release's attestation and checksum before execution, install into a new versioned directory, and keep previous versions for rollback.

Assets 7
Loading