Detection half of the meeting-request conversion edge for the outbound follow-up loop. It scans data.shared watch rows written by outbound-follow-up-response-watcher, picks one response_needs_owner row classified as meeting_requested that is not already converted or already proposed, fetches the reply body from the recorded mail slug and record id, extracts explicit schedule fields, and writes a durable proposal (extracted meeting details + linkage, status awaiting_owner_approval) plus a notification for the owner. It never creates a calendar event or sends an invite itself: the actual approval-gated create is owner-invoked via outbound-follow-up-schedule-approved-meeting. Runs unattended (auto_run) but takes no outward-facing action, because under auto_run an internal calendar write would otherwise execute silently at the admin trust ceiling. It never invents a start time and skips rows that lack enough linkage to fetch the reply.