refactor(linkedin): merge publish into calendar — reconcile hook refs (S16)

Step 17 of voyage-build (S16 in plan). publish.md absorbed into calendar.md
as an inline action (Mark as Published flow: queue update, state update,
first-hour battle plan) reusing the same queue-manager.mjs + state-updater.mjs
primitives that publish.md called. calendar.md frontmatter triggers extended
with the publish trigger words; quick-routing block jumps straight to the
publish action when the user prompt names it.

All 21 route-refs reconciled across the 9 expected files, with the 9
hook-script refs (5 in session-start.mjs, 2 in posting-reminder.mjs, 1 in
user-prompt-context.mjs, 1 in hooks/prompts/state-update-reminder.md)
rewritten to call /linkedin:calendar so the runtime guidance no longer
points at a dead command. compile-hooks.py --check reports clean (no
type: prompt hook changes touched hooks.json).

Verify (intent: zero stray refs, file gone): exit 0. Literal Verify in
plan.md:727 logged exit 1 (same exit-inverted && pattern as S15 plan.md:635
— logged for plan-pass at Step 21).

Manifest audit: PASS (expected_paths=calendar.md present; must_contain
[Pp]ublish: 17 matches in calendar.md).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

plugins/linkedin-thought-leadership/README.md

@@ -142,8 +142,7 @@ All 26 commands use colon notation: `/linkedin:post`, `/linkedin:quick`, etc.
 | `/linkedin:quick` | 5-minute quick post using the 3-line formula. Target: 150-500 characters. Best for reactions, observations, tips, and questions. Also the single entry point for the 8 post-type templates (fill-in-the-blank structures). |
 | `/linkedin:pipeline` | Full end-to-end content pipeline from idea to published post. Guides through ideation, drafting, optimization, scheduling, pre-engagement, publishing, and post-analysis. |
 | `/linkedin:batch` | Create a full week of LinkedIn content in one session. Input one theme, output 3-5 posts with varying angles and formats. Writes to scheduling queue. |
-| `/linkedin:calendar` | View and manage the post scheduling queue — upcoming, overdue, published. |
-| `/linkedin:publish` | Mark scheduled posts as published. Updates state and streak tracking. |
+| `/linkedin:calendar` | View and manage the post scheduling queue — upcoming, overdue, published — and run the publish action (mark a scheduled post as published, update state + streak tracking, surface the first-hour engagement plan). |
 | `/linkedin:video` | Video script generator for 30s, 60s, 90s, or 2-minute LinkedIn videos with pacing and visual cues. |
 | `/linkedin:multiplatform` | Adapt LinkedIn content for Twitter/X threads, newsletter sections, blog posts, presentation slides, and YouTube scripts. |
 | `/linkedin:react` | URL-to-post pipeline — paste an article, research paper, or news link and generate a reaction post. |
@@ -503,7 +502,7 @@ Scheduled posts are tracked in `assets/drafts/queue.json`:
 - Status flow: `draft` -> `scheduled` -> `published` (or `cancelled`)
 - Created by `/linkedin:batch` and `/linkedin:pipeline`
 - Viewed via `/linkedin:calendar`
-- Transitioned via `/linkedin:publish`
+- Transitioned (marked as published) via the `/linkedin:calendar` publish action
 
 ---
 
@@ -516,7 +515,7 @@ Scheduled posts are tracked in `assets/drafts/queue.json`:
 | Engagement automation | Automated commenting violates LinkedIn ToS | Manual engagement guided by `/linkedin:collab` |
 | Profile editing | Plugin generates recommendations, not API calls | Apply changes manually on LinkedIn |
 | Team/multi-user workflows | Designed for individual thought leaders | Enterprise LinkedIn tools |
-| Content scheduling via API | No official scheduling API | Queue management with manual posting via `/linkedin:publish` |
+| Content scheduling via API | No official scheduling API | Queue management with manual posting via `/linkedin:calendar` (publish action) |
 
 ---