Release notes

HOL Guard v3.44.0a10

Preview

Published Original GitHub release for alpha/v3.44.0a10

Documented changes

53 typed entries

Verified contributors

Attribution coverage

attribution complete; history inventory partial.

Scope

Guard v3.44.0a10 is a preview release published 2026-10-13. Upstream documents: Guard 3.44.0a10 is an opt-in prerelease cut from 6b3abc6. Stable installations remain on the stable channel. 22 commits • 20 merged pull requests • 3 contributors since Guard 3.44.0a9. Its comparison base is alpha/v3.44.0a9. It includes 22 verified contribution deliveries with public evidence links.

Changes

Added

10
  • runtime: Check Guard's private files on Windows before the bridges trust them (#4501) Evidence for this change
  • runtime: Compile native hook bridges on Windows (#4500) Evidence for this change
  • guard: Answer Oh My Pi hooks from the native resident (#4486) Evidence for this change
  • The resident's hook_direct operation answers Pi and Oh My Pi PreToolUse (including calls with no event name), UserPromptSubmit, and lifecycle events. Evidence for this change
  • PostToolUse is answered in the resident when the managed policy requires no structured-output mediation. Python publishes the exact managed-policy view the daemon resolves from (structured_output_config). The… Evidence for this change
  • The Pi extension posts to the daemon, so the daemon's /v1/hooks/{harness} handler asks the resident first through the existing evidence-drain resident client. It returns the edge's harness response unchanged. Any… Evidence for this change
  • guard: Answer Cursor reviews and prompts from the native resident (#4488) Evidence for this change
  • preToolUse reviews go through the same saved-decision, approve-once and review-queue path the other harnesses use. cursor-hook-bridge prints the paused review in the same shape as Cursor's hook client. Evidence for this change
  • A pause is answered natively only when its approval link reaches the agent unchanged. That means the Guard home has no daemon auth token, or the link is not loopback. A loopback link that the client may sign still goes… Evidence for this change
  • UserPromptSubmit prompts are answered with the edge's own harness response, which the bridge renders the way the client does. Evidence for this change

Improved

3

Fixed

13

Other changes

27
  • Documented change: Guard 3.44.0a10 is an opt-in prerelease cut from 6b3abc6. Stable installations remain on the stable channel. 22 commits • 20 merged pull requests • 3 contributors since Guard 3.44.0a9. Evidence for this change
  • guard: Share identical git probe queries within one evaluation (#4507) Evidence for this change
  • guard: Leave the background evidence drain out of the pi hook RPC budget (#4508) Evidence for this change
  • guard: Re-run a gate case once when the native review misses its budget (#4499) Evidence for this change
  • guard: Exclude the opt-in guard mcp serve dispatcher from runtime scope (#4490) Evidence for this change
  • Merged pull request #4473: fix(guard): allow chains that stage and reuse private temp files (#4473) Evidence for this change
  • Merged pull request #4508: test(guard): leave the background evidence drain out of the pi hook RPC budget (#4508) Evidence for this change
  • Merged pull request #4491: fix(codex): leave Codex approval requests to Codex's own prompt (#4491) Evidence for this change
  • Merged pull request #4488: feat(guard): answer Cursor reviews and prompts from the resident (#4488) Evidence for this change
  • Merged pull request #4482: fix(guard): allow bounded in-place sed substitutions on workspace files (#4482) Evidence for this change
  • Merged pull request #4485: fix(guard): keep sync working on stores with more than 4,096 events (#4485) Evidence for this change
  • Merged pull request #4489: fix(guard): treat package-manager directory flags like cd into that directory (#4489) Evidence for this change
  • Merged pull request #4500: feat(runtime): compile native hook bridges on Windows (#4500) Evidence for this change
  • Merged pull request #4499: test(guard): re-run a gate case once when the native review misses its budget (#4499) Evidence for this change
  • Merged pull request #4492: fix(guard): allow chains that copy readable files into private temp files (#4492) Evidence for this change
  • Merged pull request #4498: refactor(guard): answer Kubernetes secret-read checks from the resident (#4498) Evidence for this change
  • Merged pull request #4494: fix(guard): release proven Oh My Pi directory listings Evidence for this change
  • Merged pull request #4487: fix(guard): allow local Git writes in proven sibling repositories (#4487) Evidence for this change
  • Merged pull request #4486: feat(guard): answer Oh My Pi hooks from the native resident (#4486) Evidence for this change
  • Merged pull request #4501: feat(runtime): check Guard's private files on Windows before the bridges trust them (#4501) Evidence for this change
  • Merged pull request #4464: fix(guard): prove sibling glob reads and admit read-only command inspection (#4464) Evidence for this change
  • Merged pull request #4490: chore(guard): exclude the opt-in guard mcp serve dispatcher from runtime scope (#4490) Evidence for this change
  • Merged pull request #4474: refactor(guard): remove uncalled helpers from approvals and the daemon (#4474) Evidence for this change
  • Merged pull request #4481: fix(guard): release approved Oh My Pi learn results Evidence for this change
  • Merged pull request #4468: fix(guard): let sibling worktree probes, pwd paths and cd-then-run steps proceed (#4468) Evidence for this change
  • Merged pull request #4507: perf(guard): share identical git probe queries within one evaluation (#4507) Evidence for this change
  • Merged pull request #4484: refactor(guard): build GitHub permission specs where the extension is declared (#4484) Evidence for this change

Upgrade and compatibility

None documented.

Compare with the previous release

Predecessor on the same channel: alpha/v3.44.0a9

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.

Contributors

Evidence ledger22 credits