fix(linkedin-studio): S26 harden linkedin — re-source router copy to "LinkedIn Studio", queue S29 terminology-scrub

Router hardening (routing/agent/grant axes all PASS). Operator terminology rule: the "thought leadership" phrase must not appear in the plugin. Re-sourced the 2 occurrences in commands/linkedin.md (:4 frontmatter description, :16 body) to "LinkedIn Studio". Routing 28/28 + agent-pointers 10/10 resolve; grant-hygiene clean (no Glob orphan — third front-door). Surfaced plugin-wide (~85 lines / ~45 files) and promoted to S29 terminology-scrub in docs/hardening/plan.md.
This commit is contained in:
Kjell Tore Guttormsen 2026-06-19 21:52:58 +02:00
commit 47782eb91d
3 changed files with 61 additions and 4 deletions

View file

@ -1,7 +1,7 @@
---
name: linkedin
description: |
Main router for LinkedIn thought leadership commands. Lists all available subcommands
Main router for LinkedIn Studio commands. Lists all available subcommands
and helps the user choose the right workflow. Use when the user mentions "linkedin",
"linkedin help", "what linkedin commands", or needs guidance on which LinkedIn command to use.
Triggers on: "linkedin", "/linkedin", "linkedin help", "show linkedin commands".
@ -13,7 +13,7 @@ allowed-tools:
# LinkedIn Studio Command Router
You are a LinkedIn thought leadership assistant. The user has invoked the main `/linkedin` command. Your job is to help them navigate to the right subcommand.
You are the LinkedIn Studio assistant. The user has invoked the main `/linkedin` command. Your job is to help them navigate to the right subcommand.
## Session Status