fix(linkedin-studio): N24.5 — mekanisk gjeldssveip (plugin.json, CHANGELOG-dublett, de-niche, KTG, Step 9-nøkler) [skip-docs]

Fem grep-lokaliserte gjeldsposter fra STATE FUNN, pluss to anti-erosjons-lints
som gjør to av dem terminale i stedet for gjenoppdaget en gang til.

1. .claude-plugin/plugin.json description — v4.0.0-arvet release-notat med
   historiske tellinger («→ 19 agents», «→ 27 commands», «→ 29 commands»)
   erstattet av en beskrivelse av hva pluginen ER. Dette er teksten /plugin
   viser. Ingen tellinger i teksten: de drifter, og CHANGELOG.md eier historikken.

2. CHANGELOG hadde TO «## [0.6.0]»-overskrifter (2026-07-17 = ekte, 2026-02-07 i
   halen). Halens datert om til «## [0.6.0-legacy]». Sjette gangs gjenoppdagelse
   — derfor lint, se punkt 6.

3. De-niche: 7 «thought leader»-treff utenfor commands/ rettet — README (mot
   kommandoens egen frontmatter-ordlyd), skills/linkedin-networking (2:
   FUNN-listen navnga bare :9, men :185 var samme defekt), analytics-interpreter,
   analytics-tools-guide, collaborations-guide, linkedin-visual-style.
   BEVISST BEHOLDT: de 5 blocklist-linjene, de to negative eksemplene
   (opportunity-generation, det ironiske sitatet i video-strategy-guide), og
   network-builder:562 — et WebSearch-uttrykk som treffer hvordan ANDRE
   merker seg selv, allerede paret med «Creator».

4. Hardkodet «KTG» i generisk operatør-tiltale fjernet. FUNN navnga tre linjer i
   language-reviewer; klassen var 21 linjer over 4 agenter, newsletter.md,
   edition-state-templaten og specifics-bank sitt renderte NN-kilder.md-artefakt.
   BEVISST BEHOLDT som proveniens: CHANGELOG, tests/fixtures/* (de ER KTGs
   faktiske redaktørrunde, kalibreringsfasiten), adopter-notatene som ærlig
   flagger KTG-interne verktøy (contract-gate, specifics-bank), «KTG
   cover-directive» og «answers KTG's question» — attribusjon, ikke tiltale.

5. Step 9 persisterte tre nøkler templaten aldri deklarerte: randsoneGate (N9),
   hookForge + personaSweep.deling (N24). Nå deklarert i BÅDE artikkel-shapen og
   _doc. Additivt, schemaVersion forblir 1. _doc.hookForge bærer N22-invarianten
   videre: en variant har målt lengde / krok-type / kroppsspor og ALDRI en
   predikert engagement-score.

6. To nye ubetingede lints (Section 16aa), begge mutasjonstestet mot de FAKTISKE
   filene, ikke bare mot self-testen:
   - CHANGELOG-dublettvakt (+ in-memory non-vakuitets-self-test som skiller en
     ekte dublett fra en bevisst «-legacy»-overskrift)
   - Step 9-nøkkeldeklarasjon (shape + _doc)
   Mutasjon 1 (gjeninnfør dubletten) → rødt. Mutasjon 2 (fjern hookForge fra
   shapen) → rødt. Mutasjon 3 (fjern _doc.randsoneGate, fila fortsatt gyldig
   JSON) → rødt. Restaurert → grønt.

Ti suiter grønne: test-runner 300 → 303 (floor 281 → 284) · trends 300 ·
analytics 202 · hooks 191 · brain 134 · editions 72 · render 63 ·
specifics-bank 45 · tests 35 · contract-gate 33.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017vMLTF7J13jJmgqwwJyivt

agents/analytics-interpreter.md

@@ -424,7 +424,7 @@ Remind them:
 - Month 1: Learning mechanics (baseline)
 - Month 3: Understanding YOUR patterns (above average)
 - Month 6: Discovering insights from practice (exceptional)
-- Month 12: Systematically generating unique perspectives (thought leader)
+- Month 12: Systematically generating unique perspectives (recognized expert)
 
 ## References
 

agents/content-reviewer.md

@@ -181,7 +181,7 @@ flags; if you suppressed any, say how many and of what severity.
 ### Step 4 — Emit the report (the operator gates)
 
 You do **not** gate the pipeline yourself — your output is surfaced to the
-operator (KTG) as a markdown report (`SendUserFile`), and the operator decides
+operator as a markdown report (`SendUserFile`), and the operator decides
 which flags fold in. Your severity ranking is the *recommendation*; the operator
 holds the gate (`[OPERATØR]`). After fold-in, the editor (the command session)
 produces a revised draft and **may re-run you** on the cleaned version before
@@ -238,7 +238,7 @@ before lock (Step 8). Operator decides fold-in; this is [OPERATØR].
    C2 / C4); NICE = a cheap soft spot. Sort BLOCK→REWORK→NICE.
 7. **Cap at eight; never truncate silently.** If you suppressed findings, say how
    many and of what severity (`no silent caps`).
-8. **The operator gates, you recommend.** Your output is a report for KTG, not a
+8. **The operator gates, you recommend.** Your output is a report for the operator, not a
    pipeline stop. BLOCK is your strongest recommendation, not a hard halt — the
    gate is `[OPERATØR]`.
 

agents/editorial-reviewer.md

@@ -28,7 +28,7 @@ tools: ["Read", "Grep"]
 
 You are an **editor**. You read a near-final long-form draft and judge whether the
 **prose is clean** and the **narrative architecture holds** — the craft layer a
-reader never names but always feels. You are the pass a human editor (KTG) makes
+reader never names but always feels. You are the pass a human editor makes
 on first reading, operationalized as an automated pre-persona gate.
 
 You run at **Step 5.5** of the `/linkedin:newsletter` pipeline — *after* the
@@ -182,7 +182,7 @@ flags**; if you suppressed any, say how many and of what severity.
 ### Step 5 — Emit the report (the operator gates)
 
 You do **not** gate the pipeline yourself — your output is surfaced to the
-operator (KTG) as a markdown report (`SendUserFile`), and the operator decides
+operator as a markdown report (`SendUserFile`), and the operator decides
 which flags fold in. Your severity ranking is the *recommendation*; the operator
 holds the gate (`[OPERATØR]`). After fold-in, the editor (the command session)
 produces v(n+1) and **may re-run you** on the cleaned version before Step 6.
@@ -233,7 +233,7 @@ before the Step 6 persona sweep. Operator decides fold-in; this is [OPERATØR].
    takeaway; REWORK = real weakness; NICE = cheap polish. Sort BLOCK→REWORK→NICE.
 6. **Cap at ten; never truncate silently.** If you suppressed findings, say how
    many and of what severity (`no silent caps`).
-7. **The operator gates, you recommend.** Your output is a report for KTG, not a
+7. **The operator gates, you recommend.** Your output is a report for the operator, not a
    pipeline stop. BLOCK is your strongest recommendation, not a hard halt — the
    gate is `[OPERATØR]`.
 8. **The in-tree checklist is the operative source of truth.** It ships and is

agents/fact-reviewer.md

@@ -188,7 +188,7 @@ corrected sentence is not. If you ever hand back edited prose, you have failed t
 role.
 
 You do **not** gate the pipeline. Your output is a markdown report surfaced to the
-operator (KTG) via `SendUserFile`; the operator decides which fixes fold in. Every
+operator via `SendUserFile`; the operator decides which fixes fold in. Every
 claim row carries the **source found** or **"none found"** — no row is left
 unaccounted.
 
@@ -313,7 +313,7 @@ already hedged in the draft.]
    that fails verification is the headline catch.
 8. **A contradicted claim is 🔴, not 🟡.** Never soften disproving evidence.
 9. **Direction, not copy; the operator gates.** Verdicts + fixes-as-direction, never
-   rewritten prose. You recommend PASS/REWORK/BLOCK; KTG holds the gate.
+   rewritten prose. You recommend PASS/REWORK/BLOCK; the operator holds the gate.
 
 ## Anti-Patterns
 

agents/language-reviewer.md

@@ -185,7 +185,7 @@ carries a **quote or line reference.** If you ever hand back edited prose, you
 have failed the role.
 
 You do **not** gate the pipeline. Your output is a markdown report surfaced to the
-operator (KTG) via `SendUserFile`; the operator decides which flags fold in. Your
+operator via `SendUserFile`; the operator decides which flags fold in. Your
 severity ranking is the *recommendation*; the operator holds the gate
 (`[OPERATØR]`).
 
@@ -226,7 +226,7 @@ flags**; if you suppressed any, say how many and of what severity.
 ### Step 5 — Emit the report (the operator gates)
 
 You do **not** gate the pipeline yourself — your output is surfaced to the
-operator (KTG) as a markdown report (`SendUserFile`), and the operator decides
+operator as a markdown report (`SendUserFile`), and the operator decides
 which flags fold in. Your severity ranking is the *recommendation*; the operator
 holds the gate (`[OPERATØR]`).
 
@@ -284,7 +284,7 @@ before lock. Operator decides fold-in; this is [OPERATØR].
    polish. Sort BLOCK→REWORK→NICE.
 7. **Cap at ten; never truncate silently.** If you suppressed findings, say how
    many and of what severity.
-8. **The operator gates, you recommend.** Your output is a report for KTG via
+8. **The operator gates, you recommend.** Your output is a report for the operator via
    `SendUserFile`, not a pipeline stop. BLOCK is your strongest recommendation,
    not a hard halt — the gate is `[OPERATØR]`.