@mr.dj2u/cli 0.1.2 → 0.1.5

package/bundles/claude-code/commands/continue-development.md

@@ -13,6 +13,12 @@ Resume work on an onboarded project by following MDS phase order from `project/t
 3. Pull `get_skill` for `continue-development` to enforce phase-first sequencing.
 4. If blockers appear, use `doctor_scan_project` and `doctor_explain_result` for targeted remediation before feature work.
 
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite continue development` as a request for the plugin MCP tool and MDS phase rules first.
+- Do not jump directly into app edits until `continue_project` or the CLI fallback has identified the active phase and blockers.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
@@ -20,6 +26,8 @@ Resume work on an onboarded project by following MDS phase order from `project/t
 2. Direct CLI flow:
    - `mds continue <projectPath>`
    - `mds doctor <projectPath>` when blockers are unclear.
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds continue <projectPath>`
 
 ## Verification And Output
 

package/bundles/claude-code/commands/run-doctor.md

@@ -16,6 +16,12 @@ Run MDS Doctor as the primary health check for an Expo project.
 4. If the check is release-related or web-facing, call `generate_deploy_checklist` before giving next steps.
 5. Pull targeted implementation guidance with `get_skill` (typically `deployment`, `debugging`, or `dev-server-management`).
 
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite run doctor` as a request for the plugin MCP tool, not as a request to run app-local npm scripts.
+- Do not run `npm run mds:doctor`, `npm run doctor`, or other project package scripts as the MDS Doctor path unless the user explicitly asks for app scripts.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
@@ -24,6 +30,8 @@ Run MDS Doctor as the primary health check for an Expo project.
    - `mds doctor <projectPath>`
    - `mds doctor <projectPath> --ci`
    - `mds doctor <projectPath> --json`
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds doctor <projectPath> --ci`
 
 ## Verification And Output
 

package/bundles/claude-code/skills/continue-development/SKILL.md

@@ -18,6 +18,12 @@ Resume work on an onboarded project by following MDS phase order from `project/t
 3. Pull `get_skill` for `continue-development` to enforce phase-first sequencing.
 4. If blockers appear, use `doctor_scan_project` and `doctor_explain_result` for targeted remediation before feature work.
 
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite continue development` as a request for the plugin MCP tool and MDS phase rules first.
+- Do not jump directly into app edits until `continue_project` or the CLI fallback has identified the active phase and blockers.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
@@ -25,6 +31,8 @@ Resume work on an onboarded project by following MDS phase order from `project/t
 2. Direct CLI flow:
    - `mds continue <projectPath>`
    - `mds doctor <projectPath>` when blockers are unclear.
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds continue <projectPath>`
 
 ## Verification And Output
 

package/bundles/claude-code/skills/run-doctor/SKILL.md

@@ -21,6 +21,12 @@ Run MDS Doctor as the primary health check for an Expo project.
 4. If the check is release-related or web-facing, call `generate_deploy_checklist` before giving next steps.
 5. Pull targeted implementation guidance with `get_skill` (typically `deployment`, `debugging`, or `dev-server-management`).
 
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite run doctor` as a request for the plugin MCP tool, not as a request to run app-local npm scripts.
+- Do not run `npm run mds:doctor`, `npm run doctor`, or other project package scripts as the MDS Doctor path unless the user explicitly asks for app scripts.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
@@ -29,6 +35,8 @@ Run MDS Doctor as the primary health check for an Expo project.
    - `mds doctor <projectPath>`
    - `mds doctor <projectPath> --ci`
    - `mds doctor <projectPath> --json`
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds doctor <projectPath> --ci`
 
 ## Verification And Output
 

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

@@ -1,6 +1,6 @@
 {
   "name": "mr-djs-dev-suite",
-  "version": "0.1.0",
+  "version": "0.1.5",
   "description": "MDS Expo development workflows for review, onboarding, deployment readiness, and project continuation.",
   "author": {
     "name": "DJ Grimsley",

package/bundles/codex/.mcp.json

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

package/bundles/codex/README.md

@@ -13,21 +13,22 @@ The source of truth for skills remains `packages/knowledge/src/content/skills`.
 
 ## One-Command Install
 
-Project scope installs MCP into `.codex/config.toml`, copies this plugin into `plugins/mr-djs-dev-suite`, and registers it in `.agents/plugins/marketplace.json`:
+Project scope installs MCP plus the local marketplace/plugin enable blocks into `.codex/config.toml`, copies this plugin into `plugins/mr-djs-dev-suite`, and registers it in `.agents/plugins/marketplace.json`:
 
 ```sh
 mds agent install --client codex --scope project --target /path/to/your/expo-app
-mds agent verify --client codex --target /path/to/your/expo-app
+mds agent verify --client codex --scope project --target /path/to/your/expo-app
 ```
 
-User scope installs MCP into `~/.codex/config.toml`, copies the plugin into `~/plugins/mr-djs-dev-suite`, and registers it in `~/.agents/plugins/marketplace.json`:
+User scope installs MCP plus the local marketplace/plugin enable blocks into `~/.codex/config.toml`, copies the plugin into `~/plugins/mr-djs-dev-suite`, and registers it in `~/.agents/plugins/marketplace.json`:
 
 ```sh
 mds agent install --client codex --scope user
+mds agent verify --client codex --scope user
 mds agent install --client codex --scope user --dry-run
 ```
 
-After install, restart Codex if needed and enable/install `mr-djs-dev-suite` from the local marketplace.
+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.
 
 ## MCP-Only Fallback
 

package/bundles/codex/commands/continue-development.md

@@ -13,6 +13,12 @@ Resume work on an onboarded project by following MDS phase order from `project/t
 3. Pull `get_skill` for `continue-development` to enforce phase-first sequencing.
 4. If blockers appear, use `doctor_scan_project` and `doctor_explain_result` for targeted remediation before feature work.
 
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite continue development` as a request for the plugin MCP tool and MDS phase rules first.
+- Do not jump directly into app edits until `continue_project` or the CLI fallback has identified the active phase and blockers.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
@@ -20,6 +26,8 @@ Resume work on an onboarded project by following MDS phase order from `project/t
 2. Direct CLI flow:
    - `mds continue <projectPath>`
    - `mds doctor <projectPath>` when blockers are unclear.
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds continue <projectPath>`
 
 ## Verification And Output
 

package/bundles/codex/commands/run-doctor.md

@@ -16,6 +16,12 @@ Run MDS Doctor as the primary health check for an Expo project.
 4. If the check is release-related or web-facing, call `generate_deploy_checklist` before giving next steps.
 5. Pull targeted implementation guidance with `get_skill` (typically `deployment`, `debugging`, or `dev-server-management`).
 
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite run doctor` as a request for the plugin MCP tool, not as a request to run app-local npm scripts.
+- Do not run `npm run mds:doctor`, `npm run doctor`, or other project package scripts as the MDS Doctor path unless the user explicitly asks for app scripts.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
@@ -24,6 +30,8 @@ Run MDS Doctor as the primary health check for an Expo project.
    - `mds doctor <projectPath>`
    - `mds doctor <projectPath> --ci`
    - `mds doctor <projectPath> --json`
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds doctor <projectPath> --ci`
 
 ## Verification And Output
 

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

@@ -0,0 +1,47 @@
+---
+name: "MDS Continue Development"
+description: "Use when the user asks Mr. DJ's Dev Suite to continue development, pick the next phase task, resume work, or inspect project/todo.md."
+---
+
+# 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.
+- 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>`.
+
+# /continue-development
+
+Resume work on an onboarded project by following MDS phase order from `project/todo.md`.
+
+## Arguments
+
+- `projectPath`: onboarded app path (default: current directory).
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Call `continue_project` first to get the active-phase brief.
+3. Pull `get_skill` for `continue-development` to enforce phase-first sequencing.
+4. If blockers appear, use `doctor_scan_project` and `doctor_explain_result` for targeted remediation before feature work.
+
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite continue development` as a request for the plugin MCP tool and MDS phase rules first.
+- Do not jump directly into app edits until `continue_project` or the CLI fallback has identified the active phase and blockers.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client codex --scope project`
+2. Direct CLI flow:
+   - `mds continue <projectPath>`
+   - `mds doctor <projectPath>` when blockers are unclear.
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds continue <projectPath>`
+
+## Verification And Output
+
+- Confirm the chosen task belongs to the active phase or has an explicit deferral note.
+- Output: selected next task, blockers, and validation commands to run after implementation.

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

@@ -0,0 +1,42 @@
+---
+name: "MDS Create Expo Super Stack"
+description: "Use when the user asks Mr. DJ's Dev Suite to run the Create Expo Super Stack workflow."
+---
+
+# 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.
+- 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>`.
+
+# /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.
+
+## Arguments
+
+- `parentDir`: folder where the new app directory should be created.
+- `appName`: app folder name.
+
+## MCP-First Workflow
+
+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.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client codex --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>`
+
+## 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.

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

@@ -0,0 +1,41 @@
+---
+name: "MDS Fix Seo"
+description: "Use when the user asks Mr. DJ's Dev Suite to run the Fix Seo workflow."
+---
+
+# 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.
+- 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>`.
+
+# /fix-seo
+
+Apply SEO metadata fixes for Expo web routes with MCP guidance and post-fix verification.
+
+## Arguments
+
+- `projectPath`: Expo project path (default: current directory).
+- `routeOrFile`: optional route/file focus for targeted checks.
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Pull `get_skill` for `seo-metadata`.
+3. Optionally run `doctor_scan_file` for focused route files, then `doctor_scan_project` for full checks.
+4. Use `knowledge_list_resources` (`kind: "rule"`) to ensure canonical/indexing strategy is complete.
+5. Implement metadata, canonical, robots, and sitemap corrections in route ownership boundaries.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client codex --scope project`
+2. Direct CLI checks:
+   - `mds doctor <projectPath> --ci`
+   - Run project-specific web build/preview commands to verify metadata output.
+
+## Verification And Output
+
+- Confirm canonical tags, social metadata, and sitemap/robots behavior on affected routes.
+- Output: changed files, resolved SEO gaps, and any remaining manual verification steps.

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

@@ -0,0 +1,43 @@
+---
+name: "MDS Prepare Deploy"
+description: "Use when the user asks Mr. DJ's Dev Suite to run the Prepare Deploy workflow."
+---
+
+# 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.
+- 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>`.
+
+# /prepare-deploy
+
+Prepare an Expo project for release using deployment-focused skills plus Doctor parity checks.
+
+## Arguments
+
+- `projectPath`: release candidate project path (default: current directory).
+- `includeSeo`: whether to include web metadata/indexing checks (default: `true` when web is targeted).
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Run `doctor_scan_project` in `ci` mode for release parity.
+3. Pull `get_skill` for `deployment`; if web is involved also pull `seo-metadata`.
+4. Use `knowledge_list_resources` (`kind: "rule"`) to confirm env hygiene, SSR safety, and metadata requirements.
+5. Call `generate_deploy_checklist` so SEO, scripts, and release-readiness gaps are reflected in the next steps.
+6. Produce a release checklist mapped to current failing checks.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client codex --scope project`
+2. Direct CLI path:
+   - `mds doctor <projectPath> --ci`
+   - Run project scripts: `lint`, `type-check`, `test`, and production build/profile scripts.
+
+## Verification And Output
+
+- Re-run `doctor_scan_project` (or CLI equivalent) until blockers are cleared.
+- Keep the response user-facing and checklist-driven; avoid internal tool chatter and avoid asking for a PR unless the user requested GitHub workflow.
+- Output: release readiness status, unresolved blockers, and rollback/readiness notes.

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

@@ -0,0 +1,41 @@
+---
+name: "MDS Project Research Plan"
+description: "Use when the user asks Mr. DJ's Dev Suite to run the Project Research Plan workflow."
+---
+
+# 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.
+- 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>`.
+
+# /project-research-plan
+
+Turn rough product notes/research into actionable MDS project memory and next-phase plan.
+
+## Arguments
+
+- `projectPath`: target project path (default: current directory).
+- `inputs`: attached notes/docs to normalize into canonical memory files.
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Pull `get_skill` for `research-plan-intake` (and `project-onboarding` when onboarding context is mixed in).
+3. Call `knowledge_list_resources` for `guide` and `reference` resources as needed for structure and validation.
+4. Normalize clear context directly; ask focused follow-up only where ambiguity changes implementation direction.
+5. Update project memory files and produce an implementation-ready next-phase plan.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client codex --scope project`
+2. Direct CLI fallback:
+   - Use `mds onboard <projectPath>` for structured intake when memory files are missing.
+   - Use `mds continue <projectPath>` after memory normalization to select the next task.
+
+## Verification And Output
+
+- Confirm `project/info.md`, `project/style.md`, and `project/todo.md` align with extracted research context.
+- Output: resolved unknowns, outstanding questions, and the recommended next implementation slice.

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

@@ -0,0 +1,44 @@
+---
+name: "MDS Review Expo Project"
+description: "Use when the user asks Mr. DJ's Dev Suite to run the Review Expo Project workflow."
+---
+
+# 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.
+- 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>`.
+
+# /review-expo-project
+
+Review an Expo project with MCP-first diagnostics and skill-guided remediation.
+
+## Arguments
+
+- `projectPath`: absolute or relative project path (default: current directory).
+- `mode`: Doctor mode (`fast`, `ci`, or `full`; default: `ci`).
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Call `continue_project` to summarize current project state and blockers.
+3. Call `doctor_scan_project` with `projectPath` and `mode`.
+4. For each warning/error, call `doctor_explain_result`, then pull targeted guidance with `get_skill` (for example: `project-onboarding`, `debugging`, `deployment`).
+5. If the findings affect release readiness, call `generate_deploy_checklist` so the next steps stay checklist-driven instead of PR-driven.
+6. Call `knowledge_list_resources` with `kind: "guide"` if extra reference context is needed.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client codex --scope project`
+2. If MCP still cannot run, use direct CLI flows:
+   - `mds continue <projectPath>`
+   - `mds doctor <projectPath> --ci`
+
+## Verification And Output
+
+- Keep the response user-facing: summarize findings and next steps without echoing internal tool chatter or file-read noise.
+- Re-run `doctor_scan_project` (or `mds doctor --ci`) after fixes.
+- If the user is validating an installed agent bundle, include `mds agent verify --client <client> --target <path>` in the follow-up commands.
+- Output: blocker summary, failing checks, recommended next task, and concrete follow-up commands. Avoid proposing a PR unless the user explicitly asks for a GitHub workflow.

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

@@ -0,0 +1,52 @@
+---
+name: "MDS Run Doctor"
+description: "Use when the user asks Mr. DJ's Dev Suite to run Doctor, run a health check, run CI checks, diagnose project status, or explain MDS Doctor findings."
+---
+
+# 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.
+- 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>`.
+
+# /run-doctor
+
+Run MDS Doctor as the primary health check for an Expo project.
+
+## Arguments
+
+- `projectPath`: project root path (default: current directory).
+- `mode`: `fast`, `ci`, or `full` (default: `ci`).
+- `runScripts`: whether Doctor should execute project scripts (default: `true` for `ci` mode).
+
+## MCP-First Workflow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+2. Call `doctor_scan_project` with selected arguments.
+3. For each non-pass result, call `doctor_explain_result`.
+4. If the check is release-related or web-facing, call `generate_deploy_checklist` before giving next steps.
+5. Pull targeted implementation guidance with `get_skill` (typically `deployment`, `debugging`, or `dev-server-management`).
+
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite run doctor` as a request for the plugin MCP tool, not as a request to run app-local npm scripts.
+- Do not run `npm run mds:doctor`, `npm run doctor`, or other project package scripts as the MDS Doctor path unless the user explicitly asks for app scripts.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
+## CLI / Manual Fallback
+
+1. If MCP is not configured, install it manually:
+   - `mds mcp install --client codex --scope project`
+2. Direct CLI alternatives:
+   - `mds doctor <projectPath>`
+   - `mds doctor <projectPath> --ci`
+   - `mds doctor <projectPath> --json`
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds doctor <projectPath> --ci`
+
+## Verification And Output
+
+- Re-run Doctor after each fix batch.
+- Keep the response concise and user-facing; do not surface internal tool chatter or intermediate file reads.
+- Output: check summary, blocking errors first, and the exact command used for re-check.

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

@@ -18,6 +18,12 @@ Resume work on an onboarded project by following MDS phase order from `project/t
 3. Pull `get_skill` for `continue-development` to enforce phase-first sequencing.
 4. If blockers appear, use `doctor_scan_project` and `doctor_explain_result` for targeted remediation before feature work.
 
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite continue development` as a request for the plugin MCP tool and MDS phase rules first.
+- Do not jump directly into app edits until `continue_project` or the CLI fallback has identified the active phase and blockers.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
@@ -25,6 +31,8 @@ Resume work on an onboarded project by following MDS phase order from `project/t
 2. Direct CLI flow:
    - `mds continue <projectPath>`
    - `mds doctor <projectPath>` when blockers are unclear.
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds continue <projectPath>`
 
 ## Verification And Output
 

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

@@ -21,6 +21,12 @@ Run MDS Doctor as the primary health check for an Expo project.
 4. If the check is release-related or web-facing, call `generate_deploy_checklist` before giving next steps.
 5. Pull targeted implementation guidance with `get_skill` (typically `deployment`, `debugging`, or `dev-server-management`).
 
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite run doctor` as a request for the plugin MCP tool, not as a request to run app-local npm scripts.
+- Do not run `npm run mds:doctor`, `npm run doctor`, or other project package scripts as the MDS Doctor path unless the user explicitly asks for app scripts.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
@@ -29,6 +35,8 @@ Run MDS Doctor as the primary health check for an Expo project.
    - `mds doctor <projectPath>`
    - `mds doctor <projectPath> --ci`
    - `mds doctor <projectPath> --json`
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds doctor <projectPath> --ci`
 
 ## Verification And Output
 

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

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

package/bundles/vscode-copilot/user/.copilot/skills/workflow-continue-development/SKILL.md

@@ -18,6 +18,12 @@ Resume work on an onboarded project by following MDS phase order from `project/t
 3. Pull `get_skill` for `continue-development` to enforce phase-first sequencing.
 4. If blockers appear, use `doctor_scan_project` and `doctor_explain_result` for targeted remediation before feature work.
 
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite continue development` as a request for the plugin MCP tool and MDS phase rules first.
+- Do not jump directly into app edits until `continue_project` or the CLI fallback has identified the active phase and blockers.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
@@ -25,6 +31,8 @@ Resume work on an onboarded project by following MDS phase order from `project/t
 2. Direct CLI flow:
    - `mds continue <projectPath>`
    - `mds doctor <projectPath>` when blockers are unclear.
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds continue <projectPath>`
 
 ## Verification And Output
 

package/bundles/vscode-copilot/user/.copilot/skills/workflow-run-doctor/SKILL.md

@@ -21,6 +21,12 @@ Run MDS Doctor as the primary health check for an Expo project.
 4. If the check is release-related or web-facing, call `generate_deploy_checklist` before giving next steps.
 5. Pull targeted implementation guidance with `get_skill` (typically `deployment`, `debugging`, or `dev-server-management`).
 
+## Codex Routing Guardrails
+
+- Treat `@Mr. DJ's Dev Suite run doctor` as a request for the plugin MCP tool, not as a request to run app-local npm scripts.
+- Do not run `npm run mds:doctor`, `npm run doctor`, or other project package scripts as the MDS Doctor path unless the user explicitly asks for app scripts.
+- Never invoke `@mrdj/cli`; that package name is wrong. The published CLI package is `@mr.dj2u/cli` and its executable is `mds`.
+
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
@@ -29,6 +35,8 @@ Run MDS Doctor as the primary health check for an Expo project.
    - `mds doctor <projectPath>`
    - `mds doctor <projectPath> --ci`
    - `mds doctor <projectPath> --json`
+3. If `mds` is not on PATH, invoke the published CLI by binary name:
+   - `npx -y -p @mr.dj2u/cli@latest mds doctor <projectPath> --ci`
 
 ## Verification And Output
 

package/dist/cli.js

@@ -277,7 +277,6 @@ async function main() {
         .option('scope', {
         describe: 'Install for the current user or just the target project',
         choices: ['user', 'project'],
-        default: 'project',
     })
         .option('target', {
         describe: 'Project directory for project-scope install or verify',