Suggested test: copilot/sandbox-token-steering-opt-out

## Motivation

github/gh-aw#50122 — Add AWF token steering frontmatter opt-out (`sandbox.agent.token-steering: false`)

## Proposed test

- **Workflow file**: `test-copilot-sandbox-token-steering.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `create-issue` (or `noop`) — the frontmatter field itself is the thing under test, not a specific safe output
- **Variant**: standard

## Minimal test prompt sketch

Set `sandbox.agent.token-steering: false` in frontmatter and confirm the workflow compiles and runs, emitting `apiProxy.enableTokenSteering: false` in the generated AWF config. Prompt body can be trivial (e.g. emit a noop message) since the interesting assertion is on the compiled lock file / AWF config, not agent behavior.

## New fixtures or secrets needed

None. Uses existing `githubnext/gh-aw-test` fixture.

## Notes

This is a compiler/config-emission feature more than a runtime behavior difference, so the e2e assertion may need to inspect the generated `.lock.yml` for `enableTokenSteering: false` rather than relying purely on safe-output content. Not present in `existing-tests.json` or `open-suggestions.json`.

> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/30896082598) · auto · 36.6 AIC · ⌖ 3.13 AIC · ⊞ 8.3K · [◷](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)

Create `test-copilot-sandbox-token-steering.md` with a `workflow_dispatch` trigger, the copilot engine, the standard variant, and the existing `githubnext/gh-aw-test` fixture. Run the workflow with `sandbox.agent.token-steering: false`, then inspect the generated `.lock.yml` or AWF config to confirm `apiProxy.enableTokenSteering: false`.

Written by the indexing model from the issue text.