Repository navigation
[awf-feature-surfacing] Surface model-routing and governance toolset guidance #68542
Closed as not planned
Description
Overview
The seven-day AWF spec/compiler review found two user-facing guidance gaps in recently changed capabilities. The compiler and schema accept the behavior, but two discoverable syntax references still give incomplete or incorrect instructions.
Key findings
- P2 — Model routing syntax:
.github/aw/syntax-engine.mdsaysengine.model-routing.allowed-modelsis required and implies it limits models the routed task may call. Since Model routing: make models.allowed/models.blocked the only request policy, and allowed-models optional router candidates #68495, it is an optional router candidate list (AWF v0.28.33+); onlymodels.allowedandmodels.blockedset the request policy. The same syntax entry omits theengine.model-provider: githubrequirement for routed Claude and Codex workflows enforced by Fail compilation for model-routed workflows that don't use GitHub Copilot inference #68080. - P2 — GitHub governance toolset: The
tools.github.toolsetsschema acceptsgovernanceafter Add governance and Copilot Automation tools to GitHub MCP mapping #67738, and.github/aw/syntax-tools-imports.mdlists it, but the Available list indocs/src/content/docs/reference/github-tools.mdomits it. The reference also lacks a short explanation of its custom property and ruleset tools and token permissions.
Evidence and current surfacing
pkg/parser/schemas/main_workflow_schema.jsonhasengine.model-routingrequired fieldsgoalandmodeonly, and describesallowed-modelsas optional router candidates. It includesgovernanceingithub_toolset_name.pkg/workflow/model_routing.goapplies routing policy and provider validation;pkg/workflow/data/github_toolsets_permissions.jsonmapsgovernanceto custom property and ruleset tools and their permission needs.docs/src/content/docs/reference/model-routing.mdcorrectly explains optional candidates, the AWF version boundary, request policy, and the GitHub provider requirement.docs/src/content/docs/reference/frontmatter.mdalso describes the candidate/policy distinction..github/aw/syntax-engine.md:97retains the stale required-field and request-limit wording.docs/src/content/docs/reference/github-tools.md:22has the incomplete toolset list.- Relevant changes: Model routing: make models.allowed/models.blocked the only request policy, and allowed-models optional router candidates #68495 (
63e2c65) and Fail compilation for model-routed workflows that don't use GitHub Copilot inference #68080 (70f8448) for routing; Add governance and Copilot Automation tools to GitHub MCP mapping #67738 for GitHub MCP toolsets.
Next actions
- P2: Update
.github/aw/syntax-engine.mdto callallowed-modelsoptional for AWF v0.28.33+, describe it as router candidates only, and point readers tomodels.allowed/models.blockedfor request policy. State that routed Claude and Codex must resolveengine.model-providertogithub. - P2: Update the GitHub tools reference's available-toolsets list and add a compact
governanceexample with the tool purposes and required token permissions, using the permission map as the source.
Generated by 🧭 Daily AWF Spec Compiler Surfacing Review · codex · gpt60 · 127.8 AIC · ⌖ 5.96 AIC · ⊞ 14.1K · ◷
- expires on Oct 20, 2026, 2:27 PM UTC-08:00
Activity
lpcox commentedon Oct 14, 2026
🔗 AWF tracking issue: github/gh-aw-firewall#9956
github-actions commentedon Oct 14, 2026
This issue is being closed as outdated. A newer issue has been created: #68861
View newer issue
This action was performed automatically by the
Daily AWF Spec Compiler Surfacing Reviewworkflow.