Workflow origin for the Confluence inline comment reply closure loop. It reads one Confluence page and its open inline comments for context, creates exactly one owner-provided storage-format reply on an existing inline comment through recued-core.confluence.inline_comment.create, and when the reply succeeds it seeds durable data.shared closure state for confluence-inline-comment-reply-closure-watcher. It uses deterministic owner-provided storage content rather than AI and does not create top-level inline comments, create footer comments, edit or resolve comments, update pages, delete pages, update tasks, alter labels, change permissions, create properties, configure automations, or call arbitrary Atlassian endpoints.

Scheduled adopter for Confluence inline comment reply closure rows seeded by reply-confluence-inline-comment-with-closure. It lists only Recued-originated inline-comment reply watches, re-reads a bounded batch of Confluence page and that page's inline comments, and closes or flags the shared row when Confluence reports the watched root comment resolved, the comment is no longer returned, or the page reaches a configured terminal status. It can notify the owner on resolution, disappearance, or terminal page status, but it never creates, updates, resolves, deletes, or comments on Confluence content, updates pages, changes tasks, alters labels, changes permissions, creates properties, configures automations, or calls arbitrary Atlassian endpoints.

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