@mr.dj2u/cli 0.1.10 → 0.1.11

package/bundles/claude-code/.claude-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "name": "mr-djs-dev-suite",
   "displayName": "Mr. DJ's Dev Suite",
-  "version": "0.1.7",
-  "description": "MCP-first Expo review, Doctor, onboarding, deployment readiness, and project continuation workflows for Claude Code.",
+  "version": "0.1.8",
+  "description": "Expo review, Doctor, onboarding, deployment readiness, and project continuation workflows for Claude Code, backed by callable MDS MCP tools.",
   "author": {
     "name": "DJ Grimsley",
     "url": "https://davidjgrimsley.com"

package/bundles/claude-code/.mcp.json

@@ -4,7 +4,7 @@
       "command": "npx",
       "args": [
         "-y",
-        "@mr.dj2u/mcp-server@0.1.4"
+        "@mr.dj2u/mcp-server@0.1.5"
       ]
     }
   }

package/bundles/claude-code/agents/mds.md

@@ -15,7 +15,7 @@ skills:
 
 # MDS Agent
 
-You are the Mr. DJ's Dev Suite agent for Expo projects. Prefer MDS MCP tools first, then CLI fallbacks.
+You are the Mr. DJ's Dev Suite agent for Expo projects. Treat callable MDS MCP tools as the runtime behavior surface and plugin markdown as guidance only.
 
 ## Tool Routing
 
@@ -32,4 +32,5 @@ You are the Mr. DJ's Dev Suite agent for Expo projects. Prefer MDS MCP tools fir
 - Keep route files thin, env secrets server-only, and release work gated by Doctor checks.
 - Prefer official Expo/React Native guidance for framework mechanics; MDS adds project memory, checks, defaults, and workflows.
 - Do not skip unresolved `# TodoForContext(optional):` markers before implementation.
-- When MCP is unavailable, use CLI fallbacks such as `mds doctor`, `mds continue`, and `mds report`.
+- When a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, use commands such as `mds doctor`, `mds continue`, and `mds report`.

package/bundles/claude-code/commands/create-expo-super-stack.md

@@ -1,30 +1,31 @@
 # /create-expo-super-stack
 
-Create a new Expo app with the MDS Super Stack flow, using this knowledge package as the shared source of truth for agent-facing text and the published CLI as the execution source of truth.
+Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
 
 ## Arguments
 
 - `parentDir`: folder where the new app directory should be created.
 - `appName`: app folder name.
 
-## MCP-First Workflow
+## Required MDS MCP Tool Flow
 
 1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Invoke the MCP prompt `create_expo_super_stack` from a parent directory when you want guided intake.
-3. Keep the conversation one question per turn and summarize the captured choices before generation.
-4. Treat the MCP prompt as the intake surface and the CLI as the generator, so CLI changes are picked up automatically when the published command changes.
-5. After generation, move into the new app folder and invoke `continue_project` (or prompt `continue_mds_project`) for the first implementation session.
+2. Drive intake with `create_expo_super_stack_intake_step`.
+3. Ask exactly one question per turn.
+4. Always show the returned default and options.
+5. Never invent or silently accept defaults on the user's behalf.
+6. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
+7. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
+8. Then call `create_expo_super_stack_generate` with `confirmed: true`.
 
-## CLI / Manual Fallback
+## Failure Behavior
 
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI generation:
-   - `npx -y create-expo-super-stack <appName>`
-3. Then onboard/continue from inside the generated app using the current CLI behavior:
-   - `mds continue <new-app-path>`
+1. If the guided intake or generate tools are unavailable, stop.
+2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
+3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
+4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
 
 ## Verification And Output
 
 - Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
-- Output: generated app path, onboarding status, and immediate next command.
+- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.

package/bundles/claude-code/skills/create-expo-super-stack/SKILL.md

@@ -1,35 +1,36 @@
 ---
-description: Create a new Expo app with the MDS Super Stack flow, using this knowledge package as the shared source of truth for agent-facing text and the published CLI as the execution source of truth.
+description: Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
 disable-model-invocation: true
 ---
 
 # /create-expo-super-stack
 
-Create a new Expo app with the MDS Super Stack flow, using this knowledge package as the shared source of truth for agent-facing text and the published CLI as the execution source of truth.
+Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
 
 ## Arguments
 
 - `parentDir`: folder where the new app directory should be created.
 - `appName`: app folder name.
 
-## MCP-First Workflow
+## Required MDS MCP Tool Flow
 
 1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Invoke the MCP prompt `create_expo_super_stack` from a parent directory when you want guided intake.
-3. Keep the conversation one question per turn and summarize the captured choices before generation.
-4. Treat the MCP prompt as the intake surface and the CLI as the generator, so CLI changes are picked up automatically when the published command changes.
-5. After generation, move into the new app folder and invoke `continue_project` (or prompt `continue_mds_project`) for the first implementation session.
+2. Drive intake with `create_expo_super_stack_intake_step`.
+3. Ask exactly one question per turn.
+4. Always show the returned default and options.
+5. Never invent or silently accept defaults on the user's behalf.
+6. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
+7. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
+8. Then call `create_expo_super_stack_generate` with `confirmed: true`.
 
-## CLI / Manual Fallback
+## Failure Behavior
 
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI generation:
-   - `npx -y create-expo-super-stack <appName>`
-3. Then onboard/continue from inside the generated app using the current CLI behavior:
-   - `mds continue <new-app-path>`
+1. If the guided intake or generate tools are unavailable, stop.
+2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
+3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
+4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
 
 ## Verification And Output
 
 - Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
-- Output: generated app path, onboarding status, and immediate next command.
+- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.

package/bundles/codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mr-djs-dev-suite",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "description": "MDS Expo development workflows for review, onboarding, deployment readiness, and project continuation.",
   "author": {
     "name": "DJ Grimsley",
@@ -21,8 +21,8 @@
   "mcpServers": "./.mcp.json",
   "interface": {
     "displayName": "Mr. DJ's Dev Suite",
-    "shortDescription": "MCP-first Expo review, doctor, onboarding, and deploy workflows",
-    "longDescription": "Generate and use MDS skills plus command playbooks for Expo project review, onboarding, deployment prep, SEO fixes, and phase-based continuation with reliable MCP and CLI fallback paths.",
+    "shortDescription": "Expo review, doctor, onboarding, and deploy workflows powered by MDS MCP tools",
+    "longDescription": "Generate and use MDS skills plus command playbooks for Expo project review, onboarding, deployment prep, SEO fixes, and phase-based continuation, with callable MDS MCP tools for runtime behavior.",
     "developerName": "MDS",
     "category": "Coding",
     "capabilities": [

package/bundles/codex/.mcp.json

@@ -4,7 +4,7 @@
       "command": "npx",
       "args": [
         "-y",
-        "@mr.dj2u/mcp-server@0.1.4"
+        "@mr.dj2u/mcp-server@0.1.5"
       ]
     }
   }

package/bundles/codex/README.md

@@ -10,6 +10,7 @@ The Mr. DJ's Dev Suite Codex plugin bundle is generated from `packages/knowledge
 - Command prompt files: `commands/*.md`
 
 The source of truth for skills remains `packages/knowledge/src/content/skills`.
+Runtime behavior comes from callable MDS MCP tools exposed by `@mr.dj2u/mcp-server`.
 
 ## One-Command Install
 
@@ -30,9 +31,11 @@ mds agent install --client codex --scope user --dry-run
 
 After install, restart Codex so it picks up the local marketplace. Then type `@Mr. DJ's Dev Suite` in chat to get the install pop-up, hit Install, and use `@Mr. DJ's Dev Suite` in Codex Desktop or the Codex extension for VS Code.
 
+If Codex keeps using stale behavior after republish, refresh the local plugin cache, reinstall the MDS MCP server, then run `mds_runtime_versions` from the host surface to confirm which versions are active.
+
 ## MCP-Only Fallback
 
-Use this when you only want predictable MCP tools/prompts and not the plugin/skills bundle:
+Use this when you only want the callable MDS MCP tools/prompts and not the plugin/skills bundle:
 
 ```sh
 mds mcp install --client codex --scope project --target /path/to/your/expo-app

package/bundles/codex/commands/create-expo-super-stack.md

@@ -1,30 +1,31 @@
 # /create-expo-super-stack
 
-Create a new Expo app with the MDS Super Stack flow, using this knowledge package as the shared source of truth for agent-facing text and the published CLI as the execution source of truth.
+Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
 
 ## Arguments
 
 - `parentDir`: folder where the new app directory should be created.
 - `appName`: app folder name.
 
-## MCP-First Workflow
+## Required MDS MCP Tool Flow
 
 1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Invoke the MCP prompt `create_expo_super_stack` from a parent directory when you want guided intake.
-3. Keep the conversation one question per turn and summarize the captured choices before generation.
-4. Treat the MCP prompt as the intake surface and the CLI as the generator, so CLI changes are picked up automatically when the published command changes.
-5. After generation, move into the new app folder and invoke `continue_project` (or prompt `continue_mds_project`) for the first implementation session.
+2. Drive intake with `create_expo_super_stack_intake_step`.
+3. Ask exactly one question per turn.
+4. Always show the returned default and options.
+5. Never invent or silently accept defaults on the user's behalf.
+6. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
+7. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
+8. Then call `create_expo_super_stack_generate` with `confirmed: true`.
 
-## CLI / Manual Fallback
+## Failure Behavior
 
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI generation:
-   - `npx -y create-expo-super-stack <appName>`
-3. Then onboard/continue from inside the generated app using the current CLI behavior:
-   - `mds continue <new-app-path>`
+1. If the guided intake or generate tools are unavailable, stop.
+2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
+3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
+4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
 
 ## Verification And Output
 
 - Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
-- Output: generated app path, onboarding status, and immediate next command.
+- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.

package/bundles/codex/skills/workflow-continue-development/SKILL.md

@@ -5,10 +5,11 @@ description: "Use when the user asks Mr. DJ's Dev Suite to continue development,
 
 # Codex Workflow Routing
 
-- This is a Mr. DJ's Dev Suite plugin workflow. Prefer the bundled MCP tools before terminal fallbacks.
-- When an MCP tool named in this workflow is available, call that tool directly instead of running app-local npm scripts.
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
 - Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If the MCP server is unavailable, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
 
 # /continue-development
 

package/bundles/codex/skills/workflow-create-expo-super-stack/SKILL.md

@@ -5,38 +5,40 @@ description: "Use when the user asks Mr. DJ's Dev Suite to run the Create Expo S
 
 # Codex Workflow Routing
 
-- This is a Mr. DJ's Dev Suite plugin workflow. Prefer the bundled MCP tools before terminal fallbacks.
-- When an MCP tool named in this workflow is available, call that tool directly instead of running app-local npm scripts.
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
 - Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If the MCP server is unavailable, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
 
 # /create-expo-super-stack
 
-Create a new Expo app with the MDS Super Stack flow, using this knowledge package as the shared source of truth for agent-facing text and the published CLI as the execution source of truth.
+Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
 
 ## Arguments
 
 - `parentDir`: folder where the new app directory should be created.
 - `appName`: app folder name.
 
-## MCP-First Workflow
+## Required MDS MCP Tool Flow
 
 1. Confirm the `mr-djs-dev-suite` MCP server is available.
-2. Invoke the MCP prompt `create_expo_super_stack` from a parent directory when you want guided intake.
-3. Keep the conversation one question per turn and summarize the captured choices before generation.
-4. Treat the MCP prompt as the intake surface and the CLI as the generator, so CLI changes are picked up automatically when the published command changes.
-5. After generation, move into the new app folder and invoke `continue_project` (or prompt `continue_mds_project`) for the first implementation session.
+2. Drive intake with `create_expo_super_stack_intake_step`.
+3. Ask exactly one question per turn.
+4. Always show the returned default and options.
+5. Never invent or silently accept defaults on the user's behalf.
+6. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
+7. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
+8. Then call `create_expo_super_stack_generate` with `confirmed: true`.
 
-## CLI / Manual Fallback
+## Failure Behavior
 
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI generation:
-   - `npx -y create-expo-super-stack <appName>`
-3. Then onboard/continue from inside the generated app using the current CLI behavior:
-   - `mds continue <new-app-path>`
+1. If the guided intake or generate tools are unavailable, stop.
+2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
+3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
+4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
 
 ## Verification And Output
 
 - Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
-- Output: generated app path, onboarding status, and immediate next command.
+- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.

package/bundles/codex/skills/workflow-fix-seo/SKILL.md

@@ -5,10 +5,11 @@ description: "Use when the user asks Mr. DJ's Dev Suite to run the Fix Seo workf
 
 # Codex Workflow Routing
 
-- This is a Mr. DJ's Dev Suite plugin workflow. Prefer the bundled MCP tools before terminal fallbacks.
-- When an MCP tool named in this workflow is available, call that tool directly instead of running app-local npm scripts.
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
 - Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If the MCP server is unavailable, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
 
 # /fix-seo
 

package/bundles/codex/skills/workflow-prepare-deploy/SKILL.md

@@ -5,10 +5,11 @@ description: "Use when the user asks Mr. DJ's Dev Suite to run the Prepare Deplo
 
 # Codex Workflow Routing
 
-- This is a Mr. DJ's Dev Suite plugin workflow. Prefer the bundled MCP tools before terminal fallbacks.
-- When an MCP tool named in this workflow is available, call that tool directly instead of running app-local npm scripts.
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
 - Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If the MCP server is unavailable, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
 
 # /prepare-deploy
 

package/bundles/codex/skills/workflow-project-research-plan/SKILL.md

@@ -5,10 +5,11 @@ description: "Use when the user asks Mr. DJ's Dev Suite to run the Project Resea
 
 # Codex Workflow Routing
 
-- This is a Mr. DJ's Dev Suite plugin workflow. Prefer the bundled MCP tools before terminal fallbacks.
-- When an MCP tool named in this workflow is available, call that tool directly instead of running app-local npm scripts.
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
 - Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If the MCP server is unavailable, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
 
 # /project-research-plan
 

package/bundles/codex/skills/workflow-push-merge-loop/SKILL.md

@@ -5,10 +5,11 @@ description: "Use when the user asks Mr. DJ's Dev Suite to run the PR iteration
 
 # Codex Workflow Routing
 
-- This is a Mr. DJ's Dev Suite plugin workflow. Prefer the bundled MCP tools before terminal fallbacks.
-- When an MCP tool named in this workflow is available, call that tool directly instead of running app-local npm scripts.
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
 - Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If the MCP server is unavailable, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
 
 # /push-merge-loop
 

package/bundles/codex/skills/workflow-review-expo-project/SKILL.md

@@ -5,10 +5,11 @@ description: "Use when the user asks Mr. DJ's Dev Suite to run the Review Expo P
 
 # Codex Workflow Routing
 
-- This is a Mr. DJ's Dev Suite plugin workflow. Prefer the bundled MCP tools before terminal fallbacks.
-- When an MCP tool named in this workflow is available, call that tool directly instead of running app-local npm scripts.
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
 - Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If the MCP server is unavailable, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
 
 # /review-expo-project
 

package/bundles/codex/skills/workflow-run-doctor/SKILL.md

@@ -5,10 +5,11 @@ description: "Use when the user asks Mr. DJ's Dev Suite to run Doctor, run a hea
 
 # Codex Workflow Routing
 
-- This is a Mr. DJ's Dev Suite plugin workflow. Prefer the bundled MCP tools before terminal fallbacks.
-- When an MCP tool named in this workflow is available, call that tool directly instead of running app-local npm scripts.
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
 - Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If the MCP server is unavailable, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
 
 # /run-doctor
 

package/bundles/codex/skills/workflow-wrap-up/SKILL.md

@@ -5,10 +5,11 @@ description: "Use when the user has finished testing and wants Mr. DJ's Dev Suit
 
 # Codex Workflow Routing
 
-- This is a Mr. DJ's Dev Suite plugin workflow. Prefer the bundled MCP tools before terminal fallbacks.
-- When an MCP tool named in this workflow is available, call that tool directly instead of running app-local npm scripts.
+- This is a Mr. DJ's Dev Suite plugin workflow. Plugin skills and command markdown are guidance only.
+- Prefer callable MDS MCP tools exposed by `@mr.dj2u/mcp-server` when this workflow names them.
 - Do not use stale package names such as `@mrdj/cli`. The CLI package is `@mr.dj2u/cli`; the executable is `mds`.
-- If the MCP server is unavailable, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
+- If a workflow specifically requires guided MDS MCP tools and they are unavailable, stop and tell the user to refresh or reinstall the MDS plugin/MCP server instead of inventing defaults.
+- For ordinary CLI workflows that do allow fallback, prefer `mds <command>` from PATH, then `npx -y -p @mr.dj2u/cli@latest mds <command>`.
 
 # /wrap-up
 

package/bundles/vscode-copilot/.github/agents/mds.agent.md

@@ -5,7 +5,7 @@ description: "MDS Expo project intelligence agent for Doctor, onboarding, deploy
 
 # MDS Agent
 
-You are the Mr. DJ's Dev Suite agent for Expo projects. Prefer MDS MCP tools first, then CLI fallbacks.
+You are the Mr. DJ's Dev Suite agent for Expo projects. Treat callable MDS MCP tools as the runtime behavior surface and prompt markdown as guidance only.
 
 ## Tool Routing
 

package/bundles/vscode-copilot/.github/copilot-instructions.md

@@ -2,7 +2,7 @@
 # Mr. DJ's Dev Suite Copilot Instructions
 
 - Treat `project/` as the source of truth for product intent, roadmap, style, and technical rules.
-- Prefer MDS MCP tools before broad edits: `doctor_scan_project`, `doctor_scan_file`, `generate_refactor_plan`, and `generate_deploy_checklist`.
+- Prefer callable MDS MCP tools before broad edits: `doctor_scan_project`, `doctor_scan_file`, `generate_refactor_plan`, and `generate_deploy_checklist`.
 - Use `list_skills`, `get_skill`, and `get_guide` for MDS guidance, while delegating framework mechanics to official Expo/React Native guidance when available.
 - Keep route files thin, env secrets server-only, and release work gated by Doctor checks.
 <!-- END MDS COPILOT INSTRUCTIONS -->

package/bundles/vscode-copilot/.github/prompts/continue-development.prompt.md

@@ -1,6 +1,6 @@
 ---
 mode: "agent"
-description: "Run the MDS Continue Development workflow with MCP-first diagnostics and CLI fallback."
+description: "Run the MDS Continue Development workflow with callable MDS MCP diagnostics and explicit fallback rules."
 ---
 
 # /continue-development

package/bundles/vscode-copilot/.github/prompts/create-expo-super-stack.prompt.md

@@ -1,35 +1,36 @@
 ---
 mode: "agent"
-description: "Run the MDS Create Expo Super Stack workflow with MCP-first diagnostics and CLI fallback."
+description: "Run the MDS Create Expo Super Stack workflow with callable MDS MCP diagnostics and explicit fallback rules."
 ---
 
 # /create-expo-super-stack
 
-Create a new Expo app with the MDS Super Stack flow, using this knowledge package as the shared source of truth for agent-facing text and the published CLI as the execution source of truth.
+Create a new Expo app with the MDS Super Stack flow, using the published CESS CLI as the execution source of truth and callable MDS MCP tools as the guided intake surface.
 
 ## Arguments
 
 - `parentDir`: folder where the new app directory should be created.
 - `appName`: app folder name.
 
-## MCP-First Workflow
+## Required MDS MCP Tool Flow
 
 1. Confirm the `mds` MCP server is available.
-2. Invoke the MCP prompt `create_expo_super_stack` from a parent directory when you want guided intake.
-3. Keep the conversation one question per turn and summarize the captured choices before generation.
-4. Treat the MCP prompt as the intake surface and the CLI as the generator, so CLI changes are picked up automatically when the published command changes.
-5. After generation, move into the new app folder and invoke `continue_project` (or prompt `continue_mds_project`) for the first implementation session.
+2. Drive intake with `create_expo_super_stack_intake_step`.
+3. Ask exactly one question per turn.
+4. Always show the returned default and options.
+5. Never invent or silently accept defaults on the user's behalf.
+6. When the intake tool returns `confirm`, summarize the returned `summaryLines` and ask the user to confirm.
+7. After explicit confirmation, set `answers.confirmed=true`, call the intake tool again, and proceed only when it returns `ready`.
+8. Then call `create_expo_super_stack_generate` with `confirmed: true`.
 
-## CLI / Manual Fallback
+## Failure Behavior
 
-1. If MCP is not configured, install it manually:
-   - `mds mcp install --client <client> --scope project`
-2. Direct CLI generation:
-   - `npx -y create-expo-super-stack <appName>`
-3. Then onboard/continue from inside the generated app using the current CLI behavior:
-   - `mds continue <new-app-path>`
+1. If the guided intake or generate tools are unavailable, stop.
+2. Call `mds_runtime_versions` to diagnose stale plugin or MCP installs.
+3. Tell the user to refresh or reinstall the MDS plugin/MCP server.
+4. Do not fall back to `--mds-yes` or direct CLI shortcuts unless the user explicitly asked for a fast non-interactive run.
 
 ## Verification And Output
 
 - Confirm generated app has `project/info.md`, `project/todo.md`, `project/style.md`, and `project/guidelines.md`.
-- Output: generated app path, onboarding status, and immediate next command.
+- Output: generated app path, onboarding status, and the handoff to open a fresh agent session inside the new app folder and run `mds continue`.

package/bundles/vscode-copilot/.github/prompts/fix-seo.prompt.md

@@ -1,6 +1,6 @@
 ---
 mode: "agent"
-description: "Run the MDS Fix Seo workflow with MCP-first diagnostics and CLI fallback."
+description: "Run the MDS Fix Seo workflow with callable MDS MCP diagnostics and explicit fallback rules."
 ---
 
 # /fix-seo

package/bundles/vscode-copilot/.github/prompts/prepare-deploy.prompt.md

@@ -1,6 +1,6 @@
 ---
 mode: "agent"
-description: "Run the MDS Prepare Deploy workflow with MCP-first diagnostics and CLI fallback."
+description: "Run the MDS Prepare Deploy workflow with callable MDS MCP diagnostics and explicit fallback rules."
 ---
 
 # /prepare-deploy

package/bundles/vscode-copilot/.github/prompts/project-research-plan.prompt.md

@@ -1,6 +1,6 @@
 ---
 mode: "agent"
-description: "Run the MDS Project Research Plan workflow with MCP-first diagnostics and CLI fallback."
+description: "Run the MDS Project Research Plan workflow with callable MDS MCP diagnostics and explicit fallback rules."
 ---
 
 # /project-research-plan

package/bundles/vscode-copilot/.github/prompts/push-merge-loop.prompt.md

@@ -1,6 +1,6 @@
 ---
 mode: "agent"
-description: "Run the MDS Push Merge Loop workflow with MCP-first diagnostics and CLI fallback."
+description: "Run the MDS Push Merge Loop workflow with callable MDS MCP diagnostics and explicit fallback rules."
 ---
 
 # /push-merge-loop

package/bundles/vscode-copilot/.github/prompts/review-expo-project.prompt.md

@@ -1,6 +1,6 @@
 ---
 mode: "agent"
-description: "Run the MDS Review Expo Project workflow with MCP-first diagnostics and CLI fallback."
+description: "Run the MDS Review Expo Project workflow with callable MDS MCP diagnostics and explicit fallback rules."
 ---
 
 # /review-expo-project

package/bundles/vscode-copilot/.github/prompts/run-doctor.prompt.md

@@ -1,6 +1,6 @@
 ---
 mode: "agent"
-description: "Run the MDS Run Doctor workflow with MCP-first diagnostics and CLI fallback."
+description: "Run the MDS Run Doctor workflow with callable MDS MCP diagnostics and explicit fallback rules."
 ---
 
 # /run-doctor

package/bundles/vscode-copilot/.github/prompts/wrap-up.prompt.md

@@ -1,6 +1,6 @@
 ---
 mode: "agent"
-description: "Run the MDS Wrap Up workflow with MCP-first diagnostics and CLI fallback."
+description: "Run the MDS Wrap Up workflow with callable MDS MCP diagnostics and explicit fallback rules."
 ---
 
 # /wrap-up

package/bundles/vscode-copilot/.vscode/mcp.json

@@ -4,7 +4,7 @@
       "command": "npx",
       "args": [
         "-y",
-        "@mr.dj2u/mcp-server@0.1.4"
+        "@mr.dj2u/mcp-server@0.1.5"
       ]
     }
   }