Workflow origin for the Linear issue closure loop. It creates exactly one owner-approved issue through recued-core.linear.issue.create, and when the issue succeeds it seeds durable data.shared closure state for linear-issue-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, move, cancel, complete, delete, archive, assign, label, subscribe to, comment on, or otherwise mutate Linear issues beyond the approved issue create.

Scheduled adopter for Linear issue closure rows seeded by create-linear-issue-with-closure. It lists only Recued-originated issue watches, re-reads a bounded batch of Linear issue, and closes the shared row when Linear reports the issue completed or canceled. It can notify the owner on terminal issue state, but it never creates, updates, moves, cancels, completes, deletes, archives, assigns, labels, subscribes to, comments on, or otherwise mutates Linear issues.

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