fix(linkedin-studio): S12 harden firsthour — re-source ~70% stat to first 15-30 min + drop CEA mislabel

Axis-b: command attributed ~70% of reach to the first 60 min (desc + body);
SSOT algorithm-signals-reference.md:81 pins ~70% to the first 15-30 min
sub-window (golden window 60-90 min). The command even cited that SSOT, so it
contradicted its own source. Re-attributed to '15-30 minutes decide ~70%',
framing the hour as the golden window worked.

Axis-a: footer labelled engagement-frameworks.md as carrying CEA, but CEA lives
in the SSOT + engagement-coach. Dropped 'CEA' from the footer label.

Verified clean: both agents namespaced + frontmatter name/model/color match
CLAUDE.md; recordFirstHourPlan exported/additive/$-safe; delegation + hand-off
sound. test-runner.sh 81/0/0; counts 29/19/26 unchanged. FIXED, 0 deferrals.

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

commands/firsthour.md

@@ -1,7 +1,7 @@
 ---
 name: linkedin:firsthour
 description: |
-  Run the critical first hour after you publish — the window that decides ~70% of a post's
+  Run the critical first hour after you publish — its first 15–30 minutes decide ~70% of a post's
   reach. Builds a timestamped first-hour plan: a warm-up + reply-loop target list, draft
   self-comments and CEA replies in your voice, and a minute-by-minute timeline — then persists
   it to state so you can work it live. Hands off to the 48-hour monitor afterwards.
@@ -19,8 +19,9 @@ allowed-tools:
 # First Hour / Reply Loop — Post-Publish Engagement Sprint
 
 You are a LinkedIn engagement operator. A post just went live (or is about to). The first
-60 minutes set ~70% of its total reach, so this command turns that window into a concrete,
-worked plan: who to engage, what to say, and exactly when — persisted to state.
+15–30 minutes decide ~70% of its reach and the first hour is the golden window you work it,
+so this command turns that window into a concrete, worked plan: who to engage, what to say,
+and exactly when — persisted to state.
 
 ## Step 0: Load Context
 
@@ -114,5 +115,5 @@ delayed spike) with the post-feedback monitor — invoke it via `Task` with
 ## Reference Files
 
 - `${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/voice-samples/authentic-voice-samples.md` — voice matching for the draft comments
-- `references/engagement-frameworks.md` — hook types, CEA, engagement hierarchy
+- `references/engagement-frameworks.md` — hook types, engagement hierarchy
 - `references/algorithm-signals-reference.md` — first-hour weighting, signal order, timing data