Skip to content

fix: clarify scoped tool execution guidance - #12

Merged
Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/explicit-execution-boundaries
Oct 21, 2026
Merged

Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/explicit-execution-boundaries

Conversation

@bkrabach

Copy link
Copy Markdown
Contributor

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

  • CI runs the full Work composition test suite after resolving current Amplifier sources.
  • Prior isolated cross-repository validation: 395 unique tests passed, 0 failed, 2 skipped because the validation filesystem keeps Unicode spellings distinct. The focused Work suite passed 4 tests.
  • Real ordinary and managed tool schemas were observed. A bounded CLI/provider smoke verified exact successful calls to read_file, glob, bash, and grep.
  • Root, named-child, and self-child prompt construction passed at documented seams. Child activation/execution was mocked; initialized provider-driven child behavior and freeform model efficacy are not claimed.
  • Before publishing Work, Bash, Search, Filesystem, Tester, and Foundation were merged. Each runnable upstream CI workflow was settled successfully; Search has no runnable CI workflow and its CLA policy check passed.

Breaking changes

None. Runtime enforcement, permissions, defaults, and retry policy are unchanged.

Generated with Amplifier

Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
@bkrabach
Brian Krabach (bkrabach) merged commit c7c5872 into main Oct 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants