feat(linkedin-studio): N24 — promo-post-motor (hook-forge + shareability-gate) [skip-docs]

Step 9 (post-lock distribution gate) får to tillegg, begge scoped til utgave-promo:

1. Hook-forge (E#7): 5-8 krok-varianter for delingsteksten. 110-140-båndet
   håndheves PER VARIANT og MÅLES (perl -CSD; awk length/wc -c teller bytes og
   lyver på æ/ø/å). Utenfor båndet = diskvalifisert, ikke rangert lavere.
   Settet må spenne minst tre krok-typer, ellers er det omskrivinger, ikke valg.
   Hver variant må spores til en påstand kroppen faktisk gjør (ingen bait).
   Ingen predicted-engagement score — et tall som påstår å vite hva som sprer
   seg er oppfunnet (N22-defektklassen); operatøren rangerer.
   Valgt variant går GJENNOM randsone-gaten, aldri utenom.

2. Shareability-gate (E#8): konverter-modus får en ANDRE binær — deling.
   «Hvem deler dette til en kollega, og hvorfor?» + RESHARE/SAVE/SEND.
   Svaret må navngi en rolle og et avsender-motiv; «nyttig for alle i tech»
   er NEI. Blokkerende: to mislykkede omramminger => operatørvalg (pivot eller
   registrert foldIn), aldri en stille passering.

Ti suiter grønne: test-runner 300/0 (287->300, +13 ubetingede; floor 268->281)
· trends 300 · analytics 202 · hooks 191 · brain 134 · editions 72 · render 63
· specifics-bank 45 · tests 35 · contract-gate 33. Begge nye compound-predikater
mutasjonstestet mot faktisk fil (fjernet literal => rød).

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

config/edition-state.template.json

@@ -21,7 +21,7 @@
       "annotation — optional annotatable review HTML for a manual pass (Step 7)",
       "visual-assets — cover (+ optional inline figures) or carousel deck: brief → generate → operator-gate → approve, BEFORE lock so build-linkedin.mjs picks them up (Step 7.5)",
       "lock-delivery — LOCK → POST.html all-in-one-place deliverable (Step 8)",
-      "hook-conversion-gate — persona gate on distribution text post-lock: would YOU click? (Step 9)",
+      "hook-conversion-gate — persona gate on distribution text post-lock: hook-forge, would YOU click?, and who forwards this and why (Step 9)",
       "scheduling — register edition in plugin queue/state for native LinkedIn scheduling (Step 10)",
       "retro — close the loop (≤5 min, AFTER scheduling): promote the pending articles.NN.foldIns with an explicit operator JA/NEI (mechanical → a contract-gate rule; judgment → the language-rules file / craft checklist), summarize the MEASURED effort from articles.NN.phaseLog, and ask ONE process-friction question. The corrections made in this edition become enforced before the next one starts (Step 11)"
     ],

config/personas.template.md

@@ -35,7 +35,8 @@ trim, or extend them per series.
   NO is **not** accepted: the text is revised until the primær reaches a clean YES.
 - **Two sweep modes** (same `persona-reviewer` agent): resonance mode (Step 6,
   BEFORE lock — «does the point land for this reader?») and conversion mode
-  (Step 9, after lock — binary «would YOU click?» on the hook only).
+  (Step 9, after lock — two binaries on the distribution copy: «would YOU click?»
+  and «who forwards this to a colleague, and why?»).
 
 ### Per-artifact personas (one or more personas per edition)