MM-005 lock the version probe contract - #7
Draft
himattm wants to merge 1 commit into
Draft
Conversation
The --version behavior was already restored in the stack base, but the backlog acceptance criterion had no dedicated regression and the installed skill depends on that exact probe. Cover both --version and -V against the crate semantic version and assert the packaged navigation skill still names minimap --version as its prerequisite. Verified with the targeted version contract, cargo test --workspace, Clippy with warnings denied, formatting checks, and the minimap binary build.
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.
What changed
Add a dedicated contract for both
minimap --versionandminimap -V, checking the exact crate semantic version. The same test verifies that the packaged navigation skill continues to useminimap --versionas its prerequisite probe.Why
The behavior had been restored in the stack base, but the backlog acceptance criterion lacked an independent regression and the installed skill depends on the exact command.
Impact
CLI changes cannot silently break installation detection or drift away from the packaged skill.
Validation
--versionoutput-VoutputStack
Depends on #6; base branch:
agent/mm-004-concise-android-analytics-error.