[docs] auth: auth: correct stale host-routing wiring status in awf-config-spec.md - #9034
Conversation
PR #8985 (host-side routing bootstrap) merged 2026-09-25 and is fully wired into src/cli-workflow.ts and src/routing/bootstrap.ts on main. The spec still described host staging/validation as not-yet-merged; update it to reflect that both the proxy-side (PR #8966) and host-side (PR #8985) halves of task-level routing are shipped. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The unsupported-configuration list omits the rejected --keep-containers option.
Review effort: Balanced
Findings: 1
Open (1)
What changed in this PR
Updates the model-routing specification to reflect shipped host-side routing support.
Changes:
- Documents routing input staging, validation, readiness waiting, and exit code
78. - Updates PR #8985’s status from pending to shipped.
| File | Description |
|---|---|
docs/awf-config-spec.md |
Corrects task-level routing workflow documentation. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
The host workflow now validates `apiProxy.routing` input and handles unsupported configurations, improving error handling. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
✅ Copilot review passed with no inline comments. @github-actions[bot] Add the |
Documentation PreviewDocumentation has been built for this PR. To view locally:
Built from commit bd0a4e9 |
|
@copilot merge main and resolve conflicts |
…ing-shipped-20260926-3148511e369c6391 # Conflicts: # docs/awf-config-spec.md Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
Merged current |

Summary
src/services/api-proxy-env-config.ts,src/cli-workflow.ts,src/routing/bootstrap.ts; PRs Activate task-level model routing in the API proxy server #8966 (merged, proxy-side routing wiring), Wire task-level model routing into the host workflow #8985 (merged 2026-09-25, host-side routing bootstrap), Gate task-level model routing behind experimental opt-in #9033 (open — gates routing behindexperimental.modelRouting, not yet shipped); issue fix: isolate Actions OIDC from agent container #6894 (closed, merged) and Ensure HTTP MCP GitHub OIDC bypasses the AWF agent credential boundary gh-aw#50053 (closed, resolved by Enforce runner→gateway OIDC path and prevent AWF agent exposure for HTTP MCP auth gh-aw#50054, merged) — both confirmed shipped, no stale doc claims found referencing them. Also confirmed prior updater PRs [docs] auth: auth: correct stale GCP OIDC agent-routing claim in auth-matrix.md #8953 and [docs] auth: auth: correct stale task-level routing wiring status in awf-config-spec.md #8993 already landed their corrections and remain accurate.docs/awf-config-spec.mdstill described the host workflow as not yet staging or validatingapiProxy.routinginput, citing PR Wire task-level model routing into the host workflow #8985 as "open, not yet merged." That PR merged on 2026-09-25 and its host routing bootstrap (src/routing/bootstrap.ts: private per-run routing directory, host-mode rejection, digest-pin enforcement,selection.jsonwait-for-ready, exit code78on failure) is fully wired intosrc/cli-workflow.ts(prepareRouting,waitForRoutingSelection,verifyRoutingCompletion). The doc's "does not yet produce a working end-to-end routed run" caveat is no longer accurate.main. PR Gate task-level model routing behind experimental opt-in #9033 (gating routing behind anexperimental.modelRoutingopt-in) is still open and unmerged — it was not referenced by the existing doc text and does not need a caveat added, since the corrected text describes only shipped behavior.Documentation Changes
selection.jsonbefore starting the agent; a routing failure from either side surfaces as host exit code78.Validation
src/routing/bootstrap.ts(stageRoutingConversation,RoutingFailureExitErrorwithexitCode = 78,ROUTING_SELECTION_TIMEOUT_MS, digest-pin check viaisDigestPinnedImageReference),src/cli-workflow.ts(dependencies.prepareRouting,waitForRoutingSelection,verifyRoutingCompletionall invoked in the run flow),src/services/api-proxy-env-config.ts(buildModelRoutingEnvnow requiresconfig.modelRoutingBootstrapand throwsMODEL_ROUTING_NOT_STAGED_MESSAGEif routing is configured without host staging having run).[PR #8966](...)/[PR #8985](...)links render correctly and match the file's existing convention for citing merged PRs; surrounding code fence and table were left untouched.sk-,ghp_,gho_,Authorization:, bearer-shaped strings) — none present; only prose and existing PR URLs were changed.Sources
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
msfeed25.pkgs.visualstudio.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.