sent-mail-outcome-trackerlisted

# Sent-mail outcome tracker The rest of the toolkit asks "is this email well-written?" This skill asks the only question that actually matters: "did the email get a reply, and what did the messages that replied have in common?" Composes with `voice-update --source sent-mail` (which audits voice files against sent mail). This skill produces outcome data; voice-update proposes voice updates if patterns emerge. ## Why this exists Two gaps the existing toolkit does not close: 1. **The critic measures rule recall, not response rate.** The eval harness asserts the inline critic catches em-dashes and vague asks. None of that proves the resulting emails get replies. Reply rate is the only metric the recipient cares about, and it is the only one that compounds. 2. **You learn from outcomes, not from the draft.** A draft that passes every rule and gets ignored teaches you something the rules cannot. A draft that breaks a rule and gets a same-day intro teaches you something the rules will never catch. Both signals live in the sent folder and the inbox, not in the rule library. Auto-tracking every email is out of scope. The user invokes this on demand, the skill reads, the skill reports. The user judges what to change. ## Inputs Optional arguments: - **Time window**: default `last 30 days`. Accept "last week," "last 3 months," "since [date]." - **Count cap**: default `25 messages`. Cap at 50 to keep token cost bounded. - **Mode filter**: default `cold outreach only`. The skill ap