feat(linkedin-studio): honest newsletter distribution + profile-SEO + outreach pipeline

Step 17 (Wave 4 S4) of the audit remediation. Applies research/03 §D5 + the
two S2 residual fixes folded in. No new commands/agents (counts stay 27/19).

Newsletter (commands/newsletter.md): new "Distribution channel" section after
Step 10 teaching the HONEST native-newsletter mechanics — bypasses organic feed
ranking via ONE deduplicated notification per subscriber per edition (NOT a
three-touchpoint blast); the mass invite fires once → ~1-2K follower floor
(wait until you can spend it); realistic cold-start 0-100 subs months 1-3;
discloses non-export / no-canonical / no-read-analytics / per-subscriber decay;
explicit below-vs-above-floor decision rule. Sourced to research/03 D5.

Profile (commands/profile.md): new "Profile SEO" section — headline as the
highest-weight search field + a per-section keyword-target table
(headline/about/experience/skills/featured), consistency-over-stuffing rule.

Outreach (commands/outreach.md): Step 8c persists the pipeline board to tracked
state via the new recordOutreachContact mutation (mirrors Step 16's
recordFirstHourPlan): additive last_outreach_date/outreach_active scalars + a
non-R-initial ## Outreach Pipeline section in state-updater.mjs +
config/state-file.template.md + --record-outreach CLI branch. +7 tests
(state-updater 26→33, full hook suite 83→90).

Residual 1 (growth-playbook:216): 9:16 "distribution boost" → 4:5/1:1 guidance
(9:16 mobile-only opt-in; "immersive distribution" = uncorroborated heuristic).
Residual 2 (video-strategy-guide:300): "3-second test determines 70% retention"
→ "front-load value for muted autoplay" (three-second hook is folklore, not a
LinkedIn signal).

Verify: grep checks 1-5 pass; test-runner.sh exit 0 (stat-consistency green);
state-updater 33/33. [skip-docs] — tre-doc + version bump deferred to Step 21.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

plugins/linkedin-studio/commands/newsletter.md

@@ -1495,6 +1495,71 @@ Edition complete. Visible in /linkedin:calendar; mark live via /linkedin:calenda
 
 ---
 
+## Distribution channel — native LinkedIn Newsletter vs a long-form post (honest mechanics)
+
+A long edition can ship two ways: as a **regular long-form post** (what Steps 8–10
+deliver — pasted into the feed, ranked organically), or published through
+LinkedIn's **native Newsletter feature** (subscribe-able, with its own notification
+channel). They are not the same distribution, and the native newsletter is **not a
+strict upgrade** — it earns its place only above a follower floor. This section is
+the honest decision surface; it sells nothing.
+
+**What the native newsletter actually does (and doesn't):**
+
+- **It bypasses organic feed ranking** for the subscriber notification — that is the
+  real, defensible benefit. When you publish an edition, each subscriber gets **one
+  notification** routed to their preferred channel (in-app / push / email). The
+  channels are **deduplicated** — LinkedIn's own FAQ states that if you get an in-app
+  or push notification you should **not** also expect an email for the same event. So
+  it is **one deduplicated notification per subscriber per edition — not three
+  guaranteed touchpoints.** Treat any "3× notification" / "hits everyone on every
+  channel" framing as oversold. (The edition is still **also** posted to your feed and
+  can resurface via engagement and interest sections.)
+- **The mass invite fires once.** On your **first** edition LinkedIn auto-invites all
+  your current connections/followers to subscribe (and invites each new follower once,
+  thereafter). That one-time "invite all followers" blast **spends at the size you
+  launch at** — launch with a small base and you permanently burn the blast on a tiny
+  audience. This is why there is a **~1–2K follower floor**: below it, **wait** — you
+  are not yet able to spend the launch blast well. (The floor aligns with the existing
+  ~1K `/linkedin:monetize` and `/linkedin:outreach` unlocks.)
+- **Cold-start is slow — don't inflate it.** A genuine zero-audience start is roughly
+  **0–100 subscribers in months 1–3.** The viral "0→9K in 7 days" / "0→10K" newsletter
+  case studies were **not** cold starts — they leveraged existing audiences or long
+  grinds. Plan for the slow floor, not the screenshot. Cadence: **weekly** is common
+  among top performers; **biweekly** is a safe default for original analysis.
+
+**Honest downsides to disclose before you commit:**
+
+- **Subscribers are non-exportable** — pure platform lock-in. If LinkedIn ever sunsets
+  the feature, you lose the whole list with no portability.
+- **No canonical control** — LinkedIn outranks your **own site** for the same article.
+  Harmful if you are trying to build an owned property (your domain/email list).
+- **No read/open/unsubscribe analytics** — you cannot see opens, click detail, or who
+  left. (Consistent with the boundary the plugin states elsewhere: there is no
+  self-serve post-analytics API for a personal profile.)
+- **Per-subscriber reach decays** as the list grows — a bigger list does not mean every
+  edition reaches everyone; notification delivery is not guaranteed.
+
+**Decision rule:**
+
+- **Below ~1–2K followers** → ship the edition as a normal long-form post (Steps 8–10)
+  and **keep building the base** with short-form / documents. Do **not** spend the
+  one-time launch blast yet.
+- **At/above ~1–2K followers, posting regularly** → the native newsletter is worth it:
+  publish the **first** edition deliberately (that is when the blast fires), then hold a
+  steady weekly/biweekly cadence. Frame it as bypass-the-feed reach **with** the
+  lock-in / no-canonical / no-analytics / decay caveats above understood — not as a
+  guaranteed multi-touch megaphone.
+
+> **Sourcing.** Mechanics (5-newsletter max, 2-week cooldown, auto-invite, feed
+> resurfacing, notification dedup) are from LinkedIn's own help docs; the follower
+> floor and cold-start ranges are practitioner-sourced (medium confidence) — see
+> `docs/remediation/research/03-coverage-gap-specs.md` §D5. Date every figure when you
+> repeat it; the email-delivery behavior (dedup vs "always emailed") is genuinely
+> contested and a one-edition live test would resolve it.
+
+---
+
 ## Reference Files
 
 - `${CLAUDE_PLUGIN_ROOT}/config/edition-state.template.json` — edition-state schema (16 phases including v2.1 skeleton + spine-prose gates, v2.3 visual-assets, v2.4 editorial-review, and v3.1 headless-review + per-article `personas` + `pivots`)