kai-email-systemlisted

## Objective A complete, gated email system for a product: an approved lifecycle map covering every touchpoint the product actually has, plus produced copy for each email in priority order, plus the Loops implementation notes an operator needs to wire the triggers. All emails target Loops (lifecycle + transactional). The map is the contract — the emails are what the map spawns. ## Done when Work type `email-lifecycle` — floor **E5/C3/O3** (`harness/eco-floors.yaml`). Any cold outreach email inside the system is graded under `cold-email` instead (floor **E5/C4/O3**). - **E5** — the ESP reports the send completed with a recipient count reconciled to the approved segment. This skill's local output reaches E3 at best: a named human approved the lifecycle map and the exact copy. The floor closes when the sends go out through Loops, which happens outside this skill. - **C3** — every email passes its declared gates (below), and a named non-producer read the set end to end. Unsubscribe and sender-identity compliance is a C4 field-standard item rather than a lint — check it against `harness/references/advertising-compliance.md`. - **O3** — open rate, click rate, reply rate, unsubscribe rate, and revenue per recipient read from the ESP connector at 14 days. Record the baseline and threshold before the first send, never after. ## Constraints - **`MARKETING.md` in the project root is the product bible.** Read it before asking the user anything. If it does not exist, build it from t