Release notes
HOL Guard v3.59.0a40
PreviewHOL Guard v3.59.0a40, released November 3, 2026, is a preview release with 5 additions, 5 improvements, 3 fixes and 1 other change across 11 merged pull requests. Highlights: Open Guard Cloud from accounts connect; Add Cross Exam coverage with terminator-aware stdio.
5 added · 5 improved · 3 fixed · 1 other
Key facts
- Version
- v3.59.0a40
- Channel
- Preview
- Published
- Previous release
- alpha/v3.59.0a39
- Merged pull requests
- 11
Documented changes
14 typed entries
Verified contributors
3 verified contributors · 14 credits
Attribution coverage
attribution complete; history inventory partial.
Install
Scope
Guard v3.59.0a40 is a preview release published 2026-11-03. Upstream documents: Guard 3.59.0a40 is an opt-in prerelease cut from dca7dac. Stable installations remain on the stable channel. 13 commits • 11 merged pull requests • 3 contributors since Guard 3.59.0a39. Its comparison base is alpha/v3.59.0a39. It includes 14 verified contribution deliveries with public evidence links.
Changes
Added
5- cloud-actionsOpen Guard Cloud from accounts connect (#7050) Evidence for this change
- commandAdd Cross Exam coverage with terminator-aware stdio (
101bc5f) Evidence for this change - cloud-actionsPreview an AI tool's Cloud actions settings (#7046) Evidence for this change
- mcp-serversAdd the opt-in Aletheia MCP contribution (
5c72ef7) Evidence for this change - cliSign in to Guard Cloud for cloud actions, one workspace per profile (#7038) Evidence for this change
Improved
5- mcpGroup observed MCP tools into connectors in the native store (#7047) Evidence for this change
- kimiCompose Kimi's managed hooks block in the native runtime (#7041) Evidence for this change
- mcpGroup and match discovered harness MCP servers in the native runtime (#7043) Evidence for this change
- cursorPlan Cursor editor MCP installs in the native runtime (#7039) Evidence for this change
- grokClean legacy Grok managed settings in the native runtime (#7040) Evidence for this change
- Direct commit 6ca6cde2b8e5: Merge remote-tracking branch 'origin/main' into repair/pr-6974
- Merged pull request #7043: refactor(mcp): group and match discovered harness MCP servers in the native runtime (#7043)
- Merged pull request #7047: refactor(mcp): group observed MCP tools into connectors in the native store (#7047)
- Merged pull request #7040: refactor(grok): clean legacy Grok managed settings in the native runtime (#7040)
- Merged pull request #7050: feat(cloud-actions): open Guard Cloud from accounts connect (#7050)
- Merged pull request #6974: feat(command): add Cross Exam coverage with terminator-aware stdio
- Merged pull request #7039: refactor(cursor): plan Cursor editor MCP installs in the native runtime (#7039)
- Merged pull request #7053: fix(dashboard): say what CIGAR does on Home and Settings in plain words (#7053)
- Merged pull request #7046: feat(cloud-actions): preview an AI tool's Cloud actions settings (#7046)
- Merged pull request #7038: feat(cli): sign in to Guard Cloud for cloud actions, one workspace per profile (#7038)
- Merged pull request #7036: feat(mcp-servers): add the opt-in Aletheia MCP contribution
- Merged pull request #7041: refactor(kimi): compose Kimi's managed hooks block in the native runtime (#7041)
- Merged pull request #7031: fix(command): project a setting prefix whose value holds a pattern (#7031)
- Merged pull request #7042: fix(command): read npm's own reporting keys in front of a test run (#7042)
Fixed
3- dashboardSay what CIGAR does on Home and Settings in plain words (#7053) Evidence for this change
- commandRead npm's own reporting keys in front of a test run (#7042) Evidence for this change
- commandProject a setting prefix whose value holds a pattern (#7031) Evidence for this change
Other changes
1- Guard 3.59.0a40 is an opt-in prerelease cut from
dca7dac. Stable installations remain on the stable channel. 13 commits • 11 merged pull requests • 3 contributors since Guard 3.59.0a39. Evidence for this change
Upgrade and compatibility
None documented.
Compare with the previous release
Predecessor on the same channel: alpha/v3.59.0a39
Verified contributors
Credits derive from public pull-request authorship, verified commit authorship, or verified co-authorship — never from thanks text or release metadata. Each distinct contributor is listed once; the evidence ledger paginates every published credit record.