Release notes
HOL Guard v3.59.0a41
PreviewHOL Guard v3.59.0a41, released November 3, 2026, is a preview release with 6 additions, 11 improvements, 1 fix and 1 other change across 15 merged pull requests. Highlights: Add opt-in Wever Labs hosted MCP contribution; Add opt-in Vicem Context Baton MCP contribution.
6 added · 11 improved · 1 fixed · 1 other
Key facts
- Version
- v3.59.0a41
- Channel
- Preview
- Published
- Previous release
- alpha/v3.59.0a40
- Merged pull requests
- 15
Documented changes
19 typed entries
Verified contributors
4 verified contributors · 19 credits
View the complete verified rosterAttribution coverage
attribution complete; history inventory partial.
Install
Scope
Guard v3.59.0a41 is a preview release published 2026-11-03. Upstream documents: Guard 3.59.0a41 is an opt-in prerelease cut from 91822de. Stable installations remain on the stable channel. 18 commits • 15 merged pull requests • 4 contributors since Guard 3.59.0a40. Its comparison base is alpha/v3.59.0a40. It includes 19 verified contribution deliveries with public evidence links.
Changes
Added
6- mcp-serversAdd opt-in Wever Labs hosted MCP contribution (
b7688ee) Evidence for this change - mcp-serversAdd opt-in Vicem Context Baton MCP contribution (
7a4f345) Evidence for this change - cloud-actionsCheck the saved sign-in live in status and add doctor (#7058) Evidence for this change
- cloud-actionsApply and restore AI tool settings (#7056) Evidence for this change
- Writes only while the file still holds the bytes the preview read, and checks again right before the move (
changed_since_previewotherwise). A new file is linked into place, so a file created in the meantime is never… - Copies the previous file into the Guard home first (folder 0700, files 0600, last 10 kept). If no copy can be kept, nothing is written (
backup_failed). - Reads the file back and puts the previous one back if it does not match (
write_not_verified).
- Writes only while the file still holds the bytes the preview read, and checks again right before the move (
- extension-builderPoint cloud binding errors at the rejected binding (#7057) Evidence for this change
- build request (
validate,compile,check):/cloud_bindings/N/bindings/M - source stream (
compile-stream):/records/N/bindings/M
- build request (
- mcpAdd Rel-Time Protocol (@rel-time/mcp-server) contribution (
37c15c0) Evidence for this change
Improved
11- isolation-providerCheck provider plans, artifacts and the managed registry in the native runtime (#7068) Evidence for this change
- adaptersDecide the Grok and Muse approval wait in the native runtime (#7062) Evidence for this change
- cursorRender the Cursor hook client in the native runtime (#7063) Evidence for this change
- adaptersDecide harness setup status and diagnostic warnings in the native runtime (#7060) Evidence for this change
- opencodeShape the OpenCode launch command and environment in the native runtime (#7059) Evidence for this change
- fleet-posturePlan and size the posture report in the native runtime (#7051) Evidence for this change
- codexCheck Codex host app inventory replies in the native runtime (#7055) Evidence for this change
- workspace-syncBuild and trim the workspace assessment summary in the native runtime (#7054) Evidence for this change
- grokDrop the unused Python Grok hook renderer (#7044) Evidence for this change
- copilotPlan Copilot MCP installs in the native runtime (#7052) Evidence for this change
- zcodeRender ZCode hook settings in the native runtime (#7048) Evidence for this change
- Merged pull request #7055: refactor(codex): check Codex host app inventory replies in the native runtime (#7055)
- Merged pull request #7058: feat(cloud-actions): check the saved sign-in live in status and add doctor (#7058)
- Merged pull request #7051: refactor(fleet-posture): plan and size the posture report in the native runtime (#7051)
- Merged pull request #7068: refactor(isolation-provider): check provider plans, artifacts and the managed registry in the native runtime (#7068)
- Merged pull request #7056: feat(cloud-actions): apply and restore AI tool settings (#7056)
- Merged pull request #7048: refactor(zcode): render ZCode hook settings in the native runtime (#7048)
- Direct commit d2c7e908971b: Merge remote-tracking branch 'origin/main' into feat/mcp-rel-time
- Merged pull request #7062: refactor(adapters): decide the Grok and Muse approval wait in the native runtime (#7062)
- Merged pull request #7054: refactor(workspace-sync): build and trim the workspace assessment summary in the native runtime (#7054)
- Merged pull request #7044: refactor(grok): drop the unused Python Grok hook renderer (#7044)
- Merged pull request #7065: fix(cigar): rank prompt files by word rarity and keep the first prompt after a break (#7065)
- Merged pull request #7057: feat(extension-builder): point cloud binding errors at the rejected binding (#7057)
- Merged pull request #7063: refactor(cursor): render the Cursor hook client in the native runtime (#7063)
- Merged pull request #7061: feat(mcp-servers): add opt-in Wever Labs hosted MCP contribution
- Merged pull request #7064: feat(mcp-servers): add opt-in Vicem Context Baton MCP contribution
- Merged pull request #7060: refactor(adapters): decide harness setup status and diagnostic warnings in the native runtime (#7060)
- Merged pull request #7052: refactor(copilot): plan Copilot MCP installs in the native runtime (#7052)
- Merged pull request #7049: feat(mcp): add Rel-Time Protocol (@rel-time/mcp-server) contribution
- Merged pull request #7059: refactor(opencode): shape the OpenCode launch command and environment in the native runtime (#7059)
Fixed
1- cigarRank prompt files by word rarity and keep the first prompt after a break (#7065) Evidence for this change
Other changes
1- Guard 3.59.0a41 is an opt-in prerelease cut from
91822de. Stable installations remain on the stable channel. 18 commits • 15 merged pull requests • 4 contributors since Guard 3.59.0a40. Evidence for this change
Upgrade and compatibility
None documented.
Compare with the previous release
Predecessor on the same channel: alpha/v3.59.0a40
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.