Workflow origin for the Jira issue comment closure loop. It reads one Jira issue and current comments for context, creates exactly one owner-provided Atlassian Document Format comment through recued-core.jira.comment.add, and when the comment succeeds it seeds durable data.shared closure state for jira-issue-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, transition, assign, delete, attach to, link, watch, vote on, or otherwise mutate Jira issues.

Scheduled adopter for Jira issue comment closure rows seeded by comment-jira-issue-with-closure. It lists only Recued-originated issue-comment watches, re-reads a bounded batch of Jira issue, and closes the shared row when Jira reports that issue has reached the Done status category. It can notify the owner on closure, but it never creates, updates, transitions, assigns, deletes, attaches to, links, watches, votes on, comments on, or otherwise mutates Jira issues.

Low-frequency timeout role for recued-core/jira-issue-comment-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.

Owner-visible list/close role for recued-core/jira-issue-comment-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.