Suggested test: copilot/report-failed-jobs-config

## Motivation

github/gh-aw#50076 — safe-output-integrator found two `SafeOutputsConfig` types with no fixture coverage: `data` and `report-failed-jobs`. New Go unit tests were added upstream (`compiler_safe_outputs_config_test.go`), but there is no live E2E workflow exercising either in `gh-aw-test`.

## Proposed test

- **Workflow file**: `test-copilot-report-failed-jobs.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `report-failed-jobs: false` combined with `create-issue`
- **Variant**: standard

## Minimal test prompt sketch

Configure `safe-outputs.report-failed-jobs: false` alongside a `create-issue` safe output with a `samples:` block, and have the agent create an issue as usual — the point of the test is to confirm the config parses and compiles without the report-failed-jobs collector step firing.

## New fixtures or secrets needed

None.

## Notes

`data: true` mode is a separate, more speculative capability (raw structured data safe-output) that may warrant its own test once its purpose is clearer — suggesting `report-failed-jobs` first since it's simpler to assert (presence/absence of a compiled step). 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)

Start by comparing existing Copilot E2E workflows and checking existing-tests.json and open-suggestions.json for conventions. Add test-copilot-report-failed-jobs.md with a workflow_dispatch trigger, the standard Copilot engine, report-failed-jobs: false, and a create-issue safe output with samples. Done means the workflow compiles and the report-failed-jobs collector step is absent.

Written by the indexing model from the issue text.