Workflow origin for the Zendesk ticket reply closure loop. It reads one ticket for context, updates exactly that ticket with an owner-provided public reply through recued-core.zendesk.ticket.update, and when the public reply succeeds it seeds durable data.shared closure state for zendesk-ticket-reply-closure-watcher. It uses user-configured deterministic copy rather than AI and does not create tickets, create internal notes, delete, bulk update, attach files, redact comments, execute macros, create or edit triggers or automations, change SLA/admin settings, or call arbitrary Zendesk endpoints.

Scheduled adopter for Zendesk ticket reply closure rows seeded by send-zendesk-ticket-reply-with-closure. It lists only Recued-originated public-reply watches, re-reads a bounded batch of ticket from Zendesk, and closes or flags the shared row when Zendesk 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, executes macros, creates or edits triggers or automations, changes SLA/admin settings, redacts comments, deletes records, or calls arbitrary Zendesk endpoints.

Read-only review brief for one Zendesk ticket. It reads ticket details, comments, audits, and ticket metrics through recued-core.zendesk, then asks the AI summarizer for customer ask, status, blockers, owner expectations, and the next response. It never creates, updates, deletes, redacts comments, executes macros, changes admin settings, or calls arbitrary Zendesk endpoints.

Low-frequency timeout role for recued-core/zendesk-ticket-reply-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.