refactor(linkedin-studio): S29e terminology-scrub — rename thought-leadership-angles.md -> content-angles.md + all pointers

Final sub-pass of the S29 plugin-wide terminology scrub. The canonical reference file is
renamed and every functional pointer updated atomically in one commit. The file's in-file
title/headers were already FORM A-scrubbed in S29c (H1 reads "Content Angles"), so S29e is a
pure rename + pointer update — no FORM A remained in the file.

Rename: references/thought-leadership-angles.md -> references/content-angles.md (git mv).

Pointers updated (17 files, 29 occurrences) — token "thought-leadership-angles" -> "content-angles":
- references/ (2): ai-content-framework, glossary
- agents/ (7): content-repurposer, strategy-advisor, network-builder, content-planner,
  trend-spotter, video-scripter, differentiation-checker
- commands/ (6): pipeline, video, post, competitive, react, batch
- skills/ (1): linkedin-content-creation/SKILL
- docs/ (1, forward-looking): integration-test-guide

Left URØRT per the standing S29 decision (history = honest record of a past state, not a
runtime load): CHANGELOG.md, docs/hardening/log.md, docs/hardening/plan.md. STATE.md untouched
here (rewritten at session end).

Verify: no thought-leadership-angles* file remains; references/content-angles.md present; zero
residual "thought-leadership-angles" in commands/agents/references/skills/integration-test-guide;
structure gate scripts/test-runner.sh 81/0/0 exit 0.

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

commands/batch.md

@@ -40,7 +40,7 @@ Use AskUserQuestion:
 3. **Use existing plan** — Follow the weekly plan already created
 4. **Mix it up** — Diverse topics across pillars
 
-If they choose a theme, help them identify 3-5 unique angles from `references/thought-leadership-angles.md`. For timely angles, delegate to the `trend-spotter` agent — invoke it via `Task` with `subagent_type: linkedin-studio:trend-spotter` (foreground, from this command layer) — to surface trending topics and score their relevance against the user's pillars.
+If they choose a theme, help them identify 3-5 unique angles from `references/content-angles.md`. For timely angles, delegate to the `trend-spotter` agent — invoke it via `Task` with `subagent_type: linkedin-studio:trend-spotter` (foreground, from this command layer) — to surface trending topics and score their relevance against the user's pillars.
 
 ## Step 2: Plan the Batch (with Scheduling)
 
@@ -203,7 +203,7 @@ Each scheduled post has a 15-minute reminder before posting time.
 
 ## Reference Files
 
-- `${CLAUDE_PLUGIN_ROOT}/references/thought-leadership-angles.md`
+- `${CLAUDE_PLUGIN_ROOT}/references/content-angles.md`
 - `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md`
 - `${CLAUDE_PLUGIN_ROOT}/references/low-frequency-posting-strategy.md`
 - `${CLAUDE_PLUGIN_ROOT}/references/scheduling-strategy.md`

commands/competitive.md

@@ -158,6 +158,6 @@ Emphasize: The goal is inspiration and differentiation, NOT copying. Always find
 
 ## Reference Files
 
-- `${CLAUDE_PLUGIN_ROOT}/references/thought-leadership-angles.md`
+- `${CLAUDE_PLUGIN_ROOT}/references/content-angles.md`
 - `${CLAUDE_PLUGIN_ROOT}/references/linkedin-growth-playbook-2025-2026.md`
 - `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md`

commands/pipeline.md

@@ -52,7 +52,7 @@ To situate the post in the broader plan — does it fill a content-mix gap or re
 
 Once topic is chosen, create the draft:
 
-1. **Select angle** — Auto-select the strongest angle from `references/thought-leadership-angles.md` based on topic and user's expertise. Present ONE recommended angle with reasoning. Do NOT use AskUserQuestion — just proceed. If user disagrees, offer alternatives.
+1. **Select angle** — Auto-select the strongest angle from `references/content-angles.md` based on topic and user's expertise. Present ONE recommended angle with reasoning. Do NOT use AskUserQuestion — just proceed. If user disagrees, offer alternatives.
 2. **Infer format** — Default to text post. Only mention carousel/video as a note if particularly well-suited.
 3. **Write draft** — Following the structure:
    - Hook: 110-140 characters
@@ -201,7 +201,7 @@ Replace placeholders with actual post data. Set `next_planned_topic` manually if
 
 ## Reference Files
 
-- `${CLAUDE_PLUGIN_ROOT}/references/thought-leadership-angles.md`
+- `${CLAUDE_PLUGIN_ROOT}/references/content-angles.md`
 - `${CLAUDE_PLUGIN_ROOT}/references/engagement-frameworks.md`
 - `${CLAUDE_PLUGIN_ROOT}/references/algorithm-signals-reference.md`
 - `${CLAUDE_PLUGIN_ROOT}/references/linkedin-formats.md`

commands/post.md

@@ -63,9 +63,9 @@ If they provide a URL, use WebFetch to extract the content first.
 
 ## Step 2: Select Content Angle
 
-Read `references/thought-leadership-angles.md` for the 8 universal angles.
+Read `references/content-angles.md` for the 8 universal angles.
 
-**Industry-specific angles:** If `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/profile/user-profile.md` exists and has an `industry` field, check the "Industry Angle Variants" section in `thought-leadership-angles.md` for the matching industry table. Use the industry-specific starter questions and example hooks to generate more targeted angle suggestions.
+**Industry-specific angles:** If `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/profile/user-profile.md` exists and has an `industry` field, check the "Industry Angle Variants" section in `content-angles.md` for the matching industry table. Use the industry-specific starter questions and example hooks to generate more targeted angle suggestions.
 
 Select the strongest angle based on the content and user's expertise areas. Present ONE recommended angle with brief reasoning:
 
@@ -200,7 +200,7 @@ Replace placeholders with actual post data. This replaces manual YAML editing.
 
 ## Reference Files
 
-- `references/thought-leadership-angles.md` - 8 universal angles
+- `references/content-angles.md` - 8 universal angles
 - `references/engagement-frameworks.md` - Hooks, structure, CTAs
 - `references/linkedin-formats.md` - Format specifications
 - `references/algorithm-signals-reference.md` - Algorithm mechanics

commands/react.md

@@ -270,6 +270,6 @@ Same as Step 8 — run `state-updater.mjs` with actual post data.
 ## Reference Files
 
 - `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/voice-samples/authentic-voice-samples.md` — Voice matching
-- `references/thought-leadership-angles.md` — 8 universal angles
+- `references/content-angles.md` — 8 universal angles
 - `references/engagement-frameworks.md` — Hooks, structure, CTAs
 - `assets/checklists/quality-scorecard.md` — Pre-publish check

commands/video.md

@@ -73,7 +73,7 @@ Default recommendation: **60 seconds** is the 2026 sweet spot — shorter videos
 Follow the same flow as `/linkedin:post`:
 
 1. Ask what they want the video to be about (if not already clear)
-2. Read `references/thought-leadership-angles.md` for the 8 universal angles
+2. Read `references/content-angles.md` for the 8 universal angles
 3. Present 2-3 angle options via AskUserQuestion
 4. Verify topic doesn't duplicate recent posts (check state file)
 5. Confirm topic aligns with user's 5 core expertise areas
@@ -233,6 +233,6 @@ Replace placeholders with actual post data. This replaces manual YAML editing.
 - `references/video-strategy-guide.md` — Script templates, pacing, production
 - `references/linkedin-formats.md` — Video specs, algorithm, technical requirements
 - `references/engagement-frameworks.md` — Hook types, CTAs
-- `references/thought-leadership-angles.md` — 8 universal angles
+- `references/content-angles.md` — 8 universal angles
 - `references/algorithm-signals-reference.md` — Algorithm mechanics
 - `assets/checklists/quality-scorecard.md` — Pre-publish check