compiler: add implicit self-alias for provider-scoped model in AWF config

[Copilot]

The compiler accepts provider-scoped model: values (e.g. copilot/gpt-5.6-sol) and emits a valid lock file, but the AWF api-proxy rejects them at runtime because it validates the requested model against keys of apiProxy.models — and alias keys cannot contain / (V-MAF-005), so a provider-scoped name can never appear as a key via normal frontmatter models: declarations.

Changes

• pkg/workflow/awf_config.go — In BuildAWFConfigJSON, when WorkflowData.Model is provider-scoped (contains /) and is not a runtime expression, add an implicit self-alias entry to apiProxy.models before writing the section:

  "copilot/gpt-5.6-sol": ["copilot/gpt-5.6-sol"]

  The original ModelMappings map is never mutated (a clone is created). Existing explicit mappings are not overwritten.

• pkg/workflow/awf_config_test.go — Five new subtests under TestBuildAWFConfigJSON_ProviderScopedModelImplicitSelfAlias covering: self-alias is injected for provider-scoped models; works when ModelMappings is nil; bare aliases are unaffected; runtime expressions are skipped; existing explicit mappings are preserved.

• Lock file recompile — All 266 workflows recompiled. Workflows already using provider-scoped models (e.g. ab-testing-advisor.md with model: copilot/gpt-5.4) now have the implicit self-alias in their generated AWF config.

• Fixes Provider-scoped engine.model compiles cleanly but is rejected by the bundled AWF at runtime #46306

[github-actions]

PR Triage

• Category: bug | Risk: low | Priority: low
• Score: 17/100 (impact 10 + urgency 5 + quality 2)
• Recommended action: defer
• Batch: wip-drafts

Note: Draft, no diff yet (still generating)

Generated by 🔧 PR Triage Agent · auto · 48.9 AIC · ⌖ 6.24 AIC · ⊞ 7.9K · ◷