Suggested test: copilot/jobs-setup-steps-checkout-permission

## Motivation

Link to the gh-aw PR: github/gh-aw#60137 — "Preserve contents permission for built-in job setup checkouts". Recompiling workflows previously dropped `contents: read` from `safe_outputs`/`conclusion` built-in jobs when `actions/checkout` was declared in job-level `setup-steps:`, breaking private-repo checkouts in those jobs.

## Proposed test

- **Workflow file**: `test-copilot-jobs-setup-steps-checkout-permission.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `create-issue`
- **Variant**: standard

## Minimal test prompt sketch

Declare `jobs.safe_outputs.setup-steps` with an `actions/checkout@v4` step plus an explicit `id-token: write` permission (pattern similar to the custom `setup` job in `test-copilot-restore-memory-custom-job.md`). Agent creates an issue confirming the run completed.

## New fixtures or secrets needed

None.

## Notes

No existing test exercises `jobs..setup-steps` with checkout to trigger the permission-inference path. Distinct from open suggestion #11354 (`safe-outputs.steps`, a different mechanism). Whether e2e.sh should also grep the lock file for `contents: read` needs triage.

> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/34580092090) · copilot · auto · 96 AIC · ⌖ 7.08 AIC · ⊞ 8.4K · [◷](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 test-copilot-restore-memory-custom-job.md for the setup-steps pattern, then create test-copilot-jobs-setup-steps-checkout-permission.md using the stated workflow settings and prompt. Run the relevant copilot end-to-end test and inspect e2e.sh to decide whether the lock file should be checked. Done means the test confirms completion and covers the checkout permission path.

Written by the indexing model from the issue text.