fix(linkedin-studio): N20 — CLAUDE_PLUGIN_ROOT-normalisering av load-bearing ref-stier [skip-docs]

81 load-bearing stier i 16 kommandofiler pinnet til ${CLAUDE_PLUGIN_ROOT}/.
Rene prefikser: 81 inn / 81 ut, ingen linje lagt til eller fjernet.

FASIT-VERIFISERING (premiss-sjekk mot BASELINE, ikke bare HEAD): planens
68 linjer / 17 filer er RIKTIG mot sin egen baseline 882f6ee. HEAD ga 73/18 —
altså ekte kode-drift siden baseline (newsletter.md 11→15, calendar.md 0→1),
ikke en telle-feil som i N19.

SCOPE UTVIDET ETTER GO: planens grep (references|hooks/scripts|scripts) har en
blindsone — skills/ assets/ config/ render/ agents/ commands/ er samme defekt-
klasse og allerede anerkjent som pin-verdig av mønsteret (audit.md:24 og
competitive.md:22 pinner skills/, batch.md:214 og pipeline.md:211 pinner
assets/). Under planens scope kunne dens EGEN verifisering ikke passere:
quick.md:229-230 ville stått upinnet rett over en pinnet linje, og setup.md
(3 load-bearing Read, 0 pins) var ikke i settet i det hele tatt.
Full defektklasse: 117 linjer / 19 filer → 81 pinnet, 36 bevisst urørt.

KLASSIFISERINGSREGEL (utledet av mønsteret, ikke oppfunnet):
- PIN = stien skal åpnes/kjøres/skrives — Read/Reference/See-pekere,
  ref-fil-lister, Bash/node/npm, edit-mål.
- PROSA = stien står som sitat bak en påstand, eller som beskrivelse av
  oppførsel/plassering. Ingen inline «(see …)» er pinnet noe sted i repoet
  (0 av 25 filer) — den grensen er arvet, ikke satt her.

36 BEVISST URØRTE, tre klasser:
1. Inline sitat/attribusjon (17): carousel.md:37 · pipeline.md:70,75 ·
   newsletter.md:999,1082,1211,1433 · report.md:273 · video.md:69 ·
   react.md:115 · calendar.md:87 · profile.md:28,34 · firsthour.md:112 ·
   monetize.md:343,492 · outreach.md:922
2. Beskrivelse av oppførsel/plassering (10): newsletter.md:50,1097,1205,1694,
   1744,1944 · report.md:45 · linkedin.md:218 · import.md:121,200
3. newsletter.md fase-tabellens Tooling-kolonne (9): :100,102,105,106,111,112,
   113,115,116 — tabellen er et register, og hvert steg pinner sitt eget
   faktiske kall i brødteksten.

S13-LINTEN (M0 data-dir): alle assets/-stiene som ble pinnet står eksplisitt i
lintens NEGATIVE13-unntaksliste, og lintens egen kommentar (test-runner.sh:552)
sier at shipped read-only assets SKAL bære ${CLAUDE_PLUGIN_ROOT}.

VERIFISERING: 76 unike pinnede stier hentet ut og resolvet med cwd=/tmp —
75 finnes. Den ene som ikke gjør det, config/personas.local.md, er en
gitignored valgfri fallback («else personas.template.md») som var pinnet på
newsletter.md:205 før denne endringen. Re-grep: gjenstående 36 er utelukkende
prosa, listet over.

Alle ti suiter grønne, alle floors uendret: test-runner 270/0 (269 assertions
>= floor 251) · trends 300/0 · analytics 202/0 · hooks 191/0 · brain 134/0 ·
editions 72/0 · render 63/0 · specifics-bank 45/0 · tests 35/0 ·
contract-gate 33/0.

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

commands/quick.md

@@ -32,12 +32,12 @@ Read `~/.claude/linkedin-studio.local.md` for:
   Apply the ones that fit and name the applied directive in one line with the draft. Never edit
   or clear the section (each source manages its own rows; rows older than 60 days expire).
 
-Read `skills/linkedin-studio/SKILL.md` for:
+Read `${CLAUDE_PLUGIN_ROOT}/skills/linkedin-studio/SKILL.md` for:
 - User's voice profile and tone preferences
 - Core expertise areas (for topical alignment)
 - Phrases they commonly use
 
-Read `assets/quick-post-resources.md` for:
+Read `${CLAUDE_PLUGIN_ROOT}/assets/quick-post-resources.md` for:
 - Hooks bank
 - CTAs bank
 - Quality checklist
@@ -61,7 +61,7 @@ Only ask if truly ambiguous (no discernible intent). Otherwise, state: "This rea
 
 These 8 post types ARE the template library. Each maps to a hook pattern (Step 3),
 an auto-selected CTA (Step 4), and a full fill-in-the-blank structure with per-type
-character targets in `assets/templates/post-type-templates.md`. If the user explicitly
+character targets in `${CLAUDE_PLUGIN_ROOT}/assets/templates/post-type-templates.md`. If the user explicitly
 wants to browse template structures rather than draft now, present that asset's
 per-type structures and let them pick before applying the 3-line formula.
 
@@ -85,7 +85,7 @@ Use this structure for all quick posts:
 
 ## Step 3: Select Hook Pattern
 
-Based on post type, use appropriate hook from `assets/quick-post-resources.md`:
+Based on post type, use appropriate hook from `${CLAUDE_PLUGIN_ROOT}/assets/quick-post-resources.md`:
 
 ### Reaction Post
 - "[Industry event/news - state what happened]"
@@ -133,7 +133,7 @@ Auto-select the best CTA based on post type — do NOT ask:
 | CURATION | "Worth a read — what's your take?" |
 | ONE-LINER | "Agree or disagree?" |
 
-Reference `assets/quick-post-resources.md` for additional CTA options if the default doesn't fit.
+Reference `${CLAUDE_PLUGIN_ROOT}/assets/quick-post-resources.md` for additional CTA options if the default doesn't fit.
 
 ## Step 5: Write and Check
 
@@ -189,7 +189,7 @@ Replace placeholders with actual post data. This replaces manual YAML editing.
 
 ## Common Mistakes to Avoid
 
-From `assets/quick-post-resources.md`:
+From `${CLAUDE_PLUGIN_ROOT}/assets/quick-post-resources.md`:
 
 1. **Too many ideas** - Pick ONE. Save others for separate posts.
 2. **Burying the hook** - Lead with the most interesting element.
@@ -226,6 +226,6 @@ If during creation you realize:
 
 ## Reference Files
 
-- `assets/quick-post-resources.md` - Hooks and CTAs bank
-- `assets/templates/post-type-templates.md` - Template examples
-- `references/engagement-frameworks.md` - Hook psychology
+- `${CLAUDE_PLUGIN_ROOT}/assets/quick-post-resources.md` - Hooks and CTAs bank
+- `${CLAUDE_PLUGIN_ROOT}/assets/templates/post-type-templates.md` - Template examples
+- `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md` - Hook psychology