chore(release): 1.2.0 - #54
Merged
Merged
Conversation
Nine merged pull requests since 1.1, and none of them touched a frozen surface. Every change is a new field, a new entry shape, or a new document, so the number moves at the minor position and the audit fixture still verifies a trail a 1.0 daemon wrote, byte for byte. Version 1.1.0 -> 1.2.0 across all five crates. What the number now covers, and what the docs were not yet saying: Accessible paths through all three surfaces. VS Code and JetBrains name their chat structure, speakers and status to assistive technology, keep composer focus across turns, preserve transcript reading position, and confirm before clearing it. The terminal writes completed conversation once to native scrollback as selectable text, ships NO_COLOR, --no-animation, --plain-session and --message for line-oriented use, and restores terminal modes before suspending. docs/accessibility.md states the surface-specific paths, the limitations, and how to reach a human about them. The audit trail answers the question an auditor asks. A trail that recorded tool calls alone could not tell "this install did nothing" from "this install was busy and touched no tool". Every attempted turn is now sealed, including the turns Garrison's own admission gates refuse before the model ever sees them, and including which AGENTS.md files steered the turn. All of it is metadata: byte counts, hashes, and a stable refusal word, never the prompt and never the file. AGENTS.md project instructions, discovered under the session's approved root and gated by the policy bundle rather than by convention. A governed bundle decides enabled, restricted to named paths, or off; an ungoverned install or a policy ask that errors loads nothing, matching every other gate in this daemon. Project instructions are treated as untrusted content: they can shape what a turn asks for and never what the policy bundle, the approved root, the sandbox, or the approval gate decide. Release engineering that can be checked by someone who does not trust us. cargo deny gates every push, pull request and tagged release; each archive carries a CycloneDX SBOM per binary for its own target; SHA256SUMS is signed keylessly with cosign against the workflow's own OIDC identity. docs/supply-chain-policy.md is the written policy, including which inherited advisories are accepted today and why. Two corrections this commit makes rather than defers: docs/compatibility.md said turn entries were "Added in 1.1". They were not: that paragraph was written after the v1.1.0 tag and describes work shipping here. It now says 1.2, and covers the two additions that followed it, refusal entries and context_sources, on the same no-byte-moved terms. README described neither AGENTS.md discovery nor the supply-chain surface, both of which a reader evaluating a deployment would want before the download link rather than after it. The gap this release still ships with is the one 1.1 named: a completion reaches no admission gate (#22). Everything 1.0 listed under "Known gaps" remains, unchanged and still written down.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version 1.1.0 -> 1.2.0 across all five crates, plus the two doc corrections the release surfaced.
Nine merged pull requests since 1.1 and no frozen surface moved, so the number moves at the minor position.
agent/tests/audit_fixture.rsstill verifies a trail a 1.0 daemon wrote, byte for byte.What is in this diff
Cargo.lock.docs/compatibility.mdsaid turn entries were "Added in 1.1". They were not: that paragraph was written after the v1.1.0 tag and describes work shipping here. Corrected to 1.2 and extended to cover refusal entries andcontext_sourceson the same no-byte-moved terms.README.mddescribed neitherAGENTS.mddiscovery nor the supply-chain surface. Both belong in front of a reader evaluating a deployment.What the release covers
Accessible paths across VS Code, JetBrains and the terminal, with
docs/accessibility.md. Turn entries for every attempted turn, including the ones Garrison's own gates refuse and including whichAGENTS.mdsteered them, all as metadata rather than content. Policy-gatedAGENTS.mddiscovery. Advisory scanning, per-target SBOMs, and cosign-signed checksums.Still open, unchanged: inline completion reaches no admission gate (#22), and everything 1.0 listed under known gaps.