docs(linkedin-studio): legg N10 inn i [0.8.0] + presiser SC1-bevisets rekkevidde

To rettelser i release-notatene for v0.8.0, funnet i etterkontroll ETTER at
taggen var pushet. Taggen flyttes IKKE - v0.8.0 peker fortsatt paa f98446a.
Aa re-peke en pushet tag paa en offentlig remote er verre enn hullet den
skulle lukke.

1. N10 (0810631, konfigurerbart maalnivaa-spenn / C-8) manglet. Releasen
   inneholder 12 N-oekter; notatene foerte 11. Verifisert med enumerering i
   begge retninger: N-numre i [0.8.0] == N-numre i git log 0b34218..f98446a.
   CHANGELOG-dekning er en TELLING, og en telling skal enumereres mot ground
   truth foer release - ikke leses ut av en seksjon som ser komplett ut.

2. "proven end-to-end" om SC1-kjeden er myknet til det som faktisk ble gjort:
   CLI-lagene kjoert ekte, kommandostegene simulert, fordi plugin-kommando- og
   agentflater resolver konsument-side og ikke i utviklingsrepoet. STATE bar
   forbeholdet hele tiden; den offentlige teksten gjorde det ikke.

test-runner 270/0.

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

CHANGELOG.md

@@ -9,7 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [0.8.0] - 2026-07-27
 
-**The production line, closed.** 0.7.0 built the bridge from discovery to a scheduled edition; 0.8.0 makes the whole line hold together and, for the first time, feed back into itself. A candidate now travels id-traceably from capture to a scheduled slot with **no manual re-entry anywhere in the chain** (proven end-to-end before this release). A measurement now changes the next piece instead of dying in chat. A correction made once is enforced from then on. Voice is bound *before* prose rather than scrubbed after. The series remembers what it has already spent. And the engine finally knows your own normal well enough to **refuse a verdict** when the data is too thin — the answer that keeps everything above it honest.
+**The production line, closed.** 0.7.0 built the bridge from discovery to a scheduled edition; 0.8.0 makes the whole line hold together and, for the first time, feed back into itself. A candidate now travels id-traceably from capture to a scheduled slot with **no manual re-entry anywhere in the chain** — exercised before this release with the CLI layers run for real and the command steps simulated, since plugin command and agent surfaces resolve consumer-side rather than in the development repo. A measurement now changes the next piece instead of dying in chat. A correction made once is enforced from then on. Voice is bound *before* prose rather than scrubbed after. The series remembers what it has already spent. And the engine finally knows your own normal well enough to **refuse a verdict** when the data is too thin — the answer that keeps everything above it honest.
 
 ### Added — demand-sweep «innenfra og ut» (N7.5 / MR-F9)
 
@@ -36,6 +36,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **WebFetch on both fact agents (C-7)** — `fact-checker` and `fact-reviewer` gain `WebFetch`: quote precision (F2) and exact-figure attribution (F3) require the verbatim source text in context, not a search snippet.
 - test-runner 146 → 154 (Section 16p: 8 unconditional randsone-gate greps + self-test; anti-erosion floor 129 → 137). Domain-general; no KTG-specific values hardcoded.
 
+### Added — target level becomes a configurable axis, not a hardcoded reader (N10 / C-8)
+
+- **The hardcoded primary reader is gone** — `references/longform-quality-rules.md` judged every edition against "the non-technical line manager", one specific reader baked into a domain-general plugin. It now refers to **the user's own configured target-level span**, so "practically usable at every level" is measured against the levels *they* write for.
+- **A mandatory secondary persona at the opposite end of the span** — `config/personas.template.md`'s "primary trumps" rule let a secondary-persona NO be waved through as "signal, not failure". A secondary at the far end of the span is now required, and dismissing its NO demands an **explicit ceiling justification**. The seed library also gained a technician-end persona (a solutions developer / AI engineer): it shipped three *manager* personas and no technician, which quietly biased every gate toward one end of the very span it was supposed to test.
+- **`targetLevel` stops being a phantom field** — the plan assumed the N7 bridge already carried it into the edition state; it did not (it existed only in the trend store and a free-text mapping). Two files beyond the planned scope close the loop: an additive `articles.NN.targetLevel` slot in `config/edition-state.template.json` (default `null`, **no schemaVersion bump** — same pattern as `sourceTrendId` and `language`), and `/linkedin:newsletter` persisting the resolved level at the Step 1.5 checkpoint. `persona-reviewer` reads it and places the personas on the span, falling back to persona expertise when the field is `null`.
+- test-runner 154 → 163 (Section 16q: 9 unconditional `.md`/`.json` greps + non-vacuity self-test; anti-erosion floor 137 → 146). A vacuity bug in the new edition-state check was caught and tightened during the session — it grepped for the *word* `targetLevel`, which the `sourceTrendId` doc-string already contained, so it now pins the slot literal. (`0810631`)
+
 ### Added — series-level protection: make the retread visible before prose (N11 / C-5)
 
 - **`scripts/editions/` — series distillate (new package)** — each locked edition leaves behind the narrative units it spent (anecdotes told, arguments argued, hooks used) in `<serie>/linkedin/series-distillate.json`, beside `edition-state.json` in the **series root** — series-scoped state where the series' other state already lives, so it travels with the series and needs no slug→path map. `distil-append` (Step 8 lock) folds an edition in; a re-lock after `/linkedin:pivot` **replaces** its entry rather than duplicating it.