[plan] EP006: Fix Smoke Multi PR add_comment to use item_number instead of target=triggering

[github-actions]

Context

From Safe Output Health Report - 2026-03-22 (EP006 RECURRING — 8th+ occurrence across 6 days since 2026-02-25).

The Smoke Multi PR workflow creates PRs and then asks the agent to add a comment. The agent generates add_comment with target=triggering, but when the workflow is triggered by workflow_dispatch or schedule, there is no triggering issue or PR. The handler correctly rejects this but marks it as a failure rather than a skip, inflating the failure rate.

Failing workflow run: §23392726144

Objective

Update the Smoke Multi PR workflow prompt so the agent references the newly-created PR by number rather than using target=triggering. This eliminates the context mismatch entirely.

Files to Modify

• .github/workflows/smoke-multi-pr.md — workflow prompt (96 lines)

Approach

In the agent prompt (around lines 47–95 of smoke-multi-pr.md), find the section that currently instructs the agent to add a comment reporting results. Update it to:

1. Explicitly instruct the agent: "Do NOT use target: triggering for add_comment. Instead, reference the pull request you just created by its PR number using item_number."
2. Add an example like:

   When reporting results via add_comment, use the PR number of the first created PR:
   item_number: <PR number from create_pull_request output>
   

3. Alternatively, if add_comment is only used to confirm results that are already visible in the PR itself, consider removing the add_comment instruction from the prompt and relying on the PR description alone.

After editing the .md file, run make recompile to regenerate the .lock.yml file.

Acceptance Criteria

• The Smoke Multi PR workflow no longer produces add_comment with target=triggering
• No EP006 failures in Smoke Multi PR for 5 consecutive runs triggered by workflow_dispatch
• The recompiled .lock.yml is committed alongside the .md change
• make recompile completes without errors

Notes

• The Smoke Multi PR workflow itself succeeds (PRs are created correctly) — only the comment step fails. The fix is purely a prompt improvement.
• Do NOT change the add_comment handler behavior — the handler is correct to reject target=triggering in dispatch context. Fix the prompt instead.

Generated by Plan Command for issue #discussion #22230 · ◷

• expires on Mar 24, 2026, 4:46 AM UTC