Skip to content

docs(registry): group each role's model and effort anchors in variables examples - #44

Merged
lukeaus merged 1 commit into
mainfrom
docs/variables-nested-effort-anchors
Sep 17, 2026
Merged

lukeaus merged 1 commit into
mainfrom
docs/variables-nested-effort-anchors

Conversation

@lukeaus

@lukeaus lukeaus commented Sep 17, 2026

Copy link
Copy Markdown
Owner

Replaces the flat sibling effort anchors with one grouped anchor pair per role, so a role's model and its reasoning effort sit together:

variables:
  worker:
    model: &worker_model
      provider: openrouter
      model: gpt-5-mini
    effort: &worker_effort max

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 because variables is 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.

simple has no effort anchor: Factory stores no effort for subagent fields, which are model-only.

No source changes. Fixture, docs, and the registry alias test updated.

@lukeaus
lukeaus merged commit c5d61f4 into main Sep 17, 2026
8 checks passed
@lukeaus
lukeaus deleted the docs/variables-nested-effort-anchors branch September 17, 2026 06:50
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.

1 participant