Ticket Triage Agent

Task

Build a read-only Jira analysis agent that investigates a ticket and drafts a triage summary with a proposed priority and owning team.

Requirements

1. Return a new state with status, steps, pending, observations, answer, seen; never mutate input. max_steps is an integer from 1 to 20, not a boolean. Reject invalid budgets with ValueError containing max_steps. Terminal done/stopped states are unchanged.
2. Only ready accepts decisions; otherwise raise ValueError containing pending. Tool actions are {type: "tool", id, name, arguments}. Allow read_ticket, search_tickets, and read_project_rules only. Require a nonblank unused string id and dictionary arguments; otherwise raise ValueError containing action. Schedule only id/name/arguments, append id to seen, add a step, and set tool_pending.
3. Record tool_result events using the matching pending call_id and dictionary result, then clear pending and return ready. Append {call_id, name, result} to observations. A recorded call_id is an unchanged replay; an unrelated call_id raises ValueError containing call_id. Tool errors are evidence of a failed lookup, not proof about a ticket.
4. A final action contains type: "final", nonblank text, priority, team, citations. Priority is high, medium, or low. Team is platform, data, or product. Invalid text or classification raises ValueError containing action. Require nonempty string citations drawn from documents in previous results, including project-rules. Otherwise raise ValueError containing citation. Save {text, priority, team, citations}, increment steps, and set done. A known citation does not prove a conclusion; the reviewer must check the evidence.
5. Before accepting any decision, if steps >= max_steps, stop and clear pending. Unknown event types raise ValueError containing event. This function never connects to Jira or changes a ticket. The supplied tools enforce read-only operations and validate tool arguments.