Workflow origin for the Freshdesk ticket reply closure loop. It reads one ticket and its conversation context, creates exactly one owner-provided public reply through recued-core.freshdesk.ticket.reply.create, optionally updates that same ticket to a user-configured Freshdesk numeric status, and when the reply succeeds it seeds durable data.shared closure state for freshdesk-ticket-reply-closure-watcher. It uses user-configured deterministic copy rather than AI and does not create tickets, create private notes, delete, bulk update, attach files, mutate contacts or companies, change automations/dispatch rules/SLA/admin settings, or call arbitrary Freshdesk endpoints.

Scheduled adopter for Freshdesk ticket reply closure rows seeded by reply-freshdesk-ticket-with-closure. It lists only Recued-originated public-reply watches, re-reads a bounded batch of ticket from Freshdesk, and closes or flags the shared row when Freshdesk reports a configured closure or owner-actionable status. It can notify the owner on closure or customer-return states, but it never updates tickets, replies to customers, creates private notes, creates or edits automations/dispatch rules/SLA/admin settings, deletes records, or calls arbitrary Freshdesk endpoints.

Read-only AI-assisted review brief for one Freshdesk ticket. It reads the ticket, full conversation list, requester contact when available, company when available, time entries, and matching solution articles through recued-core.freshdesk, then summarizes the customer ask, urgency, history, support risk, and next response. It never replies, updates, deletes, bulk-mutates, attaches files, changes automations/admin settings, or calls arbitrary Freshdesk endpoints.

Owner-visible list/close role for recued-core/freshdesk-ticket-reply-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.