Repository navigation
fix: clarify scoped tool execution guidance - #12
Merged
Merged
Conversation
Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
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
Clarifies mounted-tool selection and permission boundaries in Work guidance, updates the Anchors + Work preset to the canonical nested Anchors manifest, and expands composition prompt coverage. Adds an explicit test-only Foundation candidate include alongside existing Tester candidate support for local integration qualification.
Why
Keep maintained bundle sources on
main, preserve caller and host authority boundaries, and ensure root and delegated prompt composition retain the intended instructions without leaking parent-only guidance to children.How to verify
read_file,glob,bash, andgrep.Breaking changes
None. Runtime enforcement, permissions, defaults, and retry policy are unchanged.