Workflow origin for the GitLab issue note closure loop. It reads one GitLab issue and current comment notes for context, creates exactly one owner-provided public note through recued-core.gitlab.issue.note.create, and when the note succeeds it seeds durable data.shared closure state for gitlab-issue-note-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, close, reopen, delete, move, label, assign, or otherwise mutate GitLab issues.

Scheduled adopter for GitLab issue note closure rows seeded by comment-gitlab-issue-with-closure. It lists only Recued-originated issue-note watches, re-reads a bounded batch of GitLab issue, and closes the shared row when GitLab reports that issue closed. It can notify the owner on closure, but it never creates, updates, closes, reopens, deletes, moves, labels, assigns, comments on, or otherwise mutates GitLab issues.

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