chore(release): 1.3.0 - #57
Merged
Merged
Conversation
One merged pull request since 1.2, and it closes the gap the last two releases shipped with. Nothing frozen moved. Version 1.2.0 -> 1.3.0 across all five crates. Inline completion now crosses the admission gates. `_garrison/complete` resolved the session that owns it and then made a paid model call; ownership proves the client holds the session and says nothing about whether this install may spend. An install refused from running a turn kept spending on every typing pause, and nothing bounded how many were in flight. Every gate but the session keeper now answers a completion as it answers a turn. The keeper is the exception because both of its rules are about a stored record a completion never writes, and refusing one because an earlier turn was left open would stop a developer's editor for a reason that is not about them. Policy turned out to be the gate that mattered most, which is not what the issue expected. It called policy unclear on the grounds that a completion runs no tools, but that gate does not gate tools: it refuses an install with no policy state, an Ungoverned one, and one whose configured provider is not an approved endpoint in the bundle. A completion sent the code around a cursor to exactly that provider, on every pause. It was the least gated path to the least approved endpoint. A refused completion is sealed and an admitted one is not, because a debounce timer decides how often that path is entered and a trail written by a timer rather than by a person is noise wearing the shape of evidence. docs/compatibility.md records this as a change within the ACP promise rather than against it. The request and response shapes are untouched, and a refusal is answered the way every other failure on that path already was: an empty completion, never an error. A client written against 1.0 needs no change, because "no suggestion" was always a reply it had to handle. What 1.3 still ships with: everything 1.0 listed under known gaps. `network_egress` and `allow_unsandboxed_escalation` are recorded and not enforced, schemas are unsigned, Graph is unproved against a real tenant, console logins are not deactivated by the sync, and there is no provisioned database. The completion gap that 1.1 and 1.2 both named is gone.
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.2.0 -> 1.3.0 across all five crates, plus the compatibility disposition the change needs.
One merged pull request since 1.2 (#56), and it closes #22 — the gap both the 1.1 and 1.2 release notes shipped with. Nothing frozen moved.
What is in this diff
Cargo.lock.docs/compatibility.mdgains a disposition on the ACP surface:_garrison/completenow crosses the admission gates, but its request and response shapes are untouched and a refusal is answered the way every other failure on that path already was, with an empty completion rather than an error. A client written against 1.0 needs no change, because "no suggestion" was always a reply it had to handle. What changed is how often it is the true one.The README and control-plane changes for this work landed with #56 itself, including removing the known-gaps bullet.
Known gaps
Everything 1.0 listed is still there. The completion gap 1.1 and 1.2 both named is gone.