v0.8.8

Operator administration uses a root-only launcher with isolated startup configuration, a fixed local endpoint and authentication from a protected token file. Install the matching Guard binary and launcher together; sudo guard-operator requires Guard 0.8.8 or newer and preserves relative file arguments and command input.

Linux release archives include a Unix installer with read-only checks and an explicit mode for updating the binary and launcher while preserving compatible existing service units, drop-ins, identities, configuration and state. The installer leaves service activation to the operator; the deployment guide covers stopped snapshots and rollback that retains displaced databases and sidecars.

v0.8.7

guard verb add --file and guard verb amend --file explain the required single YAML mapping in errors and help: start with name:, without a leading - or verbs: wrapper. Parse errors retain the underlying YAML diagnostic.

The prompt regression corpus explicitly configures three expected-ALLOW cases to require two matching decisions from three samples. Other cases, including every expected-DENY case, require unanimous matching. Evaluator errors, non-LLM results and missing required risk scores fail regardless of the vote. Risk checks include every sample.

v0.8.6

Guard 0.8.6 reports launch failures for approved commands as execution errors, with the observed failure stage when available and explicit start-state evidence. Genuine policy denials remain distinct.

Working-directory access uses the intended child identity, supplementary groups and capabilities. Child ownership extends through runtime registration and cleanup so an error after process creation retains accurate lifecycle reporting. Approval, rollback, audit and session history preserve execution outcomes, including unknown start state when evidence is unavailable.

The state database uses schema 15. Upgrade the daemon and all clients together. An older binary refuses the migrated database; rollback requires the matching pre-upgrade binary and consistent snapshot. Follow the upgrade and rollback contract.

v0.8.5

What's Changed

• Keep approved access additive outside its coverage by @morgaesis in #152

Full Changelog: v0.8.4...v0.8.5

v0.8.4

What's Changed

• Make authority timeout tests deterministic by @morgaesis in #150
• Validate typed file operands and add operator verb imports by @morgaesis in #151

Full Changelog: v0.8.3...v0.8.4

v0.8.3

What's Changed

• fix: treat closed stdout as a normal boundary by @morgaesis in #147

Full Changelog: v0.8.2...v0.8.3

v0.8.2

What's Changed

• fix: preserve authority and execution boundaries by @morgaesis in #146

Full Changelog: v0.8.1...v0.8.2

v0.8.1

What's Changed

• Bound execution, harden synthesis, and make daemon actions visible by @morgaesis in #143
• fix: correct authorization precedence and requester access by @morgaesis in #144

Full Changelog: v0.8.0...v0.8.1

v0.8.0

What's Changed

• fix(cli): name the authority behind a denial by @morgaesis in #133
• Explain what an access approval grants by @morgaesis in #134
• fix(audit): redact secret exposure details by @morgaesis in #136
• fix(gating): surface the armed auto-revert window by @morgaesis in #135
• feat(approvals): expose consequence-aware waits by @morgaesis in #137
• fix: harden matcher synthesis integrity by @morgaesis in #138
• Prepare v0.8.0 release by @morgaesis in #139

Full Changelog: v0.7.1...v0.8.0

v0.7.1

What's Changed

• Harden operator authority boundaries by @morgaesis in #131

Full Changelog: v0.7.0...v0.7.1