Workflow origin for the Google Drive file comment closure loop. It reads one Drive file and its current comments for context, creates exactly one owner-provided top-level file comment through recued-core.gdrive.file.comment.create, and when the comment succeeds it seeds durable data.shared closure state for google-drive-file-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not edit or delete comments, resolve comment threads, change file permissions, mutate document body content, download files, move files, create folders, configure Drive notifications, or call arbitrary Google Drive endpoints.

Scheduled adopter for Google Drive file comment closure rows seeded by comment-google-drive-file-with-closure. It lists only Recued-originated file-comment watches, re-reads a bounded batch of Drive comment thread, and closes the shared row when Google Drive reports that comment resolved or deleted. It can notify the owner on resolution or deletion, but it never creates, edits, deletes, or resolves comments, changes file permissions, mutates document body content, downloads files, moves files, configures Drive notifications, or calls arbitrary Google Drive endpoints.

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