Add JIRA support to the triage agent

[ralphbean]

The triage agent should optionally respond to JIRA issues (if configured) and triage them the same way it does GitHub issues.

Manish Kumar has a working prototype of this — same agent, routed by a TRIAGE_SOURCE env var. He demonstrated auto-triage on issue creation and on-demand /fs-triage against KFLUXINFRA issues. PR #2162 captures his implementation.

What needs to happen depends on the trigger model and identity story, but the agent-side work is: read a JIRA issue instead of a GitHub issue, produce triage output, and write it back as a JIRA comment.

Related: #2162, #1992

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:03 PM UTC · Completed 8:05 PM UTC
Commit: 4e21a60 · View workflow run →

[fullsend-ai-triage]

Triage Summary

This is a well-defined feature request to extend the triage agent to support JIRA issues alongside GitHub issues.

Problem: The triage agent is currently GitHub-only. Teams using JIRA for issue tracking cannot benefit from automated triage.

Prior art: PR #2162 contains a comprehensive working implementation that covers the full stack — agent prompt, harness config, pre/post scripts, ADF comment formatting, credential isolation, enrollment CLI, and scaffold workflows. It has been locally tested against a real JIRA instance (KFLUXINFRA-3002).

Key design decisions in PR #2162:

• Credential isolation: JIRA credentials never enter the sandbox; pre/post scripts handle API calls on the host
• Label namespacing: All agent labels prefixed fullsend: to avoid conflicts
• Trigger model: JIRA Automation Rules fire repository_dispatch events (no polling)
• Sticky comments: Triage comments update in place rather than appending duplicates

Recommended path forward: Review and iterate on PR #2162 rather than reimplementing. The PR includes 60 unit tests (14 pre-script, 46 post-script) and documents what can only be tested post-merge (end-to-end dispatch flow, enrollment CLI against tagged ref).

Related issues: #2263 (JIRA trigger model) addresses foundational trigger questions. #1992 tracks broader JIRA workflow scoping. #2265, #2266, #2267 track JIRA support for other agents.

Proposed test plan:
- Unit: pre-script (issue fetch, label strip, context JSON) and post-script (label apply, ADF posting, sticky update)
- Integration: enroll test project → create JIRA issue → verify dispatch triggers triage → confirm ADF comment + labels
- Edge cases: empty descriptions, non-ASCII in ADF, re-triage idempotency

---

Labels: This is a feature request for extending the triage agent to support JIRA, touching the dispatch component for trigger routing.