Suggested test: copilot/workflow-run-conclusion-trigger

## Motivation

github/gh-aw#56743 — Allow `conclusion` in `on.workflow_run` frontmatter schema, letting workflows filter which run conclusions (success/failure/etc.) trigger the agentic workflow.

## Proposed test

- **Workflow file**: `test-copilot-workflow-run-conclusion.md`
- **Trigger**: `on.workflow_run` with a `conclusion` filter (e.g. `success`), plus `workflow_dispatch` as a secondary trigger so the harness can exercise it directly
- **Engine**: copilot
- **Safe output**: `create-issue`
- **Variant**: standard

## Minimal test prompt sketch

Configure `on.workflow_run.conclusion: success` watching a small upstream workflow (or itself), and on trigger have the agent create an issue confirming it fired only for the matching conclusion. Since the harness drives tests via `workflow_dispatch`, include a `workflow_dispatch` entry alongside `workflow_run` so `e2e.sh` can invoke it directly and assert compilation accepts the new `conclusion` field.

## New fixtures or secrets needed

None — can reuse an existing lightweight workflow in this repo as the watched trigger source.

## Notes

No existing test exercises `on.workflow_run` at all, so this also adds baseline coverage for that trigger type, not just the new `conclusion` field. Feasibility of full runtime exercise (actually observing a `workflow_run` completion) may be limited under `--workflow-dispatch-only` CI mode — worth confirming compile-only coverage is acceptable before promoting to a PR.

> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/33243402461) · auto · 27.6 AIC · ⌖ 1.9 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)

Start with the proposed test file, test-copilot-workflow-run-conclusion.md, and inspect e2e.sh to understand how workflow_dispatch tests are compiled and asserted. Reuse an existing lightweight workflow as the watched source, include both triggers, and confirm the harness accepts the conclusion field and validates compilation without requiring new secrets.

Written by the indexing model from the issue text.