`http://` API targets: scheme stripped from `apiProxy.targets.<provider>.host`, defeating AWF v0.28.13 HTTP support

[golivax]

Summary

When an engine env base URL uses an explicit http:// scheme, gh-aw strips the scheme when generating the AWF apiProxy.targets.<provider>.host value in the compiled lock. The emitted target is a bare hostname, so AWF's api-proxy (per github/gh-aw-firewall#7868 / github/gh-aw-firewall#7862, shipped in AWF v0.28.13) treats it as HTTPS and dials :443. This reintroduces the exact 502 / TCP_DENIED failure that the firewall fix was meant to resolve.

Reproduction

Compile with gh aw v0.88.2 (also reproduces on current main):

network:
  allowed: [defaults]
engine:
  id: claude
  env:
    ANTHROPIC_BASE_URL: "http://gateway.example.com"
    ANTHROPIC_API_KEY: ${{ secrets.MY_ANTHROPIC_KEY }}

Generated lock contains:

"targets":{"anthropic":{"host":"gateway.example.com"}}

Expected (to honor the firewall fix):

"targets":{"anthropic":{"host":"http://gateway.example.com"}}

The agent-container env ANTHROPIC_BASE_URL keeps http:// correctly; only the proxy target loses it. The same applies to OPENAI_BASE_URL (codex) and GEMINI_API_BASE_URL (gemini).

Root cause

extractAPITargetHost() in pkg/workflow/engine_api_targets.go unconditionally strips ://…. Its result is written into AWFAPITargetConfig{Host} in pkg/workflow/awf_config_build.go for openai/anthropic (and via GetGeminiAPITarget() for gemini). AWF v0.28.13 expects the scheme embedded in the target value (--anthropic-api-target http://host); its normalizeApiTargetScheme() keeps http://<hostname> only for explicit-HTTP targets and a bare host still defaults to HTTPS/443.

Fix considerations

• The host written to apiProxy.targets.* should preserve an explicit http:// scheme (an https:// or bare value can stay bare, mirroring AWF's own normalization, so existing lock files are unchanged).
• extractAPITargetHost is also consumed by allowlist/audit logic (mergeAPITargetDomains, getEngineAPIHosts, GetCopilotAllowlistTargets) which needs the bare host — so the scheme should be preserved only on the proxy target host, not the allowlist entries (AWF strips it internally via stripTargetScheme()).
• Gate on AWF ≥ v0.28.13 (already the default) so workflows pinning an older AWF keep the bare host.
• Note for the copilot target: at AWF v0.28.13, containers/api-proxy/providers/copilot.js buildCopilotModelsRequest() still hardcodes https://${rawTarget}/models while deriveCopilotApiTarget() now returns http://<host>, so an http:// copilot target would yield a malformed https://http://host/models. The copilot target should stay bare until that is fixed on the firewall side.

A PR implementing the above is attached.

[golivax]

A fix is ready on a branch, but my account can't open a PR against this repo from a fork (CreatePullRequest is denied), so posting it here for a maintainer to adopt or cherry-pick:

• Branch: https://github.com/golivax/gh-aw/tree/fix/awf-http-api-target-scheme (commit f227c0aa90)
• Compare: main...golivax:gh-aw:fix/awf-http-api-target-scheme

What it does

• Adds extractAPIProxyTargetHost() (sibling of extractAPITargetHost()) used only for the apiProxy.targets.<provider>.host value: an explicit http:// scheme is kept; https:// and bare values still return the bare host, mirroring AWF's own normalizeApiTarget(), so existing lock files are byte-identical.
• Adds GetGeminiAPIProxyTarget() for gemini; GetGeminiAPITarget() and all allowlist/audit consumers (mergeAPITargetDomains, getEngineAPIHosts, GetCopilotAllowlistTargets) are untouched and still get bare hostnames (tests assert this).
• Version gate constants.AWFAPIProxyHTTPTargetMinVersion = "v0.28.13" + awfSupportsAPIProxyHTTPTargets() following the existing awfSupports<X> pattern; workflows pinning an older AWF keep the bare host and log a Skipping http:// scheme … requires at least v0.28.13 line. The default is already v0.28.13, so the fix is active out of the box.
• Copilot target intentionally left bare: at AWF v0.28.13, containers/api-proxy/providers/copilot.js buildCopilotModelsRequest() still builds https://${rawTarget}/models while deriveCopilotApiTarget() now returns http://<host>, so an http:// copilot target would yield https://http://host/models. Once that's fixed on the firewall side it's a one-line swap in BuildAWFConfigJSON. This also keeps daily-byok-ollama-test.lock.yml unchanged (verified by recompiling it: no diff).
• Docs paragraph in reference/engines.md, a .changeset patch entry, and the new helpers registered in engine_api_targets_file_organization_test.go.

Verification

Compiling the reproduction workflow above with a binary built from the branch now emits:

"targets":{"anthropic":{"host":"http://gateway.example.com"}}

• go test ./pkg/workflow/ ./pkg/constants/ — pass
• make test-unit — pass
• golangci-lint run ./pkg/workflow/... ./pkg/constants/... — 0 issues
• No committed .lock.yml changes

New tests: TestExtractAPIProxyTargetHost, TestStripAPITargetScheme, TestGetGeminiAPIProxyTarget, TestAWFSupportsAPIProxyHTTPTargets, plus BuildAWFConfigJSON cases for anthropic/openai/gemini http:// targets, an https:// target staying bare, and the scheme being dropped when AWF is pinned to v0.28.12.