Workflow origin for the Front conversation reply reopen loop. It reads one conversation and its latest event, sends exactly one owner-provided customer reply through recued-core.front.conversation.reply, and when the approved reply operation succeeds it seeds durable data.shared state for front-conversation-reply-reopen-watcher. It uses user-configured deterministic copy rather than AI and does not archive conversations, change ticket status, create internal comments, mutate tags or custom fields, configure Front Rules, create reminders, alter inbox/admin settings, create webhooks or application triggers, delete records, upload attachments, bulk mutate, or call arbitrary Front endpoints.

Scheduled adopter for Front conversation reply reopen rows seeded by reply-front-conversation-with-reopen-watch. It lists only Recued-originated public-reply watches, re-reads a bounded batch of Front conversation and its latest events, and closes or flags the shared row when Front reports a terminal status, resolved ticket category, newer customer-return event, reopen event, or delivery error. It can notify the owner on closure or owner-actionable states, but it never updates conversations, sends replies, creates comments, creates reminders, mutates tags or custom fields, creates or edits Front Rules, changes inbox/admin settings, creates webhooks or application triggers, deletes records, bulk mutates, or calls arbitrary Front endpoints.

Low-frequency timeout role for recued-core/front-conversation-reply-reopen. 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.

Owner-visible list/close role for recued-core/front-conversation-reply-reopen. 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.