@lvlup-sw/exarchos 2.0.5 → 2.0.6

package/.claude-plugin/marketplace.json

@@ -14,10 +14,10 @@
       "source": {
         "source": "npm",
         "package": "@lvlup-sw/exarchos",
-        "version": "2.0.5"
+        "version": "2.0.6"
       },
       "description": "SDLC workflows with agent team coordination, quality gates, and Graphite stacked PRs",
-      "version": "2.0.5",
+      "version": "2.0.6",
       "author": {
         "name": "Levelup Software"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "exarchos",
   "description": "SDLC workflows for Claude Code with agent team coordination, quality gates, and Graphite stacked PRs.",
-  "version": "2.0.5",
+  "version": "2.0.6",
   "author": {
     "name": "Levelup Software"
   },
@@ -31,13 +31,6 @@
       "env": {
         "WORKFLOW_STATE_DIR": "~/.claude/workflow-state"
       }
-    },
-    "graphite": {
-      "type": "stdio",
-      "command": "gt",
-      "args": [
-        "mcp"
-      ]
     }
   }
 }

package/commands/cleanup.md

@@ -30,12 +30,12 @@ Follow the cleanup skill: `@skills/cleanup/SKILL.md`
 
 Read workflow state:
 ```typescript
-mcp__exarchos__exarchos_workflow({ action: "get", featureId: "<feature-id>" })
+mcp__plugin_exarchos_exarchos__exarchos_workflow({ action: "get", featureId: "<feature-id>" })
 ```
 
 If no `$ARGUMENTS` provided, list active workflows:
 ```typescript
-mcp__exarchos__exarchos_view({ action: "pipeline" })
+mcp__plugin_exarchos_exarchos__exarchos_view({ action: "pipeline" })
 ```
 
 ### Step 2: Verify PR Merge Status
@@ -54,7 +54,7 @@ Collect:
 ### Step 3: Invoke Cleanup Action
 
 ```typescript
-mcp__exarchos__exarchos_workflow({
+mcp__plugin_exarchos_exarchos__exarchos_workflow({
   action: "cleanup",
   featureId: "<feature-id>",
   mergeVerified: true,

package/commands/debug.md

@@ -65,11 +65,11 @@ Switch from hotfix to thorough track during investigation.
 
 ### Step 1: Initialize State
 
-Initialize workflow state using `mcp__exarchos__exarchos_workflow` with `action: "init"`:
+Initialize workflow state using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "init"`:
 - Set `featureId` to `debug-<issue-slug>`
 - Set `workflowType` to "debug"
 
-Then update the track using `mcp__exarchos__exarchos_workflow` with `action: "set"`:
+Then update the track using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"`:
 - Set `track` to "hotfix" or "thorough" based on triage
 
 ### Step 2: Triage

package/commands/ideate.md

@@ -52,9 +52,9 @@ After user selects approach:
 
 ## State Management
 
-Initialize workflow state at the start using `mcp__exarchos__exarchos_workflow` with `action: "init"` and the featureId.
+Initialize workflow state at the start using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "init"` and the featureId.
 
-After saving design, update state using `mcp__exarchos__exarchos_workflow` with `action: "set"`:
+After saving design, update state using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"`:
 - Set `artifacts.design` to the design path
 - Set `phase` to "plan"
 
@@ -66,7 +66,7 @@ Save design to `docs/designs/YYYY-MM-DD-<feature>.md` and capture the path as `$
 
 After saving the design document, **auto-continue to planning** (no user confirmation here):
 
-1. Update state with design path and phase using `mcp__exarchos__exarchos_workflow` with `action: "set"`:
+1. Update state with design path and phase using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"`:
    - Set `artifacts.design` to the design document path
    - Set `phase` to "plan"
 

package/commands/plan.md

@@ -71,7 +71,7 @@ Write to `docs/plans/YYYY-MM-DD-<feature>.md`
 
 ## State Management
 
-After saving plan, update state with tasks using `mcp__exarchos__exarchos_workflow` with `action: "set"`:
+After saving plan, update state with tasks using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"`:
 - Set `artifacts.plan` to the plan path
 - Set `tasks` to an array of task objects (id, title, status, branch)
 - Set `phase` to "plan-review"
@@ -117,7 +117,7 @@ Plan-review performs delta analysis and **auto-loops** back to `/exarchos:plan`
 
 If plan-review finds missing coverage:
 
-1. Update state with gaps using `mcp__exarchos__exarchos_workflow` with `action: "set"`:
+1. Update state with gaps using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"`:
    - Set `planReview.gapsFound` to true
    - Set `planReview.gaps` to an array of gap descriptions
 
@@ -138,7 +138,7 @@ If plan-review finds complete coverage:
 
 2. **PAUSE for user input**: "Plan covers all design requirements. Approve and continue to delegation? (yes/no)"
 
-3. **On approval**, use `mcp__exarchos__exarchos_workflow` with `action: "set"`:
+3. **On approval**, use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"`:
    - Set `planReview.approved` to true
    - Set `phase` to "delegate"
 

package/commands/refactor.md

@@ -63,7 +63,7 @@ Switch from polish to overhaul if scope expands.
 
 ### Step 1: Initialize State
 
-Initialize workflow state using `mcp__exarchos__exarchos_workflow` with `action: "init"`, featureId `refactor-<slug>`, and workflowType `refactor`.
+Initialize workflow state using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "init"`, featureId `refactor-<slug>`, and workflowType `refactor`.
 
 ### Step 2: Explore
 

package/commands/resume.md

@@ -33,7 +33,7 @@ The SessionStart hook automatically verifies state matches git reality on resume
 
 ### Step 3: Load Context Summary
 
-The SessionStart hook provides workflow context automatically. Read the state file using `mcp__exarchos__exarchos_workflow` with `action: "get"` and the featureId for detailed state.
+The SessionStart hook provides workflow context automatically. Read the state file using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "get"` and the featureId for detailed state.
 
 ### Step 4: Display Context
 

package/commands/synthesize.md

@@ -90,7 +90,7 @@ After PR is created, this is a **human checkpoint** - user confirmation required
 
 ### Save State
 
-Update state using `mcp__exarchos__exarchos_workflow` with `action: "set"` and the `featureId`:
+Update state using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"` and the `featureId`:
 - Set `artifacts.pr` to the PR URL
 - Set `synthesis.prUrl` to the PR URL
 

package/dist/node_modules/electron/index.js

@@ -0,0 +1 @@
+module.exports = {};

package/dist/node_modules/electron/package.json

@@ -0,0 +1 @@
+{"name":"electron","version":"0.0.0","main":"index.js"}

package/dist/node_modules/playwright-core/index.js

@@ -0,0 +1 @@
+module.exports = {};

package/dist/node_modules/playwright-core/package.json

@@ -0,0 +1 @@
+{"name":"playwright-core","version":"0.0.0","main":"index.js"}

package/hooks/hooks.json

@@ -19,7 +19,7 @@
       }]
     }],
     "PreToolUse": [{
-      "matcher": "mcp__exarchos__.*",
+      "matcher": "mcp__(plugin_exarchos_)?exarchos__.*",
       "hooks": [{
         "type": "command",
         "command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/exarchos-cli.js\" guard",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lvlup-sw/exarchos",
-  "version": "2.0.5",
+  "version": "2.0.6",
   "description": "Governed SDLC workflows for Claude Code — agent orchestration, quality gates, and Graphite stacked PRs",
   "type": "module",
   "bin": {
@@ -9,6 +9,7 @@
   "files": [
     "dist/exarchos-mcp.js",
     "dist/exarchos-cli.js",
+    "dist/node_modules",
     "commands",
     "skills",
     "rules",
@@ -25,7 +26,7 @@
   ],
   "scripts": {
     "build": "tsc && bun run build:mcp && bun run build:cli",
-    "build:cli": "bun build servers/exarchos-mcp/src/cli.ts --outfile dist/exarchos-cli.js --target node --external playwright-core --external electron",
+    "build:cli": "bun run scripts/build-cli.ts",
     "build:mcp": "bun build servers/exarchos-mcp/src/index.ts --outfile dist/exarchos-mcp.js --target node --minify",
     "prepare": "tsc",
     "bench": "cd servers/exarchos-mcp && npx vitest bench",

package/scripts/build-cli.ts

@@ -0,0 +1,28 @@
+#!/usr/bin/env bun
+/**
+ * Build script for the Exarchos CLI bundle.
+ *
+ * 1. Bundles with --external for playwright-core and electron (large, unused)
+ * 2. Creates stub node_modules so the external imports resolve at runtime
+ *
+ * playwright-core and electron are transitive Azure SDK deps, never used.
+ */
+import { $ } from 'bun';
+import { mkdirSync, writeFileSync } from 'node:fs';
+import { join } from 'node:path';
+
+// Step 1: Bundle with externals
+await $`bun build servers/exarchos-mcp/src/cli.ts --outfile dist/exarchos-cli.js --target node --external playwright-core --external electron`;
+
+// Step 2: Create stub node_modules for the externals
+const stubs = ['playwright-core', 'electron'];
+const stubDir = join('dist', 'node_modules');
+
+for (const pkg of stubs) {
+  const dir = join(stubDir, pkg);
+  mkdirSync(dir, { recursive: true });
+  writeFileSync(join(dir, 'package.json'), JSON.stringify({ name: pkg, version: '0.0.0', main: 'index.js' }));
+  writeFileSync(join(dir, 'index.js'), 'module.exports = {};');
+}
+
+console.log('  Stubs created for:', stubs.join(', '));

package/skills/brainstorming/SKILL.md

@@ -73,7 +73,7 @@ This skill manages workflow state for context persistence.
 
 ### On Start (before Phase 1)
 
-Initialize workflow state using `mcp__exarchos__exarchos_workflow` with `action: "init"` and the featureId.
+Initialize workflow state using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "init"` and the featureId.
 
 This creates a state file tracked by the MCP server.
 

package/skills/cleanup/SKILL.md

@@ -34,12 +34,12 @@ Activate this skill when:
 
 Read workflow state to get current phase and metadata:
 ```typescript
-mcp__exarchos__exarchos_workflow({ action: "get", featureId: "<id>" })
+mcp__plugin_exarchos_exarchos__exarchos_workflow({ action: "get", featureId: "<id>" })
 ```
 
 If featureId not provided, use pipeline view to list active workflows:
 ```typescript
-mcp__exarchos__exarchos_view({ action: "pipeline" })
+mcp__plugin_exarchos_exarchos__exarchos_view({ action: "pipeline" })
 ```
 
 ### 2. Verify Merge Status
@@ -65,7 +65,7 @@ For detailed verification guidance, see `references/merge-verification.md`.
 
 Call the MCP cleanup action with collected data:
 ```typescript
-mcp__exarchos__exarchos_workflow({
+mcp__plugin_exarchos_exarchos__exarchos_workflow({
   action: "cleanup",
   featureId: "<id>",
   mergeVerified: true,
@@ -115,7 +115,7 @@ Output summary:
 
 Use `dryRun: true` to preview what cleanup would do without modifying state:
 ```typescript
-mcp__exarchos__exarchos_workflow({
+mcp__plugin_exarchos_exarchos__exarchos_workflow({
   action: "cleanup",
   featureId: "<id>",
   mergeVerified: true,

package/skills/debug/references/troubleshooting.md

@@ -7,15 +7,15 @@ name: troubleshooting
 ## MCP Tool Call Failed
 If an Exarchos MCP tool returns an error:
 1. Check the error message -- it usually contains specific guidance
-2. Verify the workflow state exists: call `mcp__exarchos__exarchos_workflow` with `action: "get"` and the featureId
+2. Verify the workflow state exists: call `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "get"` and the featureId
 3. If "version mismatch": another process updated state -- retry the operation
-4. If state is corrupted: call `mcp__exarchos__exarchos_workflow` with `action: "cancel"` and `dryRun: true`
+4. If state is corrupted: call `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "cancel"` and `dryRun: true`
 
 ## State Desync
 If workflow state doesn't match git reality:
 1. The SessionStart hook runs reconciliation automatically on resume
 2. If manual check needed: compare state file with `git log` and branch state
-3. Update state via `mcp__exarchos__exarchos_workflow` with `action: "set"` to match git truth
+3. Update state via `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"` to match git truth
 
 ## Investigation Timeout (Hotfix Track)
 If 15-minute investigation timer expires without root cause:
@@ -25,7 +25,7 @@ If 15-minute investigation timer expires without root cause:
 
 ## Track Switching
 If hotfix track reveals complexity requiring thorough investigation:
-1. Call `mcp__exarchos__exarchos_workflow` with `action: "set"` to update track to "thorough"
+1. Call `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"` to update track to "thorough"
 2. Previous investigation findings carry over
 3. RCA phase begins after investigation completes
 
@@ -33,12 +33,12 @@ If hotfix track reveals complexity requiring thorough investigation:
 
 When Exarchos MCP tools are available, emit events throughout the debug workflow:
 
-1. **At workflow start (triage):** `mcp__exarchos__exarchos_event` with `action: "append"` -> `workflow.started` with workflowType "debug", urgency
-2. **On track selection:** `mcp__exarchos__exarchos_event` with `action: "append"` -> `phase.transitioned` with selected track (hotfix/thorough)
-3. **On each phase transition:** `mcp__exarchos__exarchos_event` with `action: "append"` -> `phase.transitioned` from->to
+1. **At workflow start (triage):** `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` -> `workflow.started` with workflowType "debug", urgency
+2. **On track selection:** `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` -> `phase.transitioned` with selected track (hotfix/thorough)
+3. **On each phase transition:** `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` -> `phase.transitioned` from->to
 4. **Thorough track stacking:** Handled by `/exarchos:synthesize` (Graphite stack submission)
 5. **Hotfix track commit:** Single `gt create -m "fix: <description>"` -- no multi-branch stacking needed
-6. **On complete:** `mcp__exarchos__exarchos_event` with `action: "append"` -> `phase.transitioned` to "completed"
+6. **On complete:** `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` -> `phase.transitioned` to "completed"
 
 ## Performance Notes
 

package/skills/delegation/references/fix-mode.md

@@ -16,7 +16,7 @@ Or auto-invoked after review failures.
 
 ## Fix Mode Process
 
-1. **Read failure details** from state using `mcp__exarchos__exarchos_workflow` with `action: "get"`:
+1. **Read failure details** from state using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "get"`:
    - Query `reviews` for review failures
 
 2. **Extract fix tasks** from failure reports:

package/skills/delegation/references/state-management.md

@@ -1,6 +1,6 @@
 # Delegation State Management
 
-State update patterns for workflow state during delegation. Use `mcp__exarchos__exarchos_workflow` for all mutations.
+State update patterns for workflow state during delegation. Use `mcp__plugin_exarchos_exarchos__exarchos_workflow` for all mutations.
 
 ## Read Tasks from State
 

package/skills/delegation/references/worktree-enforcement.md

@@ -41,7 +41,7 @@ bash scripts/setup-worktree.sh \
 
 ## Worktree State Tracking
 
-Track worktrees in the workflow state file using `mcp__exarchos__exarchos_workflow` with `action: "set"`:
+Track worktrees in the workflow state file using `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"`:
 - Set `worktrees.<worktree-id>` to an object containing `branch`, `status`, and either `taskId` (single task) or `tasks` (array of task IDs for multi-task worktrees)
 
 ## Implementer Prompt Requirements

package/skills/implementation-planning/SKILL.md

@@ -27,7 +27,7 @@ Activate this skill when:
 
 ## Revision Mode (--revise flag)
 
-When invoked with `--revise`, plan-review found gaps. Read `.planReview.gaps` from state, re-read the design, add tasks to address each gap, update the plan file, then clear gaps via `mcp__exarchos__exarchos_workflow` `action: "set"`.
+When invoked with `--revise`, plan-review found gaps. Read `.planReview.gaps` from state, re-read the design, add tasks to address each gap, update the plan file, then clear gaps via `mcp__plugin_exarchos_exarchos__exarchos_workflow` `action: "set"`.
 
 ### Revision Loop Guard
 

package/skills/refactor/SKILL.md

@@ -151,7 +151,7 @@ Full state schema:
 
 ## Track Switching
 
-If scope expands beyond polish limits during explore or brief phase, use `mcp__exarchos__exarchos_workflow` with `action: "set"` to set `track` to "overhaul" and update `explore.scopeAssessment.recommendedTrack`.
+If scope expands beyond polish limits during explore or brief phase, use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"` to set `track` to "overhaul" and update `explore.scopeAssessment.recommendedTrack`.
 
 **Scope thresholds:** If >5 files affected OR changes cross module boundaries -> recommend overhaul track.
 
@@ -190,7 +190,7 @@ Output: "Scope expanded beyond polish limits. Switching to overhaul track."
 
 When Exarchos MCP tools are available, emit events throughout the refactor workflow:
 
-1. **At workflow start (explore):** `mcp__exarchos__exarchos_event` with `action: "append"` → `workflow.started` with workflowType "refactor"
+1. **At workflow start (explore):** `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` → `workflow.started` with workflowType "refactor"
 2. **On track selection:** Auto-emitted by `exarchos_workflow` `set` when `phase` is provided — emits `workflow.transition` with selected track (polish/overhaul)
 3. **On each phase transition:** Auto-emitted by `exarchos_workflow` `set` when `phase` is provided — emits `workflow.transition` with from/to/trigger/featureId
 4. **Overhaul track stacking:** Handled by `/delegate` (subagents use `gt create` per implementer prompt)

package/skills/refactor/phases/auto-chain.md

@@ -165,7 +165,7 @@ polish:implement → [scope expands] → overhaul:plan
 Auto-chain handles this via MCP tools:
 
 ```text
-# When scope expands during implement, use mcp__exarchos__exarchos_workflow with action: "set":
+# When scope expands during implement, use mcp__plugin_exarchos_exarchos__exarchos_workflow with action: "set":
 # 1. First call: Set updates
 updates: { "implement.switchReason": "<reason>", "implement.switchedAt": "<ISO8601>" }
 

package/skills/shepherd/SKILL.md

@@ -44,7 +44,7 @@ Gather the current state of all PRs in the stack. See `references/assess-checkli
 
 **Read PR URLs from workflow state:**
 ```
-mcp__exarchos__exarchos_workflow({ action: "get", featureId: "<id>", fields: ["synthesis", "artifacts"] })
+mcp__plugin_exarchos_exarchos__exarchos_workflow({ action: "get", featureId: "<id>", fields: ["synthesis", "artifacts"] })
 ```
 
 **For each PR, check four dimensions:**
@@ -203,7 +203,7 @@ Track shepherd progress in the workflow state under the `shepherd` field.
 ### Initialize Shepherd
 
 ```
-mcp__exarchos__exarchos_workflow({
+mcp__plugin_exarchos_exarchos__exarchos_workflow({
   action: "set",
   featureId: "<id>",
   updates: {
@@ -222,7 +222,7 @@ mcp__exarchos__exarchos_workflow({
 
 After each assess cycle:
 ```
-mcp__exarchos__exarchos_workflow({
+mcp__plugin_exarchos_exarchos__exarchos_workflow({
   action: "set",
   featureId: "<id>",
   updates: {
@@ -253,7 +253,7 @@ mcp__exarchos__exarchos_workflow({
 ### Record Approval Request
 
 ```
-mcp__exarchos__exarchos_workflow({
+mcp__plugin_exarchos_exarchos__exarchos_workflow({
   action: "set",
   featureId: "<id>",
   updates: {
@@ -293,10 +293,10 @@ mcp__exarchos__exarchos_workflow({
 
 When Exarchos MCP tools are available:
 
-1. **On shepherd start:** `mcp__exarchos__exarchos_event` with `action: "append"` — event type `shepherd.started` with PR URLs and iteration count
-2. **On each iteration:** `mcp__exarchos__exarchos_event` with `action: "append"` — event type `shepherd.iteration` with assessment results and actions taken
-3. **On approval request:** `mcp__exarchos__exarchos_event` with `action: "append"` — event type `shepherd.approval_requested` with approver list
-4. **On completion:** `mcp__exarchos__exarchos_event` with `action: "append"` — event type `shepherd.completed` with total iterations and final status
+1. **On shepherd start:** `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` — event type `shepherd.started` with PR URLs and iteration count
+2. **On each iteration:** `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` — event type `shepherd.iteration` with assessment results and actions taken
+3. **On approval request:** `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` — event type `shepherd.approval_requested` with approver list
+4. **On completion:** `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` — event type `shepherd.completed` with total iterations and final status
 
 ## Troubleshooting
 

package/skills/shepherd/references/assess-checklist.md

@@ -6,7 +6,7 @@ Detailed steps for gathering PR status during each shepherd iteration.
 
 Read PR URLs from workflow state:
 ```
-mcp__exarchos__exarchos_workflow({ action: "get", featureId: "<id>", fields: ["synthesis", "artifacts"] })
+mcp__plugin_exarchos_exarchos__exarchos_workflow({ action: "get", featureId: "<id>", fields: ["synthesis", "artifacts"] })
 ```
 
 Extract PR numbers from URLs (e.g., `https://github.com/owner/repo/pull/123` → `123`).

package/skills/synthesis/SKILL.md

@@ -65,7 +65,7 @@ See `references/troubleshooting.md` for test failures, PR check failures, and me
 
 ## State Management
 
-Call `mcp__exarchos__exarchos_workflow` for all state operations. Full parameter reference: `@skills/workflow-state/SKILL.md` § Update State.
+Call `mcp__plugin_exarchos_exarchos__exarchos_workflow` for all state operations. Full parameter reference: `@skills/workflow-state/SKILL.md` § Update State.
 
 ### Read Task State
 

package/skills/synthesis/references/troubleshooting.md

@@ -77,15 +77,15 @@ If the user receives PR review comments:
 ## MCP Tool Call Failed
 If an Exarchos MCP tool returns an error:
 1. Check the error message -- it usually contains specific guidance
-2. Verify the workflow state exists: call `mcp__exarchos__exarchos_workflow` with `action: "get"` and the featureId
+2. Verify the workflow state exists: call `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "get"` and the featureId
 3. If "version mismatch": another process updated state -- retry the operation
-4. If state is corrupted: call `mcp__exarchos__exarchos_workflow` with `action: "cancel"` and `dryRun: true`
+4. If state is corrupted: call `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "cancel"` and `dryRun: true`
 
 ## State Desync
 If workflow state doesn't match git reality:
 1. The SessionStart hook runs reconciliation automatically on resume
 2. If manual check needed: compare state file with `git log` and branch state
-3. Update state via `mcp__exarchos__exarchos_workflow` with `action: "set"` to match git truth
+3. Update state via `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"` to match git truth
 
 ## PR Creation Failed
 If `gt submit` fails:
@@ -104,9 +104,9 @@ If `gt restack` encounters conflicts:
 
 When Exarchos MCP tools are available:
 
-1. **After stack submission:** Call `mcp__exarchos__exarchos_event` with `action: "append"` with event type `stack.enqueued` including PR numbers from `gt log --short`
+1. **After stack submission:** Call `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` with event type `stack.enqueued` including PR numbers from `gt log --short`
 2. **Monitor merge status:** Use `mcp__graphite__run_gt_cmd` with `["log", "--short"]` to check stack/PR status
-3. **On successful merge:** Call `mcp__exarchos__exarchos_event` with `action: "append"` with event type `phase.transitioned` to mark workflow complete
+3. **On successful merge:** Call `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` with event type `phase.transitioned` to mark workflow complete
 
 ## Performance Notes
 

package/skills/workflow-state/SKILL.md

@@ -48,7 +48,7 @@ For full MCP tool signatures, error handling, and anti-patterns, see `references
 
 ### Initialize State
 
-At the start of `/exarchos:ideate`, use `mcp__exarchos__exarchos_workflow` with `action: "init"` with:
+At the start of `/exarchos:ideate`, use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "init"` with:
 - `featureId`: the workflow identifier (e.g., `"user-authentication"`)
 - `workflowType`: one of `"feature"`, `"debug"`, `"refactor"`
 
@@ -56,7 +56,7 @@ This creates a new state file with phase "ideate".
 
 ### Read State
 
-Use `mcp__exarchos__exarchos_workflow` with `action: "get"` and `featureId`:
+Use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "get"` and `featureId`:
 
 - **Full state**: Call with just `featureId`
 - **Specific field**: Add `query` for dot-path lookup (e.g., `query: "phase"`, `query: "tasks"`)
@@ -66,7 +66,7 @@ Field projection via `fields` returns only the requested top-level keys, reducin
 
 ### Update State
 
-Use `mcp__exarchos__exarchos_workflow` with `action: "set"` with `featureId` and either `updates`, `phase`, or both:
+Use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"` with `featureId` and either `updates`, `phase`, or both:
 
 - **Update phase**: `phase: "delegate"`
 - **Set artifact path**: `updates: { "artifacts.design": "docs/designs/2026-01-05-feature.md" }`
@@ -78,7 +78,7 @@ Worktree status values: `'active' | 'merged' | 'removed'`
 
 ### Get Summary
 
-For context restoration after summarization, use `mcp__exarchos__exarchos_workflow` with `action: "get"` and `featureId`. This outputs a minimal summary suitable for rebuilding orchestrator context.
+For context restoration after summarization, use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "get"` and `featureId`. This outputs a minimal summary suitable for rebuilding orchestrator context.
 
 ### Reconcile State
 
@@ -168,19 +168,19 @@ Key sections:
 ### MCP Tool Call Failed
 If an Exarchos MCP tool returns an error:
 1. Check the error message — it usually contains specific guidance
-2. Verify the workflow state exists: call `mcp__exarchos__exarchos_workflow` with `action: "get"` and the featureId
+2. Verify the workflow state exists: call `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "get"` and the featureId
 3. If "version mismatch": another process updated state — retry the operation
-4. If state is corrupted: call `mcp__exarchos__exarchos_workflow` with `action: "cancel"` and `dryRun: true`
+4. If state is corrupted: call `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "cancel"` and `dryRun: true`
 
 ### State Desync
 If workflow state doesn't match git reality:
 1. The SessionStart hook runs reconciliation automatically on resume
 2. If manual check needed: compare state file with `git log` and branch state
-3. Update state via `mcp__exarchos__exarchos_workflow` with `action: "set"` to match git truth
+3. Update state via `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"` to match git truth
 
 ### Checkpoint File Missing
 If the PreCompact hook can't find state to checkpoint:
-1. Verify a workflow is active: call `mcp__exarchos__exarchos_workflow` with `action: "get"` and the featureId
+1. Verify a workflow is active: call `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "get"` and the featureId
 2. If no active workflow: the hook will silently skip (expected behavior)
 3. If workflow exists but checkpoint fails: check disk space and permissions
 
@@ -193,18 +193,18 @@ If state references branches or worktrees that no longer exist:
 ### Multiple Active Workflows
 If multiple workflow state files exist:
 1. The system uses the most recently updated active (non-completed) workflow
-2. Use `mcp__exarchos__exarchos_workflow` with `action: "cancel"` and `dryRun: true` on stale workflows to preview cleanup
+2. Use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "cancel"` and `dryRun: true` on stale workflows to preview cleanup
 3. Cancel stale workflows before starting new ones
 
 ## Example Workflow
 
-1. **Start new workflow**: Use `mcp__exarchos__exarchos_workflow` with `action: "init"` with `featureId: "user-authentication"`, `workflowType: "feature"`
+1. **Start new workflow**: Use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "init"` with `featureId: "user-authentication"`, `workflowType: "feature"`
 
-2. **After design phase**: Use `mcp__exarchos__exarchos_workflow` with `action: "set"` with:
+2. **After design phase**: Use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"` with:
    - `featureId: "user-authentication"`
    - `phase: "plan"`
    - `updates: { "artifacts.design": "docs/designs/2026-01-05-user-auth.md" }`
 
-3. **Check state**: Use `mcp__exarchos__exarchos_workflow` with `action: "get"` with `featureId: "user-authentication"`
+3. **Check state**: Use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "get"` with `featureId: "user-authentication"`
 
-4. **Resume after context loss**: Use `mcp__exarchos__exarchos_workflow` with `action: "get"` with `featureId: "user-authentication"` to get context restoration output
+4. **Resume after context loss**: Use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "get"` with `featureId: "user-authentication"` to get context restoration output

package/skills/workflow-state/references/mcp-tool-reference.md

@@ -2,7 +2,7 @@
 
 Detailed tool usage, methods, and anti-patterns for all installed MCP servers.
 
-## Exarchos (`mcp__exarchos__*`)
+## Exarchos (`mcp__plugin_exarchos_exarchos__*`)
 
 Unified MCP server for workflow orchestration, event sourcing, CQRS views, and task coordination. **Always use for workflow tracking.** Exposes 5 composite tools with action discriminators. Note: inter-agent messaging uses Claude Code's native Agent Teams, not Exarchos.
 
@@ -10,11 +10,11 @@ Unified MCP server for workflow orchestration, event sourcing, CQRS views, and t
 
 | Tool | Actions | When to Use |
 |------|---------|-------------|
-| `mcp__exarchos__exarchos_workflow` | `init`, `get`, `set`, `cancel`, `cleanup` | Workflow CRUD: starting workflows, reading/updating state, cancelling abandoned workflows, resolving merged workflows |
-| `mcp__exarchos__exarchos_event` | `append`, `query` | Event sourcing: recording workflow events, reading event history |
-| `mcp__exarchos__exarchos_orchestrate` | `task_claim`, `task_complete`, `task_fail` | Task coordination and lifecycle |
-| `mcp__exarchos__exarchos_view` | `pipeline`, `tasks`, `workflow_status`, `stack_status`, `stack_place` | CQRS materialized views for read-optimized queries |
-| `mcp__exarchos__exarchos_sync` | `now` | Force sync of materialized views |
+| `mcp__plugin_exarchos_exarchos__exarchos_workflow` | `init`, `get`, `set`, `cancel`, `cleanup` | Workflow CRUD: starting workflows, reading/updating state, cancelling abandoned workflows, resolving merged workflows |
+| `mcp__plugin_exarchos_exarchos__exarchos_event` | `append`, `query` | Event sourcing: recording workflow events, reading event history |
+| `mcp__plugin_exarchos_exarchos__exarchos_orchestrate` | `task_claim`, `task_complete`, `task_fail` | Task coordination and lifecycle |
+| `mcp__plugin_exarchos_exarchos__exarchos_view` | `pipeline`, `tasks`, `workflow_status`, `stack_status`, `stack_place` | CQRS materialized views for read-optimized queries |
+| `mcp__plugin_exarchos_exarchos__exarchos_sync` | `now` | Force sync of materialized views |
 
 ### Workflow Tool Actions
 
@@ -104,7 +104,7 @@ A compound state's fix cycle limit was reached. Escalate to user or cancel the w
 | Don't | Do Instead |
 |-------|------------|
 | Use `gh pr create` or `create_pull_request` | Use Graphite `gt submit --no-interactive --publish --merge-when-ready` for ALL PR creation |
-| Manually edit workflow state JSON | Use `mcp__exarchos__exarchos_workflow` with `action: "set"` |
+| Manually edit workflow state JSON | Use `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"` |
 | Use `git commit` or `git push` | Use `gt create` + `gt submit --no-interactive --publish --merge-when-ready` |
 | Skip state reconciliation on resume | The SessionStart hook handles reconciliation automatically |