refactor: remove legacy orchestration skill artifacts

docs/lab-notes/2026-03-18-freshell-feature-research.md

@@ -78,7 +78,7 @@ Commands: `new-tab`, `list-tabs`, `select-tab`, `kill-tab`, `rename-tab`, `split
 
 **Design spec:** `TMUX-SEMANTICS-PROPOSAL.md` (775 lines). Transport is HTTP+token, not Unix sockets.
 
-**Orchestration skill:** `.claude/skills/freshell-orchestration/SKILL.md` provides agent guidance for CLI automation.
+**Orchestration surface:** the `freshell` MCP tool in `server/mcp/freshell-tool.ts` provides the canonical automation guidance and action reference.
 
 ---
 

docs/plans/2026-02-22-screenshot-commands.md

@@ -1286,11 +1286,11 @@ git commit -m "test+fix(screenshot): add integration coverage for focus-preservi
 
 ---
 
-### Task 8: Update User-Facing Docs (Skill + Mock UI)
+### Task 8: Update User-Facing Docs (MCP Tool + Mock UI)
 
 **Files:**
 - Modify: `docs/index.html`
-- Rewrite: `.claude/skills/freshell-orchestration/SKILL.md` (or the canonical skill path used in this repo/session)
+- Rewrite: `server/mcp/freshell-tool.ts` (the canonical MCP instruction source used in this repo/session)
 
 **Step 1: Write the failing doc check (manual checklist)**
 
@@ -1322,8 +1322,8 @@ Required sections:
 **Step 3: Commit**
 
 ```bash
-git add docs/index.html .claude/skills/freshell-orchestration/SKILL.md
-git commit -m "docs: update screenshot command guidance in mock UI and tmux-style skill"
+git add docs/index.html server/mcp/freshell-tool.ts
+git commit -m "docs: update screenshot command guidance in mock UI and freshell MCP help"
 ```
 
 ---

docs/plans/2026-02-27-freshclaude-plugin-injection-design.md

@@ -2,7 +2,7 @@
 
 ## Problem
 
-Freshclaude sessions need to load specific skills (via plugins) at creation time. The immediate use case is ensuring every freshclaude session has `freshell-orchestration` available. The future use case is custom pane types (e.g., "kilroy") that wrap freshclaude and inject skills from external repos.
+Freshclaude sessions may need to load explicit Claude SDK plugin bundles at creation time. Freshell orchestration is no longer one of them: the canonical orchestration surface is the `freshell` MCP tool, not a default plugin or skill path.
 
 ## Design
 
@@ -21,16 +21,15 @@ ClaudeChatPaneContent.plugins: string[]    (absolute paths)
 - Add `plugins?: string[]` — array of absolute paths to plugin directories
 
 **2. `AppSettings.freshclaude`** (`src/store/types.ts`)
-- Add `defaultPlugins?: string[]` — default plugin paths for new sessions
-- Server resolves `freshell-orchestration` to its absolute path as the fallback default
+- Add `defaultPlugins?: string[]` — default plugin paths for new sessions when the user explicitly wants extra Claude SDK plugins
 
 **3. WS Protocol** (`shared/ws-protocol.ts`)
 - Add `plugins: z.array(z.string()).optional()` to `SdkCreateSchema`
 
 **4. `SdkBridge.createSession()`** (`server/sdk-bridge.ts`)
 - Accept `plugins?: string[]` in options
 - Map to `plugins: paths.map(p => ({ type: 'local' as const, path: p }))` in the `query()` call
-- Default: `[path.resolve(projectRoot, '.claude/plugins/freshell-orchestration')]`
+- No implicit orchestration plugin default; Freshell orchestration comes from MCP
 
 **5. WS Handler** (`server/ws-handler.ts`)
 - Pass `m.plugins` through to `sdkBridge.createSession()`
@@ -49,5 +48,5 @@ ClaudeChatPaneContent.plugins: string[]    (absolute paths)
 
 ### Default Behavior
 
-- Every freshclaude session gets `freshell-orchestration` loaded by default
+- Every freshclaude session gets Freshell orchestration through the `freshell` MCP tool, while explicit plugin bundles remain opt-in
 - This is additive — the session still discovers project-level skills from its CWD normally