Release v0.19.0: AGY 1.2.2 compatibility and native repair - #133
Merged
Merged
Conversation
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
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.
AGY 1.2.2 can finish with exit zero after a partial-output timeout, and native same-conversation repair needs additional narrowly scoped initialization and SQLite metadata access. This change activates the verified 1.2.2 compatibility records, classifies refused actions and the observed timeout without discarding valid candidates, and restores the exercised native normal/repair workflow.
The skill keeps automatic selection, authority boundaries, same-scope repair, and driver-owned assurance while moving advanced procedures into references. Package and client metadata advance to 0.19.0.
Validation:
testpassed for5db9f2416c7bc53fbf4a7bf05e11d30c9fede01e(run 34757832501).Limits: live denial/partial-output canaries established the provider signatures, while valid-candidate preservation is covered by synthetic controller tests. This does not establish general provider correctness, future authentication/quota, or hostile same-user isolation. SkillStore publication is tracked separately from the GitHub release.
Release CI correction: the native settings fixture now invokes the canonical Command Line Tools Python image directly, avoiding the host-selected developer-tool shim. All expected permission denials remain unchanged; no production sandbox rule was widened. The final exact-head hosted gate reruns every canonical stage.
One local locator-cleanup assertion failed once without per-condition diagnostics. The unchanged retry and targeted four-condition probe passed; the same checks also passed in both full gates. The initial observation is retained with an unconfirmed cause. No cleanup assertion or production boundary was weakened.