Suggested test: copilot/api-proxy-http-scheme-preservation

## Motivation

github/gh-aw#58608 — Preserve explicit `(redacted) schemes in AWF API proxy targets (previously compiled to bare hosts, causing AWF to default to HTTPS/443).

## Proposed test

- **Workflow file**: `test-copilot-api-proxy-http-scheme.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `create-issue`
- **Variant**: standard (requires AWF v0.28.13+; may need `nosandbox`/custom-engine frontmatter depending on how apiProxy targets are configured)

## Minimal test prompt sketch

Configure an engine/network `apiProxy` target with an explicit `(redacted) host and have the agent make a simple request that would fail if the scheme were silently upgraded to HTTPS; then have it report success via `create-issue`.

## New fixtures or secrets needed

None expected, but need to confirm the exact frontmatter surface for declaring `apiProxy.targets` (may require a mock/echo HTTP endpoint reachable from the sandbox, which is not currently available as a fixture in this repo — flag if so).

## Notes

Distinct from existing `network-engine-domain-explicit-opt-in` (open #12914) and `network-npm-registry-allowlist` (open #13051), which cover allowlisting, not scheme preservation. Feasibility of a testable HTTP-only endpoint fixture should be confirmed before converting to a PR.

> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/33955548499) · copilot · auto · 35.2 AIC · ⌖ 8.46 AIC · ⊞ 8.8K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-test+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-test%2Fsuggest-new-e2e-tests%22&type=issues)

Start with the proposed test file, test-copilot-api-proxy-http-scheme.md, and inspect existing network and Copilot workflow tests such as network-engine-domain-explicit-opt-in and network-npm-registry-allowlist. Confirm the frontmatter syntax for apiProxy.targets and whether an HTTP-only endpoint fixture is available. Done means a workflow_dispatch test using an explicit HTTP target reports success through create-issue without requiring new secrets.

Written by the indexing model from the issue text.