Story 17.8 — R1 blog series + LinkedIn cadence + editorial calendar

[fupelaqu]

Epic 17 (R1 Documentation & Marketing), Story 17.8 — elasticsql side (Channel B).

Commits the R1 marketing content that announces R1 cleanly with the locked "stop ETL'ing ES just to JOIN it" positioning, so the project lead isn't writing copy on launch day.

Deliverables (this repo):

• 4 R1 blog drafts in blogs/ (Channel B — Medium / personal LinkedIn; site collection deferred):
  • announcing-r1-cross-cluster-join.md (J+0 launch)
  • join-matrix-walkthrough.md (J+7)
  • sre-cross-cluster-incident-triage.md (J+14)
  • how-customers-use-r1.md (J+21, fully-anonymized vignettes)
• 4 LinkedIn drafts + editorial calendar in linkedin/:
  • r1-launch-announcement.md, r1-demo-teaser.md, r1-bi-showcase.md, r1-federation-reveal.md, r1-editorial-calendar.md

Guards honored: price €119 never €129; no hard perf numbers (Arrow benchmark reserved for R1.1/Epic 18); ELv2 not "source-available"; Power BI never "ADBC default driver"; every blog post ≥1 LIVE cross-link; pending cross-links carry tracked markers (launch-gated). Editorial calendar documents the Epic-18 non-overlap guard and the R2a 90-day quiet-window hold (policing owner = project lead).

Last story of Epic 17. Refs #148.

[fupelaqu]

Closing: Story 17.8's blog + LinkedIn content is local-only working material (never committed to the public elasticsql repo). It is being rewritten as untracked drafts in elasticsql/blogs/. The landing-page deliverable is tracked in the softclient4es-web side (issue #24 / PR #25). Epic 17 tracked in #148.