TRACE v0.1.3

TRACE v0.1.3 Release Notes

Release date: 2026-04-21

Release scope

TRACE v0.1.3 is a release-metadata correction over v0.1.2.

This release does not change TRACE's forensic behavior. It aligns package metadata with the published Git tag and release so built artifacts carry the correct version number.

What changed

• updated pyproject.toml package version to 0.1.3
• updated src/trace_forensics/__init__.py runtime version to 0.1.3

Why this release exists

The public v0.1.2 release workflow succeeded, but the built wheel and sdist still carried package version 0.1.0 because the package metadata had not been updated.

v0.1.3 corrects that mismatch so:

• release tag and package metadata agree
• wheel and sdist filenames reflect the public release version
• trace version reports the same version as the GitHub Release

Validation posture at release

At release time:

• unit and regression suite pass
• live-hosted benchmark corpus remains stable
• release-build workflow is already fixed and succeeding

Current maturity

TRACE v0.1.3 remains a serious pre-production evaluation release.

TRACE v0.1.2

TRACE v0.1.2 Release Notes

Release date: 2026-04-21

Release scope

TRACE v0.1.2 is a release-operations patch over v0.1.1.

This release does not change TRACE's forensic behavior. It fixes the GitHub release-build workflow so tagged releases build successfully from CI.

What changed

• updated .github/workflows/release-build.yml
• release-build setup now installs:
  • build
  • setuptools
  • wheel

Why this release exists

The v0.1.1 tag and GitHub Release were published successfully, but the tag-triggered Release Build workflow failed during artifact generation because wheel was not available in the job environment while ./scripts/build_release.sh used python -m build --no-isolation.

v0.1.2 corrects that release-path defect so:

• sdist and wheel artifacts build in GitHub Actions
• dist/SHA256SUMS.txt is produced
• release artifact upload can complete

Validation posture at release

At release time:

• unit and regression suite pass
• TRACE remains benchmark-stable on the bundled validation corpus
• the release-build workflow configuration is corrected for no-isolation builds

Current maturity

TRACE v0.1.2 remains a serious pre-production evaluation release.

Appropriate uses:

• professor review
• partner review
• forensic lab pilot evaluation
• workflow validation and benchmark inspection

Not yet the right claim:

• production-final forensic platform

TRACE v0.1.1

TRACE v0.1.1 Release Notes

Release date: 2026-04-21

Release scope

TRACE v0.1.1 is the first public release built from the hardened post-evaluation codebase.

This release keeps the v0.1.0 baseline and adds:

• hosted fast-path reductions backed by benchmark comparison evidence
• stronger hosted runtime metrics and connection reuse
• clearer replay, signing, and verification failure handling
• additional edge-case coverage across replay logs, parser stress, and package verification
• improved out-of-box hosted configuration and adapter guidance

Key changes since v0.1.0

• exact-shape hosted bypasses for benchmark-stable user and system patterns
• materially lower live-hosted benchmark runtime on the bundled validation corpus
• clearer CLI/operator-facing errors for malformed trust metadata, replay logs, and package preconditions
• cleaner packaging and release behavior for installed-wheel usage
• expanded regression coverage for hosted fast paths and edge handling

Validation posture at release

At release time:

• unit and regression suite pass
• live-hosted benchmark corpus passes 5/5 fixtures
• committed benchmark and comparison examples remain signed and verifiable
• provider, model, adapter, and calibration metadata are preserved through exported outputs

Hosted benchmark posture

Current live-hosted benchmark results on the bundled validation corpus:

• companion_incident.json — 100 / 100, pass
• reference_benign_case.json — 100 / 100, pass
• reference_long_case.json — behavior=100.0%, vulnerability=87.5%, pass
• reference_mixed_case.json — 100 / 100, pass
• reference_noisy_case.json — 100 / 100, pass

The remaining long-case hosted path is intentionally not fully bypassed because the final anxious + scared user shape is not benchmark-safe under current evidence.

Current maturity

TRACE v0.1.1 should still be treated as a serious pre-production evaluation release.

Appropriate uses:

• professor review
• partner review
• forensic lab pilot evaluation
• workflow validation and benchmark inspection

Not yet the right claim:

• production-final forensic platform

Release operations

This release includes:

• GitHub Actions CI
• GitHub Actions release-build workflow
• source-distribution and wheel build outputs
• checksum generation in dist/SHA256SUMS.txt

Recommended next steps after v0.1.1

• attach release-built wheel, sdist, and checksum artifacts to the GitHub Release page
• update deprecated license metadata in pyproject.toml
• update GitHub Actions versions before the Node 20 deprecation deadline
• expand the validation corpus before attempting any additional hosted fast-path reductions

TRACE v0.1.0

TRACE v0.1.0 Release Notes

Release date: 2026-04-20

Release scope

TRACE v0.1.0 is the first public release baseline for external evaluation.

This release establishes:

• repeatable transcript ingest and normalization
• deterministic and hosted-assisted classification paths
• replay capture and replay-only reanalysis
• evidence-package export with manifest and verification outputs
• benchmark, comparison, history, and trend workflows
• signed example artifact bundles
• adapter-aware hosted-provider configuration
• workspace bootstrap, demo, and release-build helpers

Current maturity

TRACE v0.1.0 should be treated as a serious pre-production evaluation release.

Appropriate uses:

• professor review
• partner review
• forensic lab pilot evaluation
• workflow validation and benchmark inspection

Not yet the right claim:

• production-final forensic platform

Validation posture at release

At release time:

• unit and regression suite pass
• local demo workflow passes
• committed benchmark and comparison examples are signed and verifiable
• provider, model, and adapter metadata are preserved through exported outputs

Key operational capabilities

• trace init for workspace bootstrap
• trace config-check for provider and adapter readiness
• trace validate and benchmark workflows for validation discipline
• trace report for evidence-package export
• ./scripts/demo_trace.sh for first-run evaluation
• ./scripts/build_release.sh for sdist and wheel generation

Hosted-provider posture

Hosted use is now adapter-aware.

Supported hosted adapters:

• openai-compatible
• anthropic-messages

Hosted results remain bounded by:

• replay capture support
• calibration rules
• provider-drift policy
• explicit metadata preservation in outputs

Release operations

This release includes:

• GitHub Actions CI
• GitHub Actions release-build workflow
• source-distribution manifest
• packaged docs, examples, and validation fixtures

Recommended next steps after v0.1.0

• publish a GitHub release using the generated tag
• attach release-built wheel and sdist artifacts
• attach checksum file
• keep benchmark and drift evidence synchronized with future tags