feat: add run-name to shim workflows for agent-prefixed Actions filtering

[rh-hemartin]

Problem

Both shim templates (shim-per-repo.yaml and shim-workflow-call.yaml) set name: fullsend with no run-name. Every workflow run in the Actions tab shows up as "fullsend" regardless of which agent stage it routes to. In repos with frequent activity, this makes it hard to find or filter runs for a specific agent (review, fix, triage, code, retro).

Proposed solution

Add a run-name field to the shim templates that includes the agent context derivable at trigger time. The shim cannot know the resolved stage (dispatch.yml determines that), but it has access to:

• github.event_name and github.event.action
• Comment body (for slash commands like /fs-review, /fs-fix)
• Label name (for ready-to-code, ready-for-review)
• Issue/PR number and title

A run-name expression could produce names like:

• fullsend: /fs-review #42 (slash command)
• fullsend: review opened #42 (PR opened)
• fullsend: labeled ready-to-code #15 (label trigger)

This would let users filter by agent name in the GitHub Actions UI.

Files to change

• internal/scaffold/fullsend-repo/templates/shim-per-repo.yaml
• internal/scaffold/fullsend-repo/templates/shim-workflow-call.yaml
• Existing enrolled repos would pick up the change on next scaffold sync

Notes

• run-name expressions can only reference github.* and inputs.* context; no arbitrary logic. Ternary-style format()/&&/|| chains can cover the main cases.
• The reusable-dispatch.yml and per-org dispatch.yml are workflow_call targets and don't support run-name (only top-level workflows do), so the shim is the right place for this.

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 12:59 PM UTC · Completed 1:02 PM UTC

Commit: 9fd9b5e · View workflow run →

[fullsend-ai-triage]

Triage Summary

Severity: low · Category: feature

Recommended approach

The run-name expression must use only github.* and inputs.* context. A chain of ternary-style format()/&&/|| expressions can cover the main cases:

• Slash commands (issue_comment): extract the command from github.event.comment.body (e.g., /fs-review)
• PR events (pull_request_target): github.event.action + PR number
• Label events: github.event.label.name + issue/PR number
• Issue events: github.event.action + issue number

Both template files need the change — they share the same name: fullsend pattern but route to different dispatch targets.

Proposed test case

# Verify run-name renders correctly for each trigger:
# issue_comment with /fs-review on #42  → "fullsend: /fs-review #42"
# pull_request_target opened #42        → "fullsend: opened #42"
# issues labeled ready-to-code #15      → "fullsend: labeled ready-to-code #15"
# issues opened #15                     → "fullsend: opened #15"

Notes

• Existing enrolled repos will pick up the change on next scaffold sync — no manual migration needed.
• Related issue Tighten fullsend.yaml shim label filter to match only dispatch-routable labels #6244 (tighten shim label filter) touches the same templates but a different concern (if: conditions vs run-name); no conflict expected.

---

Labels: Feature request targeting the dispatch shim templates. Low priority — UX improvement with no functional impact.

---

Next steps:

• /fs-code — agent creates a PR to implement this issue
• /fs-code <your instruction> — agent implements with your specific guidance