Releases
Current source status, pinned release evidence, and availability — rendered from the typed facts layer at build time.
Audience
Users who verify what they install.
Task path
- Read the source status and verification date: whether the public projections were reachable and consistent at the last check.
- Review the pinned release state: a pinned entry exists only when an immutable artifact and a public checksum are both verifiable.
- Read the release observations: each entry records what was actually observed, including mismatches and non-production states — they are evidence, not recommendations.
- Compare the evidence against the public repositories before relying on any release.
Pinned release
- Version
- 0.3.40
- Tag
0.3.40- Source commit
589e1e5183ddc61e825a68fa9be94d6ac07a8608- Withdrawal status
- active
- Verified at
- 2026-09-15
Public channel artifacts · GitHub
- Artifact
- tenetora-0.3.40.zip
- Artifact URL
- https://github.com/lcgyl/Tenetora/releases/download/0.3.40/tenetora-0.3.40.zip
- Release manifest
- https://github.com/lcgyl/Tenetora/releases/download/0.3.40/manifest.json
- SHA256
4035d5c8408f9787d085ef7f7b0befa9ed93af76edf67868d5fd1d459b2c0c50- SHA256 source
- GitHub release 389261466 资产匿名下载实测 SHA256（2026-09-15），与本地从 canonical tag 0.3.40 经发布管线构建的投影资产逐字节一致；.sha256 sidecar 文件内容一致。
Public channel artifacts · Gitee
- Artifact
- tenetora-0.3.40.zip
- Artifact URL
- https://gitee.com/lcgyl/tenetora/releases/download/0.3.40/tenetora-0.3.40.zip
- Release manifest
- https://gitee.com/lcgyl/tenetora/releases/download/0.3.40/manifest.json
- SHA256
2f899234ea2717882b87518d81c817fae10755637442f8b0d68231af60c5f05b- SHA256 source
- Gitee release 1146101 资产匿名下载实测 SHA256（2026-09-15），与本地从 canonical tag 0.3.40 经发布管线构建的投影资产逐字节一致；.sha256 sidecar 文件内容一致。
Release observations
Preview release 1
- Version
- 0.3.16
- Tag
0.3.16- Source commit
8af1cbc355c3c60be1caf8aaa0f026faacea5981- Artifact
- tenetora-0.3.16.zip
- SHA256
658458f81aefc1d70249616e8c36f08b917dc52624567c3eb93b9cc7865c58dc- SHA256 source
- 0.3.16 release manifest 的 sha256 字段（发布端 manifest，经受管升级通道获取；manifest commit 与 tag 0.3.16 commit 前缀一致，file_sha256 与已安装树 219/219 个文件一致）；公开链接不可得，故 releaseManifestUrl/artifactUrl 为 null
- Verified at
- 2026-09-01
Source conflict 1
- Manifest version
- 0.2.0
- Manifest commit
d48205295144492eff437116aea46f16e986f4ad- Tag commit
7babee0aca46515df48e5056bbcddda72fb4aee6- Artifact
- tenetora-0.2.0.zip
- SHA256
90c036b2a0e38dd7ac03fbbd64fa4cce32b8f430b146cb1eb3c959b5e13b50bd- SHA256 source
- dist/agent-harness-0.2.0.zip.sha256；release-notes 0.2.0 声明 canonical/legacy ZIP 字节一致
- Verified at
- 2026-08-14
manifest.json 声明 commit d48205295144492eff437116aea46f16e986f4ad，与 0.2.0 tag 实际 commit 7babee0aca46515df48e5056bbcddda72fb4aee6 不一致；按冲突观测保存，不包装为已验证 release。
Release notes
Per-version behavior changes and compatibility boundaries, rendered from the typed content layer and mirroring the notes shipped with the source repositories:
Release notes
0.3.402026-09-14
Changes
- doctor and status now report missing or damaged registered local-environment paths — read-only checks that never read file contents.
- PreToolUse denies high-confidence destructive operations (delete, move, truncate, write, edit) against registered paths; boundary matching avoids hitting adjacent files.
- Unmanaged-workspace silence is locked in with Stop regression coverage; the Git-only onboarding reminder contract is preserved.
- The machine registry gains a bounded 30-day stale-expired marker and an explicit prune operation; nothing is deleted in the background.
Compatibility
- Workspaces without .tenetora/ remain free of governance context injection and interception.
- Local-environment protection applies only to registered paths; hosts that cannot resolve a structured tool name and path do not block speculatively.
- Expired-registry cleanup is explicit (tenetora installations prune --expired) and removes registry metadata only — never project directories, .tenetora, local environment files, or third-party configuration.
0.3.392026-09-14
Changes
- Localized Windows mklink /J output is decoded with UTF-8 replacement handling during release activation, so a system code page no longer breaks the upgrade process.
- A failed mklink keeps its first diagnostic line instead of disappearing.
- A zero-exit mklink invocation that did not actually create the temporary junction is now reported as an error.
Compatibility
- POSIX symlink activation is unchanged; Windows exit codes, rollback behavior, and installation scope semantics are unchanged.
- Junction regression tests require a Windows runner; macOS/Linux verify the non-Windows paths only.
Limitations
- No production release entry is offered while the public sources are unverified.
- Recorded observations capture verified release data, but are never production install entries or recommendations.
- Withdrawn or conflicting releases are never presented as recommended.
Next steps
