Get Cs Ticket Research

Every operational fact behind one ticket, gathered before a human asks.

See ticket_research for the incident this exists because of. In short: build_ticket_context returns the conversation and the account's ticket history and NOTHING operational, so on a ticket naming four parcel codes Rooster could only restate the question. This is the other half.

Deterministic on purpose -- the queries are fixed and run every time, so the agent never has to know which lookup to reach for and can never silently skip one. Its judgment goes on TOP of this, in the note it writes for the account manager; the gathering is not a judgment call.

Same rooster:cs:draft grant as every other CS route: reading the facts behind a ticket he may already draft for needs no new key. Scoped to this ticket's own organization for the account history, so drafting for one customer never becomes a window onto another's.