Suggested test: copilot/create-issue-group-by-day

## Motivation

Link to the gh-aw PR: github/gh-aw#44830 — Consolidate `pr-sous-chef` run reports into a daily rolling issue thread; introduces `group-by-day: true` on `safe-outputs.create-issue`

## Proposed test

- **Workflow file**: `test-copilot-create-issue-group-by-day.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `create-issue`
- **Variant**: standard

## Minimal test prompt sketch

Dispatch a workflow that uses `group-by-day: true` under `safe-outputs.create-issue`. Run the workflow twice in the same day and verify the second run appends to (or updates) the existing issue rather than creating a new one. A single run just verifies the compiled `group_by_day: true` config reaches the runtime without error.

## New fixtures or secrets needed

None.

## Notes

No existing test covers the `group-by-day` dedup feature on `create-issue`. The `test-copilot-create-issue.md` test uses a plain create without this flag. Verifying idempotent daily grouping may require running the test twice in sequence — the E2E harness would need a two-dispatch variant or a check that the issue count does not grow.

> [!WARNING]
>
> Firewall blocked 1 domain
>
> The following domain was blocked by the firewall during workflow execution:
>
> - `awmgmcpg`
>> To allow these domains, add them to the `network.allowed` list in your workflow frontmatter:
>
> ```yaml
> network:
> allowed:
> - defaults
> - "awmgmcpg"
> ```
>
> See [Network Configuration](https://github.github.com/gh-aw/reference/network/) for more information.
>
>

> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/29147036798) · 27 AIC · ⌖ 5.64 AIC · ⊞ 5.6K · [◷](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 existing test-copilot-create-issue.md workflow and compare it with the proposed test-copilot-create-issue-group-by-day.md fixture. Run or inspect the workflow_dispatch setup for the copilot create-issue path, then verify that group-by-day: true reaches the compiled configuration and that two same-day runs append to or update one issue rather than creating another.

Written by the indexing model from the issue text.