fix(linkedin-studio): N10 — konfigurerbart målnivå-spenn [skip-docs]

C-8: gjør «praktisk anvendbar på alle nivå» til en konfigurerbar gate-akse og
fjerner den hardkodede primær-personaen. 6-fils scope (KTG-valgt) — gjør
targetLevel til en EKTE ende-til-ende-dimensjon i stedet for et fantomfelt:

- references/longform-quality-rules.md: «non-technical line manager» → brukerens
  konfigurerte target-level span (domene-generelt).
- config/personas.template.md: «primær trumfer» krever nå obligatorisk sekundær i
  MOTSATT ende av spennet; sekundær-NEI kan kun avskrives som «signal, ikke svikt»
  med eksplisitt ceiling-begrunnelse. Ny tekniker-ende-seed (Persona 4,
  Løsningsutvikler/AI-ingeniør) — tidligere kun 3 leder-personas.
- config/edition-state.template.json: additivt articles.NN.targetLevel-slot
  (default null, INGEN schemaVersion-bump — samme mønster som sourceTrendId/language).
- commands/newsletter.md: persister resolvert targetLevel ved Step 1.5-checkpointet.
- agents/persona-reviewer.md: leser articles.NN.targetLevel og plasserer personaene
  på spennet (fallback til persona-ekspertise om feltet er null).

Premiss-korreksjon: planens 4-fils scope antok targetLevel fantes i edition-state
via N7-broen; det stemte ikke (fantes kun i trend-store + fritekst-mapping). +2 filer
(edition-state-slot + newsletter-persist) gjør konsumet reelt.

TDD: ny Section 16q i test-runner (9 UNCOND. .md/.json-greps + non-vacuity self-test);
en vacuity-bug i egen edition-state-check fanget og skjerpet (grep slot-literal
"targetLevel": null, ikke bare ordet — sourceTrendId-docstringen inneholder allerede
"targetLevel"). test-runner 154→163/0, anti-erosion floor 137→146. Øvrige fem suiter
uendret grønne (trends 300 · brain 134 · hooks 140 · tests 35 · render 60).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014bE7VbkmR3cqHFEeGfzgwb

commands/newsletter.md

@@ -300,7 +300,10 @@ what genuinely changes the work.
 >    point the operator confirms or edits* in the dimensions below, not a bypass of
 >    calibration:
 >    - `angle` → the edition **Angle**.
->    - `targetLevel` → the audience/tone calibration (**Audience** / **Tone**).
+>    - `targetLevel` → the audience/tone calibration (**Audience** / **Tone**); the
+>      resolved value is also persisted to `articles.NN.targetLevel` at the Step 1.5
+>      checkpoint (below) so persona-reviewer can place the personas on the configured
+>      target-level span (which end is primær, which is the mandatory secondary).
 >    - `summary` + `rationale` + `readerQuestion` / `painPoint` → seed the **Key
 >      points** and the **Leader-takeaway** (the reader-side framing this bridge
 >      exists to carry: what the reader would DO with it).
@@ -471,6 +474,12 @@ Edition brief
    - If Step 1 ran the **trend-intake bridge**, persist `articles.NN.sourceTrendId`
      (the trend id) here too — the durable provenance link Step 10 reads to auto-`act`
      the trend. Omit it (leave `null`) for a manually-started edition.
+   - Persist the resolved **`targetLevel`** (Step 1's Audience/Tone calibration; the
+     trend bridge pre-fills it from the trend record) to `articles.NN.targetLevel` — the
+     per-article position on the configured target-level span that persona-reviewer reads
+     to place the personas (which end is primær, which is the mandatory secondary). Leave
+     `null` if the operator did not resolve a level; the reader agents then fall back to
+     each persona's own `ekspertise` field.
    - Persist the resolved **`language`** (Step 1) — write it to the **top-level**
      `language` (the series/edition-level review language; there is no per-article
      `language` field) so the language-dependent review agents grade against the