Suggested test: copilot/steer

## Motivation

github/gh-aw#57763 — added `pkg/cli/workflows/test-copilot-steer.md` fixture upstream for the `steer` safe output, but `githubnext/gh-aw-test` has no equivalent `.github/workflows/test-copilot-steer.md`. This is a real safe-output feature (documented, experimental) with zero E2E regression coverage here.

## Proposed test

- **Workflow file**: `test-copilot-steer.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `steer` (creates a run-scoped steering issue during activation; closes it on completion)
- **Variant**: standard

## Minimal test prompt sketch

Set `safe-outputs: { steer: true }` with `permissions: { issues: read }` at top level (required by the compiler for steer). Prompt the agent to do a trivial task (e.g. wait briefly) while the harness verifies a steering issue is created and then closed/updated on run completion.

## New fixtures or secrets needed

None — uses existing repo issue permissions.

## Notes

Open question: `e2e.sh`'s dispatch-and-validate case list (around line 3559) does not include `*"steer"*`, so it would currently fall through to the generic issue/command-triggered branch, which expects a different flow. `e2e.sh` likely needs a new case branch to validate steering-issue creation/closure before this test can pass reliably. Flagging as an issue rather than a PR because of this harness-side open question.

> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/33609783863) · copilot · auto · 83.2 AIC · ⌖ 8.02 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 upstream-inspired .github/workflows/test-copilot-steer.md fixture requirements and inspect the dispatch-and-validate cases in e2e.sh around line 3559. Run the existing E2E harness to understand its generic issue flow, then confirm the steer-specific path creates a run-scoped steering issue and closes or updates it on completion. Done means the workflow dispatch passes with no new secrets and validates that lifecycle.

Written by the indexing model from the issue text.