Historical version
This page records design, operation, or validation facts from an earlier release. It is not current V7.17.3 guidance. Start from the documentation hub for current instructions.
V7.14.4 Validation Record¶
- npm
latestand GitHubrust-v0.159.2both identify0.159.2as a non-prerelease stable release. - npm integrity, tarball SHA-256, exact CLI-output digests, and official tag commits
8e68a98ef03cdde76d2e6800791ebdf1b3b95b24(0.159.1) andff6aec96948b70d94983af2641a6b67c94faeff5(0.159.2) were read independently. - Hook discovery/schema, apply_patch handler, and context hashes match
0.159.0; all three0.159.xreleases use the frozenresult-v158profile. - The 0.159.1/0.159.2 isolated cells remain bound to the unchanged component registry. V7.14.4 full validation passed with 816 package tests and 231 runtime tests under the new bounded timeout.
- The account management CLI read back
0.159.2; Plugin install, verify, and doctor read back7.14.4andHOST_COMPATIBLE. A new read-only ephemeral Desktop bundled-component process0.158.0-alpha.2.1returnedDESKTOP_ACCEPTANCE_PASS. - GitHub Actions run
36846683350, attempts 1-3, failed closed after the Windows Python 3.11 package suite reached its 1800-second ceiling; the retained job outputs reportexecution_status=TIMEOUTand no assertion failure. V7.14.4 raises that bounded ceiling to 3600 seconds and retains explicit timeout evidence. - CI, annotated tag, Draft, six assets, SHA256SUMS, witnesses, provenance, public Release, and anonymous downloads remain separate gates.