feat(linkedin-studio): S14 — journey layer (create/measure front-doors + 5-journey router), v4.1.0

14a's cold command-rationalization found ZERO redundancy across the 27 commands
(no defensible merge/cut), so the operator reframed S14 from "merge/cut" to
"add a journey layer over the kept atomics".

- Add /linkedin:create + /linkedin:measure — delegate-only guided front-doors
  (Read/Glob/AskUserQuestion only; route to the command that owns the work)
- Re-tier commands/linkedin.md into 5 journeys (Start/Create/Engage/Measure/Grow);
  onboarding/strategy elevated as Start/Grow front-doors; Engage = calendar+firsthour tier
- 14a honesty nits: router now lists firsthour; calendar cross-links to firsthour;
  competitive confirmed UNGATED (the claimed 1K-gating inconsistency was unfounded)
- Lockstep: EXPECT_COMMANDS 27->29, v4.0.0->4.1.0 across plugin.json / README badges /
  plugin+root CLAUDE.md / README / CHANGELOG; new README commands-badge lint guard
- 14a deliverable corrected: multiplatform entry added (26/27 -> 27/27), header counts,
  competitive nit withdrawn
- Independent /trekreview (2 Opus reviewers) raised 3 MAJORs (stale commands badge,
  router competitive self-contradiction, STATE.md count) — ALL remediated in-session;
  verdict ALLOW

Gate: test-runner.sh 74/0/0; node --test 98/98; commands=29; v4.1.0 consistent.
Additive/minor — no command removed/renamed/behavior-changed; reload registers create+measure.

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

plugins/linkedin-studio/docs/remediation/finish-plan.md

@@ -47,6 +47,21 @@ S17 (C13–C46 triage)            → ALLOW  [process complete]
 ## S14 — Command rationalization (re-opens the original command-surface Non-Goal)
 *Analysis → operator decision → execute. Nothing deleted without explicit per-command yes.*
 
+> **AMENDMENT — S14 reframed by operator decision (2026-05-30): merge/cut → journey layer.**
+> 14a's cold per-command review (`command-rationalization.md`) found **zero redundancy** —
+> no command is a defensible merge/cut candidate (the two prior consolidations already
+> removed the genuine overlaps). So instead of cutting, the operator chose to **add a
+> journey layer over the kept atomics**. The build contract is
+> **`journey-layer-design.md`** (this supersedes the 14b/14c "execute merges/cuts" bullets
+> below — there are none to execute). **Delivered:** two new guided front-doors
+> (`/linkedin:create`, `/linkedin:measure`) + the router re-tiered into five journeys
+> (Start · Create · Engage · Measure · Grow) + `onboarding`/`strategy` elevated as the
+> Start/Grow front-doors; the 27 atomic commands kept; **27 → 29 commands; v4.0.0 → v4.1.0
+> (minor/additive)**. The two 14a honesty nits real on verification were fixed (router lists
+> `firsthour`; `calendar` cross-links to it); a third (a `competitive` 1K-gating claim) was
+> withdrawn as unfounded. The **gate is unchanged**: `test-runner.sh` + `node --test` green
+> → `/trekreview` **ALLOW** (no WARN-override) → commit own files → push.
+
 - **14a Analysis (no edits):** cold per-command review of all 27 → `docs/remediation/command-rationalization.md`.
   Per command: purpose · overlap with siblings · invocation leverage (algorithmic + likely use) ·
   recommendation **keep / develop / merge→X / cut** + rationale. Delegate the cold read to an