Update security-alert-burndown campaign project URL to 132

[Copilot]

Campaign spec was pointing to wrong GitHub project (130 instead of 132).

Changes

• Updated project-url in .github/workflows/security-alert-burndown.campaign.md from projects/130 to projects/132
• Recompiled workflow to propagate URL change throughout lock file (10 references updated)

Campaign orchestrator will now track work items in the correct project board.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Campaign: Security Alert Burndown</issue_title>
<issue_description>Write a campaign that burns down the code security alerts backlog. Focus on file write issues first, cluster alerts if possible (up to 3), and add comments generated code for fixes. Use Claude for codegen, copilot for campaign manager.

---

Campaign setup status

Status: Ready for PR review

What just happened

• Created Project: https://github.com/orgs/githubnext/projects/132 (will have permanent URL after merge)
• Created standard fields (status, campaign_id, worker_workflow, repository, priority, size, start_date, end_date) with required single-select options
• Created views: Campaign Roadmap (roadmap), Task Tracker (table), Progress Board (board)
• Campaign spec already exists at .github/workflows/security-alert-burndown.campaign.md
• Selected workflows: code-scanning-fixer, security-fix-pr

What happens next

1. Copilot Coding Agent will open a pull request to update the campaign spec with the new project URL.
2. You review the PR and merge it.
3. After merge, run the orchestrator workflow from the Actions tab to begin campaign execution.

Copilot Coding Agent handoff

• Campaign ID: security-alert-burndown
• Project URL: https://github.com/orgs/githubnext/projects/132 (update in campaign spec after getting permanent URL)
• Workflows: code-scanning-fixer, security-fix-pr

Instructions for Copilot Coding Agent:

The campaign spec already exists at .github/workflows/security-alert-burndown.campaign.md. You need to:

1. Get the permanent project URL by inspecting the project that was just created (temporary ID: https://github.com/orgs/githubnext/projects/132)
2. Update line 5 of .github/workflows/security-alert-burndown.campaign.md with the correct permanent project URL (format: https://github.com/orgs/githubnext/projects/XXX)
3. Run compilation:

   gh aw compile

4. Commit the updated files:
   • .github/workflows/security-alert-burndown.campaign.md (with new project URL)
   • .github/workflows/security-alert-burndown.campaign.g.md (generated)
   • .github/workflows/security-alert-burndown.campaign.lock.yml (compiled)
5. Create a pull request with these changes and link it back to this issue

Acceptance checklist:

• ✅ Project URL updated in campaign spec
• ✅ gh aw compile succeeds
• ✅ Lock file updated with new project URL
• ✅ PR opened and linked to issue githubnext/gh-aw#11251

Documentation

• [Getting started with campaigns]((redacted)
• [Campaign flow & lifecycle]((redacted)
• [Campaign spec reference]((redacted)

Ahoy! This treasure was crafted by 🏴‍☠️ Agentic Campaign Generator</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes githubnext/gh-aw#11251

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.