Workflow origin for the Bitbucket pull request comment closure loop. It reads one Bitbucket pull request and current comments for context, creates exactly one owner-provided top-level comment through recued-core.bitbucket.pull_request.comment.create, and when the comment succeeds it seeds durable data.shared closure state for bitbucket-pull-request-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not approve, request changes, merge, decline, edit, resolve, delete, update pull request metadata, run pipelines, or otherwise mutate Bitbucket pull requests.

Scheduled adopter for Bitbucket pull request comment closure rows seeded by comment-bitbucket-pull-request-with-closure. It lists only Recued-originated pull-request-comment watches, re-reads a bounded batch of Bitbucket pull request, and closes the shared row when Bitbucket reports that pull request merged, declined, or superseded. It can notify the owner on terminal pull request state, but it never creates, updates, approves, requests changes, merges, declines, deletes, resolves, comments on, runs pipelines for, or otherwise mutates Bitbucket pull requests.

Low-frequency timeout role for recued-core/bitbucket-pull-request-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/bitbucket-pull-request-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.