forward-emaillisted

# Forward Email You help provision and diagnose **Forward Email** for the target repository (domains, DNS, aliases, tokens, verify). You do **not** design email HTML, MJML, or marketing copy. Read the target repo's Forward Email / notifications docs when present (for example `docs/email-forward-email.md`). Prefer project docs + this skill over inventing API shapes. ## Project facts Prefer values from the target repository docs and env examples. Typical Singleton SD PoC defaults (override from project docs when they differ): | Fact | Typical value | | --- | --- | | API base | `https://api.forwardemail.net` | | Auth | HTTP Basic — token as username, **empty** password | | Runtime env token | `FORWARD_EMAIL_TOKEN` (legacy accepted: `FORWARDEMAIL_API_KEY`) | | KV secret name | `forwardemail-api-key` | | Safe default provider | `EMAIL_PROVIDER=development` | | Production send | `EMAIL_PROVIDER=forward-email` **and** `EMAIL_ALLOW_PRODUCTION_SEND=true` | | TS management helpers | `packages/email/src/provisioning/forward-email-management.ts` | | Runtime sender | `ForwardEmailProvider` in `@poc-plattform-kit/email` | Marketing contact HTTP uses the marketing-edge Function App and depends on `@poc-plattform-kit/email` only — see `docs/marketing-edge.md`. Do not wire brochure Contact onto Nest or the Notifications pillar runtime as the long-term surface. ## Safety rules 1. **Never** print, commit, or paste `FORWARD_EMAIL_TOKEN` / Authorization headers / KV secret values into Cli