feat(linkedin-studio): N15 — do-next-kontrakt (recordDoNext + skrivere/lesere + forrige-utgave-kalibrering) [skip-docs]

Måling som ikke endrer neste utgave er teater: report/analyze/ab-test/48h-monitor
endte alle i chat (grep do.next = 0 i hele repoet). N15 gjør kanalen til en kontrakt.

- recordDoNext i hooks/scripts/state-updater.mjs (TDD, 17 nye tester): seksjonen
  Do-Next Directives, rader "[dato] (kilde) direktiv — evidence: peker".
  Levetid = erstatt-per-kilde + 60-dagers aldersgulv, maks 3 per skriv, additiv
  scalar last_donext_date, $-sikre replacement-funksjoner. CLI: --record-do-next.
- Skrivere: report Step 7b, analyze Step 6b, ab-test 2c.6 (kun Adopt),
  post-feedback-monitor (kun 48h-sjekken); analytics-interpreter emitterer nå
  anbefalinger på do-next-form (imperativ + evidens).
- Lesere: post/quick/batch/create Step 0 + newsletter Step 1, som i tillegg
  kalibrerer på forrige utgaves MÅLTE tall via queue-id-match (queue.json →
  analytics/posts) med eksplisitt honest-miss — aldri estimert.
- Guards: test-runner Section 16v (15 ubetingede sjekker, floor 198 → 213),
  $-safety-batteriet dekker recordDoNext (coverage-gate fanget den nye eksporten).

Suiter: test-runner 232/0, hooks 191/0, trends 300/0, brain 134/0, editions 72/0,
specifics-bank 45/0, contract-gate 33/0, tests 35/0, render 60/0.

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

commands/ab-test.md

@@ -342,6 +342,32 @@ handful of posts per variant a creator realistically gathers (well under the
 
 Update the test file status from ACTIVE to COMPLETED. Add the conclusion and recommended actions to the file.
 
+### 2c.6: Persist an Adopt verdict as a do-next directive
+
+An **Adopt** verdict (and only Adopt — "Keep A", "Inconclusive" and "Extend test" change nothing
+about the next draft) is a decision the next post must inherit. Write it to the same do-next
+channel `/linkedin:report` and `/linkedin:analyze` use, so every create surface picks it up at
+its Step 0 instead of the test result sitting unread in a file:
+
+```bash
+node --input-type=module -e "
+import { writeState, recordDoNext } from '${CLAUDE_PLUGIN_ROOT}/hooks/scripts/state-updater.mjs';
+writeState(content => recordDoNext(content, {
+  recordDate: 'YYYY-MM-DD',
+  source: 'ab-test',
+  directives: [
+    { directive: 'Open with a question hook by default', evidence: 'test hook-form (6 posts): B +38% comments, directional-strong' }
+  ]
+}));
+"
+```
+
+Carry the **directional** framing into the evidence pointer (see 2c.4 — organic volume rarely
+reaches significance); a directive that reads as proven when the signal was weak is how one
+outlier becomes a permanent rule. `recordDoNext` replaces this source's previous adopt row, so
+a newer verdict supersedes an older one automatically — and the `report`/`analyze` slots are
+untouched.
+
 ---
 
 ## Step 2d: Review Test History