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

commands/newsletter.md

@@ -1426,19 +1426,19 @@ and `persona-reviewer` never flags em-dash density (that is this step).
    grep-able, the architecture checks need a read.
 
 3. **Surface the report to the operator (`SendUserFile` — the Endring-5 pattern).**
-   The flags are surfaced to KTG as a **markdown report**, the same operator-gate
+   The flags are surfaced to the operator as a **markdown report**, the same operator-gate
    shape the visual-assets step (7.5) uses for candidates and Steps 2.5/3a use for
    annotation:
    1. Write the agent's report to `<serie>/NN-editorial-review.md` (NN = the same
       zero-padded edition number; new suffix, a first-class artifact alongside
       `NN-skjelett.md`).
-   2. `SendUserFile` it (else a markdown `file://` link) so KTG can read the flags
+   2. `SendUserFile` it (else a markdown `file://` link) so the operator can read the flags
       sorted BLOCK → REWORK → NICE and **decide which fold in**.
-   3. **KTG gates.** The agent's severity ranking is a *recommendation*; the
+   3. **The operator gates.** The agent's severity ranking is a *recommendation*; the
       operator holds the gate. A BLOCK is the agent's strongest "must fix before
       Step 6", not an automatic pipeline halt. `[OPERATØR]`
 
-4. **Fold in the approved flags by tightening, → v(n+1).** Fold the flags KTG
+4. **Fold in the approved flags by tightening, → v(n+1).** Fold the flags the operator
    approved into `<serie>/NN-utkast.md` **by tightening** (rule 6 of
    `references/longform-quality-rules.md` — close the gap, hold the length flat;
    never expand to paper over a craft defect). The result is the next draft
@@ -1458,7 +1458,7 @@ and `persona-reviewer` never flags em-dash density (that is this step).
    fold-in was substantive (especially any BLOCK), re-run the agent on v(n+1) to
    confirm the flags cleared and no new craft defect was introduced by the edit.
    This loop is cheap and is the point of the gate — every craft round saved here
-   is a KTG round saved at first reading.
+   is an operator round saved at first reading.
 
 6. **Persist + checkpoint state.** Once the editorial pass is folded in (and any
    re-run confirms clean):
@@ -1646,10 +1646,10 @@ command runs — see `${CLAUDE_PLUGIN_ROOT}/commands/headless-review.md` for the
    with a cross-archetype signal line. **Mark ⚑ converged** any passage two
    independent cold reviewers flag — independent agreement with no shared session
    is the package's strongest signal. `SendUserFile` it (else a `file://` link)
-   so KTG decides which flags fold in. You do not resolve flags or pick winners;
+   so the operator decides which flags fold in. You do not resolve flags or pick winners;
    the operator gates. `[OPERATØR]`
 
-6. **Fold in by tightening, → v(n+1).** Fold the flags KTG approved into
+6. **Fold in by tightening, → v(n+1).** Fold the flags the operator approved into
    `NN-utkast.md` **by tightening** (rule 6 — close the gap, hold the length flat).
    The editor (this session) holds the pen; never paste a reviewer's direction as
    copy. If the fold-in was substantive, re-run the affected archetype on v(n+1).