Fix agent skipping assign-to-agent call in security-alert-burndown workflow

[Copilot]

Problem

In run 21454338976, the agent created parent issue #12356 but never called assign_to_agent. The conditional step contains(needs.agent.outputs.output_types, 'assign_to_agent') skipped because the agent didn't emit that output type.

Root cause: Workflow instructions had three required actions scattered across 100 lines with a 50-line issue template interrupting the sequence:

• Action 1: Create issue (lines 109-124)
• Action 2: Add to project (lines 126-147)
• Issue template (lines 149-188)
• Action 3: Assign to agent (lines 190-197)

Changes

Restructured Step 4 to make the three-action sequence explicit and uninterruptible:

• Sequential numbering: Changed header to "Step 4: Create parent issue and assign work" with numbered list: "1. Create the parent tracking issue, 2. Add the issue to the project board, 3. Assign the issue to the Copilot agent"
• Action labels: Renamed subsections from descriptive headers to "Action 1", "Action 2", "Action 3"
• Issue number reminder: Added note after Action 1 to store the returned issue number for use in Actions 2 and 3
• Critical warning: Added **CRITICAL**: You must call all three tools (create_issue, update_project, assign_to_agent) in sequence
• Template relocation: Moved 50-line issue body template after all actions to prevent interrupting the sequence

The workflow structure remains unchanged—only the embedded prompt text was updated. The conditional logic contains(needs.agent.outputs.output_types, 'assign_to_agent') is correct; the issue was agent behavior, not the conditional.

File changes

• .github/workflows/security-alert-burndown.md - Restructured Step 4 instructions (+8 lines, -14 lines)
• .github/workflows/security-alert-burndown.lock.yml - Recompiled with updated embedded prompt

Original prompt

Analyze this run: https://github.com/githubnext/gh-aw/actions/runs/21454338976/job/61791632772
The parent issue was created, but the assign-to-agent step was skipped when it should have assigned the agent.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[mnkiefer]

@copilot recompile workflow

[Copilot]

@copilot recompile workflow

Workflow recompiled successfully. No changes were needed - the lock file was already up to date with the markdown changes.