feat(bundles): register 'anchors-amp-dev' (amplifier-dev drop-in variant) - #273
Merged
Merged
Conversation
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.
Summary
Registers
anchors-amp-devas a new, evaluated bundle alongsideamplifier-dev. This is a side-by-side registration only — no default changes. Both bundles coexist; users opt-in toanchors-amp-devby name.What is anchors-amp-dev?
A mechanical promotion of the experiment
experiments/behavioral-anchor-amplifier-devinto a registered bundle. The experiment was evaluated as a drop-in replacement foramplifier-devacross ~140 DTU eval runs (Opus-4.8 + GPT-5.5 sweeps) and reached a drop-in verdict.How promotion was done
experiments/behavioral-anchor-amplifier-dev/→bundles/anchors-amp-dev/behavioral-anchor-amplifier-dev.md→bundle.mdbundle.name: anchors-amp-devbehavioral-anchor-amplifier-dev:namespace refs →anchors-amp-dev:foundation:session-analystverbatim — ensures the registered bundle stays byte-faithful to the evaluated artifactThe original experiment folder remains intact; this is promotion, not a move.
Evaluation provenance
amplifier-devfoundation:session-analystwas included in all eval runs and resolved correctly; stripping it would make the registered bundle differ from what was testedIntegration
Side-by-side with
amplifier-devandamplifier-foundation— no defaults changed. Users can run:Follows the precedent of #259 (anchors bundle registration).
Companion PR
Requires companion app-cli PR #230 (microsoft/amplifier-app-cli#230) which registers
anchors-amp-devin WELL_KNOWN_BUNDLES. That PR depends on this one — merge this first.