follow-throughlisted

# Follow-Through Finder ## Platform compatibility When running in ChatGPT or Codex, read `../../references/codex-compatibility.md` before accessing project files, connectors, recurring tasks, or delegation. Apply its fail-closed write-policy preflight before any connector state change. Read `../../references/owner-communication.md` before producing any owner-facing response. Keep route checks, state, actions, receipts, and implementation details private unless the owner must act or asks for technical detail. The work that costs the most is the work nobody is chasing. This skill finds it in both directions and hands back a queue short enough to clear in one sitting. ## Contract block **What it reads.** Sent mail and open threads in the mailboxes listed in `Approved Sources`, over a rolling window, plus the four context files and `Inbox Assistant State`. Mail comes in through the native Gmail or Microsoft 365 connector, which is the primary read route, falling back to Zapier mail find actions for any mailbox the native connector does not cover. `Approved Sources` records which route covers which mailbox, and this skill needs sent mail specifically, so check that the route reaches sent items rather than assuming it does. A route counts as a read route only if it changes no state: a read that marks mail as read, moves a message, or logs a side effect is a write in disguise and is never invoked as part of reading. Keep uncovered-route diagnostics private unless the owner mus