open/ktg-plugin-marketplace
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions

docs(linkedin-studio): drop top What's New section, lead with motivation

Browse source 
The standalone "What's New in v3.1.0" section opened with internal
development narrative (Endring 9, Del 4 run, framing-bias) that means
nothing to a prospective adopter — still leading with a changelog, the
exact pattern the rewrite set out to fix. Follow llm-security: motivation
first, version detail only in the Version History table at the bottom.

- Remove the "## What's New in v3.1.0" section and its TOC entry
- README now flows intro → Why LinkedIn Studio Exists → What Is This?
  → Two Engines → Quick Start
- Nothing lost: v3.1.0 remains in the Version History table

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-05-29 13:50:43 +02:00
commit 10870107e4
1 changed files with 0 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

19
plugins/linkedin-studio/README.md
View file

@ -20,7 +20,6 @@ Most experts know they *should* post on LinkedIn — and quietly don't. The blan
## Table of Contents ## Table of Contents
- [What's New in v3.1.0](#whats-new-in-v310)
- [Why LinkedIn Studio Exists](#why-linkedin-studio-exists) - [Why LinkedIn Studio Exists](#why-linkedin-studio-exists)
- [What Is This?](#what-is-this) - [What Is This?](#what-is-this)
- [Two Engines](#two-engines) - [Two Engines](#two-engines)
@ -41,24 +40,6 @@ Most experts know they *should* post on LinkedIn — and quietly don't. The blan
--- ---
## What's New in v3.1.0
**An adversarial review package becomes part of the long-form pipeline (Endring 9).** The most recent production run shipped a high-quality article, but its quality assurance leaned on one good editor plus the operator's availability to re-read it several times — it did not scale. The root cause: the editor and the persona sweep ran *in the same session as drafting*, sharing the conversation history (which versions passed, what was cut, which flags were raised). They carried the drafting session's **framing-bias** and were therefore not independent. Three symptoms followed: the resonance sweep effectively judged an early version rather than the one that shipped, editor-approval was single-source, and the fact-check was post-hoc relative to a late pivot — so the pivot could build on an unverified premise.
v3.1.0 answers this with a **cold review package** that reconstructs everything from disk and refuses the drafting session's framing as "context pollution".
- **Three new headless review archetypes** (all Opus, cold/headless): **`content-reviewer`** (argument integrity — logical holes, unsupported assumptions, contradictions, missing concretization, unanswered objections; ≤8 flags), **`language-reviewer`** (Norwegian language — verbatim repetition, anglicisms, stiff register, self-contradiction, clang/rhythm; ≤10 flags), and **`fact-reviewer`** (cold re-verification of the frozen/pivoted version via web search, plus a pivot-risk subsection; deliberate redundancy with `fact-checker` to catch a premise that arrived after the fact-check ran).
- **New `/linkedin:headless-review` command** — runs the cold package on a FROZEN draft, designed to be invoked in a **fresh session** for maximum isolation, reconstructing the draft + writing contract + personas from disk.
- **New Step 6.5 (headless-review)** in `/linkedin:newsletter` — fans the package out in parallel after the in-session persona sweep, on a frozen snapshot, BEFORE lock. Converged flags (two independent cold reviewers agreeing) are the strongest signal.
- **New `/linkedin:pivot` command + pivot-detection gate** — a late change re-opens the cleared gates so they re-run on the changed version before lock. Heuristic: a draft that drifted **> 20 % in word count OR gained > 2 sections** fires the gate.
- **Per-artifact personas** (`articles.NN.personas`) — one or more readers configurable **per edition**, resolved in order (edition-state → per-series file → plugin library → interactive).
Counts: 24 → 26 commands; 16 → 19 agents; newsletter pipeline 15 → 16 phases. **Backward-compatible** — every state-shape change is additive. **Reload required** before the three new agents resolve.
> See the full release-by-release history in the [Version History](#version-history) table at the bottom.
---
## Why LinkedIn Studio Exists ## Why LinkedIn Studio Exists
For most professionals, the hard part of LinkedIn isn't writing — it's everything around it. You have the expertise. What you don't have is a repeatable way to get it out the door, consistently, in a form the algorithm actually rewards. For most professionals, the hard part of LinkedIn isn't writing — it's everything around it. You have the expertise. What you don't have is a repeatable way to get it out the door, consistently, in a form the algorithm actually rewards.