Triage Cs Ticket

Rooster's triage tool (see app/modules/rooster/triage.py): reaches one of three conclusions on a ticket BEFORE ever drafting anything -- 'reply' (proceed to draft exactly as before this route existed, no side effect), 'suggest_spam' (unsolicited marketing/bulk mail -- do not draft; a human confirms via the pre-existing POST .../spam button), or 'unsure' (genuinely ambiguous -- leave it for a human rather than guess either way). Records a 'declined' disposition for the latter two -- docs/SUPERVISION_DESK.md's outcome taxonomy, a SUCCESS, never 'abandoned' -- and raises a human-visible ActionItem routed the same way every other ticket-scoped card in this codebase already is.

Gated on the SAME rooster:cs:draft grant as every other CS-drafting route -- deciding whether a ticket deserves a reply is part of the same drafting capability, not a new one. Idempotent per ticket, exactly like POST .../escalate: a repeat call while a triage card for this ticket is still on file reuses that card and records no second disposition (created: false).