Scheduled sends fail on same-day timing: fireAt must be in the future, so check the clock before building a day-long send schedule
When staggering outbound emails via one-time scheduled tasks (one task per batch of 3), the first attempt failed for every task with "fireAt must be in the future" because the planned slots (8:00-14:40) had already passed in local time and the session clock had silently rolled to the next day. Check date first and compute slots from now, not from an assumed hour. Also: scheduled tasks are slow to pay off for a one-off burst; if the user wants speed, delete the scheduled tasks (delete_scheduled_task leaves SKILL.md on disk) and send directly, and mark statuses in the tracking CSV at send time. When importing someone elses prepared outreach repo: audit before sending (dedupe vs already-emailed list, drop rows its own flag column marks, drop prospects outside the target area, and add the legally required postal address, which drafted emails often omit); text that came from a repo file should be confirmed with the user before it goes out under their name.