fix(dispatch): route issues opened/edited to triage in per-repo mode

[rh-hemartin]

Summary

• reusable-dispatch.yml was missing the opened|edited → triage branch in the issues) routing case
• Org-mode dispatch.yml has had this routing since the feature was introduced; per-repo was an omission from the original implementation (3bcd099e)
• The shim (shim-per-repo.yaml) already subscribes to issues: [opened, edited, labeled] — only the dispatch routing logic needed updating

Fixes #1241

Test plan

• Open an issue in a per-repo-enrolled repository — triage agent should trigger
• Edit an issue in a per-repo-enrolled repository — triage agent should trigger
• Add ready-to-code label — code agent should still trigger (no regression)
• Add ready-for-review label — review agent should still trigger (no regression)

🤖 Generated with Claude Code

[github-actions]

Site preview

Preview: https://c99fd2d8-site.fullsend-ai.workers.dev

Commit: 28ed9d15d6f4a210be3d5ae19864cd898f7d7df2

[fullsend-ai-review]

Review

Findings

Medium

• [protected-path] .github/workflows/reusable-dispatch.yml — This PR modifies a file under .github/, which is a protected path requiring human approval. The change is well-justified (linked issue dispatch: per-repo install does not trigger triage on issue open #1241, clear rationale for adding the missing opened|edited → triage routing to match org-mode behavior), but human review and approval is always required for protected-path changes regardless of context.

The code change itself is correct: the new if/elif structure matches the org-mode dispatch.yml pattern exactly, the shim already subscribes to issues: [opened, edited, labeled], and the existing labeled routing is preserved via elif. No correctness, security, injection, or documentation staleness concerns identified.

[ralphbean]

LGTM.