Field note /
A tag is not a release, and source is not the installed runtime
Agent-Workflow reached its first preview tag after hardening release dependency and installed-runtime identity, but publication remains a separate evidence state.
How the claim changed
Belief
A green repository with release tooling and the intended version tag should be enough to treat the preview release path as proven.
Evidence
Pre-release work assembled release policy, dependency locking, assets, checksums, provenance, preview gating, and an annotated v0.12.0 tag at the intended source commit.
Contradiction
The tag-only release path had drifted to an older comparative-eval source even while ordinary CI was green, a stale installed benchmark wheel later produced a false version diagnosis, and the correct v0.12.0 tag still has no observed GitHub Release or release-workflow run.
Correction
Make the durable dependency lock the single release authority, verify repository source, built wheel, and installed distribution identity separately, and treat tag creation, workflow execution, and publication as distinct states.
Current claim boundary
Agent-Workflow v0.12.0 is tagged as the intended first public preview. It should not be described as published until a GitHub Release and release evidence exist.