Recompile agentic-labeler.lock.yml (PR #35540 follow-up)

[PureWeen]

Note

Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!

Description

Follow-up to #35540. That PR fixed the add-labels truncation bug by changing the source .md from max: 1 to max: 10, but did not regenerate the compiled .lock.yml. The deployed workflow on main therefore still embeds the old config and continues to silently drop all but one label per labeler run.

Running gh aw compile .github/workflows/agentic-labeler.md locally produces this 17-line diff in the lock file. The substantive changes are:

• frontmatter_hash updated to match the new .md source (so the lock file no longer fails the ERR_CONFIG: Lock file outdated check on every dispatch)
• safe-outputs config.json now emits {"add_labels":{"max":10}} (was {"add_labels":{"max":1}})
• the agent system prompt now declares add_labels(max:10), so the orchestrator knows it can return multiple labels in one call
• heredoc delimiters rotate as expected on every recompile

No behaviour changes beyond what #35540 already intended. This is purely the missing gh aw compile output.

Verification

1. Before this PR: every gh workflow run agentic-labeler.lock.yml dispatch fails with ERR_CONFIG: Lock file ... is outdated! The workflow file ... frontmatter has changed. (confirmed across 26 attempted backfill dispatches on the affected items in Fix agentic-labeler truncating labels to 1 per call #35540 audit).
2. With this PR locally, git diff shows only the lock file changed; no .md modifications.
3. After merge, dispatching the workflow once via gh workflow run agentic-labeler.lock.yml --repo dotnet/maui --ref main -f issue_number=<N> against an affected item should now successfully apply multiple area-* + platform/* labels in a single run (matching Fix agentic-labeler truncating labels to 1 per call #35540 intent).

Why this happened

PR #35540 was a documentation-style line-edit on the source .md and the author appears to have skipped the mandatory gh aw compile step. The repo currently has no CI check that recompiles the lock file and rejects out-of-sync commits — adding such a guard is a separate follow-up.

The misleading guidance in ~/.agents/skills/gh-aw-guide (which contributed to the original max: 1 bug) is being reviewed in parallel via a multi-model audit — fixes will land in a separate PR against that skill repo.

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.sh | bash -s -- 35549

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 35549"