v0.15.4 release prep: make the agent-install path correct - #369
Merged
Conversation
Version moves to 0.15.4 in both manifests, with release notes, changelog entry and candidate markers across the control docs. This release exists because the published version does not yet carry the fixes an agent needs. v0.15.3 is what 'uvx alice-memory' installs today, and in it the tool descriptions steer an agent to alice_capture for anything it learns, which is review-gated, so the write reports success and alice_recall never returns it. Five of eleven core tools also reject agent identity, so an agent that stamps agent_id on every call fails on every read. Both are corrected on main and neither is published, which makes cutting this release the difference between a first Hermes install that works and one that silently loses everything it is told. No behaviour changed in alice_capture. It is review-gated by design and stays that way. Only the descriptions changed, so that an agent choosing between the two write verbs chooses the one that matches its intent. The notes name the remaining rough edge rather than hiding it: every caller-facing failure returns the single generic code tool_request_failed, so an agent cannot tell a bad argument from a missing record. A wider code taxonomy is designed and deliberately deferred, because it is quality rather than a blocker and the design touches a security control that suppresses exception text. Release-note state is pending/pending until the artifacts exist. Verified: release_check PASS for 0.15.4, control-doc truth PASS, release-static clean, 4544 unit passed 2 skipped, ruff and mypy clean across 233 files.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
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.
Cuts
v0.15.4. The reason to ship it now is concrete.Why this cannot wait
uvx alice-memoryinstalls v0.15.3, and I verified against a genuinely fresh install of it:So a Hermes install today gets descriptions that steer the agent to
alice_capturefor anything it learns. That path is review-gated: the write reports success andalice_recallnever returns it. And if the agent stampsagent_id, every read hard-errors.Both fixes are on
main(#368) and neither is published. This release is the difference between a first install that works and one that silently loses everything it is told.Contents
alice_memory_commitfor ordinary memory, including when the user has not askedNo behaviour change.
alice_captureremains review-gated by design.Stated honestly in the notes
Every caller-facing failure still returns the single generic code
tool_request_failed, so an agent cannot distinguish a bad argument from a missing record. A wider taxonomy is designed and deliberately deferred: it is quality rather than a blocker, and the design touches a control that deliberately suppresses exception text.Verification
release_checkPASS foralice-memory 0.15.4release-staticcleanOrdering
No tag yet. Gate from this branch first, then from the tag, then confirm all twelve exact-SHA checks are complete on the release commit before dispatching publish. That last step is the one that cost a wasted dispatch on v0.15.3.