Suggested test: copilot/add-labels-issue-intents

## Motivation

Link to the gh-aw PR: github/gh-aw#46589 — Fix `add_labels` strict-mode narrowing for CJS lint/typecheck

The fix corrects a TypeScript narrowing bug in the `add_labels` action when `issue-intents: true` is set and the agent emits structured label objects (with `rationale` and `confidence`). The only existing `add-labels` test (`test-copilot-add-labels.md`) uses plain string labels without `issue-intents`, so the strict structured-label path has no E2E regression coverage.

## Proposed test

- **Workflow file**: `test-copilot-issue-intents-add-labels.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `add-labels`
- **Variant**: standard

## Minimal test prompt sketch

With `issue-intents: true` enabled, instruct the agent to add a label (e.g. `copilot-safe-output-label-test`) to a specific issue in the repository. The safe-output handler must receive a structured label object with `rationale` and `confidence` fields and apply it correctly, exercising the repaired strict-mode narrowing path.

## New fixtures or secrets needed

None. The label `copilot-safe-output-label-test` already exists in `githubnext/gh-aw-test` (used by the existing `test-copilot-add-labels` test). A known open test issue number can be hard-coded or passed as a workflow input.

## Notes

The existing `test-copilot-issue-intents.md` only exercises `create-issue` with `issue-intents: true`; this would be the first test combining `add-labels` + `issue-intents`. The bug was a silent TypeScript narrowing failure (CJS typecheck), so a passing E2E run demonstrates the full stack including the CJS compilation path.

> [!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/29731885541) · 25.4 AIC · ⌖ 5.44 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 by reading test-copilot-add-labels.md and test-copilot-issue-intents.md to compare the existing add-labels and issue-intents workflows. Create test-copilot-issue-intents-add-labels.md with the stated workflow_dispatch, copilot, add-labels, and standard settings, then run the E2E workflow against the existing test label and verify the structured-label path succeeds.

Written by the indexing model from the issue text.