Campaign launch and inbox management

Apply ../00-lead-generation-guardrails/SKILL.md first. Every recipient this skill launches to must already be resolved against that skill's compliance matrix. This skill does not re-derive a recipient's compliance status from scratch — it re-verifies the post-import list against that matrix for the email channel (the Launch Gate, section 1) and adds a new, channel-specific check the moment a step reaches for a channel the earlier list-building/copywriting pass did not clear (the phone/SMS gate, section 3).

This skill is a launch-and-response workflow, not a copywriting or infrastructure workflow: it takes an already-verified list (skill 03), already-drafted copy (skill 05), and an already-provisioned sending domain/mailbox (skill 04) and moves them into a live send, then manages what comes back. It consumes skill 04's cold_email_sending capability and providers/calendly/'s meeting_scheduling capability by the selection algorithm in ../../docs/PROVIDER_SELECTION.md — it never re-declares either capability or hardcodes a provider name.

Architecture

LIST UPLOAD -> PLATFORM COPY-IN -> LAUNCH GATE -> SEND
  -> INBOX MONITORING (response-time SLA) -> REPLY TRIAGE
  -> PHONE/SMS CONSENT GATE (any contact attempt, autodialed or manual) -> PHONE-FIRST FOLLOW-UP
  -> CALENDAR SCHEDULING (multi-option, never a bare link) -> BOOKING

1. Upload list and copy into the sending platform