feat(bundles): promote behavioral-anchor to published 'anchors' bundle#259
Merged
Conversation
Copy the experimental experiments/behavioral-anchor/ bundle into a published bundle at bundles/anchors/ and rename its namespace behavioral-anchor -> anchors (bundle.name, the six agent includes, and the @anchors:context/system.md mention). The entrypoint is renamed behavioral-anchor.md -> bundle.md. The original experiments/behavioral-anchor/ is intentionally left in place (copied, not moved). The bundle is self-contained: all module/behavior sources are full git+https URLs, so it has no foundation: namespace dependency. PR 1 of 2. The companion amplifier-app-cli PR registers `anchors` as a well-known bundle and makes it the CLI's default (last-resort fallback), referencing git+https://github.com/microsoft/amplifier-foundation@main#subdirectory=bundles/anchors/bundle.md This PR must merge first. foundation is not deleted or modified. 🤖 Generated with [Amplifier](https://github.com/microsoft/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
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.
What
Promotes the experimental
experiments/behavioral-anchor/bundle into a published bundle atbundles/anchors/, renaming the namespacebehavioral-anchor→anchors.experiments/behavioral-anchor/is intentionally left in place (constraint: experiment preserved).bundle.name: anchors; the six agent includes (anchors:explorer/architect/builder/debugger/git-ops/researcher); the context@anchors:context/system.md.behavioral-anchor.md→bundle.md.The bundle is self-contained: every module/behavior/tool source is a full
git+https://…@mainURL, so it has nofoundation:namespace dependency.amplifier-foundationitself is untouched.Why
Make a lean, principle-driven bundle available as the CLI's default for new sessions — without deleting
foundationor the experiment, and without affecting existing users.PR 1 of 2 — merge this first
The companion PR in amplifier-app-cli registers
anchorsas a well-known bundle and flips the CLI's last-resort default fallbackfoundation→anchors, referencing:git+https://github.com/microsoft/amplifier-foundation@main#subdirectory=bundles/anchors/bundle.mdBecause the app-cli PR pins
@main, it becomes correct the moment this merges.Testing
Validated in a Digital Twin Universe across new-install, existing-foundation-user, other-bundle-user, switch-to-foundation, and session-resume scenarios (see companion PR).
🤖 Generated with Amplifier