Suggested test: copilot/close-issue-auto-close-footer

## Motivation

Link to the gh-aw PR: github/gh-aw#47584 — fix: add generated footer to close_issue comment body

Comments posted when auto-closing an issue via `close_older_issues: true` were missing the standard workflow footer (run URL, workflow name, tracker ID). All other safe-output message types already included this footer.

## Proposed test

- **Workflow file**: `test-copilot-close-issue-auto-close-footer.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `create-issue` (with `close_older_issues: true`) or `close-issue`
- **Variant**: standard

## Minimal test prompt sketch

Instruct the agent to close an existing fixture issue (or create one first and then close it via `close_older_issues`). After the run, assert that the comment posted on the closed issue contains the standard generated footer (run URL / workflow name / tracker ID pattern), verifying the fix in #47584 holds.

## New fixtures or secrets needed

None. Uses existing `githubnext/gh-aw-test` repo. The harness can inspect issue comments via `gh issue view` to confirm footer presence.

## Notes

Regression test for github/gh-aw#47584. The `close-pull-request` safe output was already emitting the footer correctly; this test confirms `close_issue` is now at parity. Could be combined with the `close-issue` test, but keeping it focused on the footer content assertion is more explicit.

> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/30081887837) · sonnet46 20.1 AIC · ⌖ 5.75 AIC · ⊞ 6.1K · [◷](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-close-issue-auto-close-footer.md and the existing githubnext/gh-aw-test fixtures. Run the workflow with workflow_dispatch using the copilot engine and the close-issue safe output, then inspect the closed issue with gh issue view. Done means the comment contains the standard generated footer with the run URL, workflow name, and tracker ID.

Written by the indexing model from the issue text.