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

Scheduled adopter for Jira issue closure rows seeded by create-jira-issue-with-closure. It lists only Recued-originated issue 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, adds worklogs to, or otherwise mutates Jira issues.

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