docs(registry): group each role's model and effort anchors in variables examples - #44
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.
Replaces the flat sibling effort anchors with one grouped anchor pair per role, so a role's model and its reasoning effort sit together:
Consumption is unchanged: each slot still takes a plain alias, because an alias copies a whole node and
defaults.<role>requires exactly{provider, model}while effort slots require a scalar. Grouping is legal becausevariablesis opaque (the schema types it as a plain object and the parser only checks that it is a mapping); YAML resolves aliases before the parser runs, so nothing reads the bucket's shape.simplehas no effort anchor: Factory stores no effort forsubagentfields, which are model-only.No source changes. Fixture, docs, and the registry alias test updated.