v0.4.1 (version reporting fix)

Patch release. No change to conformance behaviour: the v0.2 profile requirement, the module set, and every finding are identical to 0.4.0.

Fixed

trace-tests --version reported the wrong version. __version__ was a second hardcoded literal alongside pyproject.toml and never moved, so it sat at 0.2.0 through both the 0.3.0 and 0.4.0 releases. A 0.4.0 install printed:

$ trace-tests --version
trace-tests, version 0.2.0

while importlib.metadata correctly returned 0.4.0.

This was worse than a cosmetic slip. The v0.2 profile cutover shipped in 0.4.0, and a 0.2.x suite rejects every v0.2 record, so --version is exactly the command you run to work out whether your suite matches your producer. It was the one command that could not answer, and it misled in the harmful direction: a correctly upgraded user was told they still had the version that cannot verify their records.

The version is now read from installed distribution metadata, so pyproject.toml is the single source of truth and the reported value cannot fall behind a release again. Stdlib only, no new dependency. Two regression tests guard against a hardcoded literal returning.

Upgrading

pip install --upgrade "agentrust-trace-tests>=0.4.1,<0.5"

If you are pinning the pair, the suite and the authoring library cut over to the v0.2 profile together and neither dual-accepts:

pip install "agentrust-trace>=0.5" "agentrust-trace-tests>=0.4.1,<0.5"

Full changelog: https://github.com/agentrust-io/trace-tests/blob/main/CHANGELOG.md