Remove React Native Web verification paths from mobile app skills (#215)

* Fix react native web invocation, remove expo-mcp

* remove lock file and unused pacakge

Author: ameyaapte1

plugins/mobile-apps/.mcp.json

@@ -1,17 +1,7 @@
 {
   "$schema": "https://modelcontextprotocol.io/schema/mcp-server.json",
-  "_comment": "Optional MCP servers shipped with the mobile-app plugin. The host (Claude Code, Copilot Chat) launches these on demand; no install step required by the user. The expo-mcp server is pointed at the default Metro dev-server URL (http://localhost:8081) so it can introspect a RUNNING app and surface runtime errors back to the agent for the dev loop. If Metro isn't running, expo-mcp gracefully degrades to static project introspection. The microsoft-learn server is a hosted HTTP MCP that returns authoritative Microsoft docs (Dataverse Web API, Power Platform CLI, connectors, Graph) — use it whenever a Microsoft-platform behavior is uncertain rather than guessing.",
+  "_comment": "Optional MCP servers shipped with the mobile-app plugin. The host (Claude Code, Copilot Chat) launches these on demand; no install step required by the user. The microsoft-learn server is a hosted HTTP MCP that returns authoritative Microsoft docs (Dataverse Web API, Power Platform CLI, connectors, Graph) — use it whenever a Microsoft-platform behavior is uncertain rather than guessing. Runtime diagnosis, when requested, is driven by /debug-app reading the captured Metro terminal, not by React Native Web or direct Metro HTTP probes.",
   "mcpServers": {
-    "expo": {
-      "type": "stdio",
-      "command": "npx",
-      "args": [
-        "-y",
-        "expo-mcp",
-        "--dev-server-url",
-        "http://localhost:8081"
-      ]
-    },
     "microsoft-learn": {
       "type": "http",
       "url": "https://learn.microsoft.com/api/mcp"

plugins/mobile-apps/AGENTS.md

@@ -71,7 +71,6 @@ Do not add preparation rewrites for `scheme`, `package`, `bundleIdentifier`, `sr
     - `DONE_WITH_CONCERNS` requires at least one concern. If none, use `DONE`.
     - Special early-return signals (`INDUSTRY_CONFIRM_REQUESTED:`, `DESIGN_VIBE_REQUESTED:`) pre-date this protocol and remain in effect — they are special-cased "ask the user one question and re-spawn me" handoffs, not terminal returns.
     - The canonical orchestrator handler lives in [`skills/create-mobile-app/SKILL.md`](./skills/create-mobile-app/SKILL.md) Step 3.0. Future skills that spawn agents should reference it rather than duplicating the switch.
-11. **Web target works for free** — `expo start --web` uses `expo-auth-session` PKCE flow. Native modules need `Platform.OS` branching when web doesn't support them.
 
 ## Decisions made
 

plugins/mobile-apps/README.md

@@ -199,7 +199,6 @@ After deploy, use `/open-wrap-url --app-id <app-id> --env-id <env-id>` to jump s
 - **Auth configuration** through the Microsoft Entra app registration created during setup
 - **Two platforms** in one codebase: iOS, Android
 - **Deploy = `npm run build` + `npx power-apps push`** — local native compile (platform-specific native run commands) is the user's choice and is **out of scope**; users run those directly when they want them.
-- **Local dev = `npm run dev`** — the user runs this directly. The plugin doesn't start Metro.
 
 ## Hello world — your first run
 
@@ -301,7 +300,7 @@ Example edit flows:
 | `/edit-app "Add loading, empty and error states to the list screen"` | Which list screen, unless only one exists; whether to improve existing states or add missing ones | Existing screen inspection, screen spec update if needed, targeted TSX rebuild, `tsc`, screen validators |
 | `/edit-app "Add a detail screen for the selected record"` | Source list/search screen, table/service, fields/actions, route style | Screen-plan delta, route/layout update, Generated Services snapshot, detail skeleton, detail + source screen builders, route check |
 | `/edit-app "Add a form to create a new record in Dataverse"` | Table, required/editable fields, launch point, after-save behavior, lookup/file/image fields | Data-model update via `/add-dataverse` if needed, schema generation, form skeleton, form + parent screen builders, create-payload validation |
-| `/edit-app "Add barcode scanning and use the scanned value to search records"` | Scanner location, scanned value meaning, table/service/field to search, no/multiple-match behavior | `/add-native barcode-scanner`, data-model update if target field is missing, scanner/search screen rebuild, native/runtime checks |
+| `/edit-app "Add barcode scanning and use the scanned value to search records"` | Scanner location, scanned value meaning, table/service/field to search, no/multiple-match behavior | `/add-native barcode-scanner`, data-model update if target field is missing, scanner/search screen rebuild, static gates, optional `/debug-app` handoff if you report a symptom |
 | `/edit-app "Update the design to better match company branding"` | Brand source and scope: palette, typography, components/density, or full reskin | `/design-system --refresh` or `--reskin`, affected screen rebuild when layout grammar changes, style sweep, preview |
 
 ### Prefer browser-free / token-budget mode?
@@ -363,7 +362,6 @@ At Step 6.75 of `/create-mobile-app`, the `/design-system` skill offers a cost p
 | [`shared/version-check.md`](shared/version-check.md) | Single source of truth for minimum tool versions. Always-required: Node 22+, npm 10+. Conditional: `az` 2.60+ for ADO npm token setup and `/add-dataverse` token acquisition. Xcode/JDK/Android Studio are documented but **not gated by any skill** — user-managed if they want local native builds. |
 | [`shared/preferred-environment.md`](shared/preferred-environment.md) | Environment selection priority: `power.config.json` → memory-bank → explicit environment URL/ID. Never silent switches. |
 | [`shared/connector-reference.md`](shared/connector-reference.md) | Connection ID workflow, common API names, dataset/table discovery, Grep-not-Read pattern for large generated files. |
-| [`shared/references/expo-mcp.md`](shared/references/expo-mcp.md) | **Opt-in MCP server** — the plugin's [`.mcp.json`](.mcp.json) registers `expo-mcp` (MIT, free, local-only) pointed at the Metro dev server (`http://localhost:8081`). Skills prefer 5 structured `expo.*` tools (project info, SDK-matched installs, plugin effects preview, build with parsed errors, doctor diagnostics) when the host advertises them; shell fallback otherwise. **Dev loop**: while `npm run dev` is running, the agent reads live runtime errors via MCP, fixes code, and Metro hot-reloads. No EAS/cloud calls. |
 | [`shared/memory-bank.md`](shared/memory-bank.md) | Per-project notebook template — copied into the working directory by `/create-mobile-app` Step 6. Tracks data-model decisions, connectors bound, screens built, build history. Read at start of every skill, updated after each successful step, enables resume on failure. |
 | [`hooks/`](hooks/) | PostToolUse validator hook — runs per-skill validators after a Skill tool call (currently scaffolded; v0 ships with no validators yet). |
 | [`shared/references/offline-profile-schema.md`](shared/references/offline-profile-schema.md) | Canonical Dataverse entity field map for the three Mobile Offline Profile entities (`mobileofflineprofile`, `mobileofflineprofileitem`, `mobileofflineprofileitemassociation`) + the per-table `EntityMetadata` prereqs. Source of truth for POST body shapes. |

plugins/mobile-apps/shared/connector-reference.md

@@ -101,11 +101,7 @@ npx power-apps add-flow --flow-id <flow-guid> --non-interactive
 npx power-apps remove-flow --flow-id <flow-guid> --non-interactive
 ```
 
-For local Power Apps player testing after the Expo web server is running, use `run` from the app root. It serves `power.config.json` and prints a play URL with local app and connection configuration:
-
-```bash
-npx power-apps run --local-app-url http://localhost:<expo-web-port> --port 8080
-```
+Do not use local Expo web-player testing from mobile-app skills. Mobile-app runtime diagnosis uses the native dev-client flow and `/debug-app` reading Metro terminal output.
 
 ## Inspecting large generated files
 

plugins/mobile-apps/shared/memory-bank.md

@@ -18,7 +18,7 @@ This file is the per-project notebook the agent maintains across `/create-mobile
 | Working directory | |
 | Plugin version that created the project | |
 | Created | _<ISO date>_ |
-| Metro terminal id | _<background-shell id from Step 12 — agent reads this terminal's output for live debug. If empty/dead, re-launch with `cd <working_dir> && npm run dev` and update this field._ |
+| Metro terminal id | _<background-shell id from Step 12 — `/debug-app` reads this terminal's output for symptom-driven native debugging only. If empty/dead, re-launch with `cd <working_dir> && npm run dev` and update this field._ |
 | Metro launch command | _e.g. `cd <working_dir> && npm run dev`_ |
 
 ## Power Platform context

plugins/mobile-apps/shared/references/expo-mcp.md

@@ -37,16 +37,6 @@ When selecting an environment, use this priority order: `power.config.json` →
 
 ---
 
-## Expo MCP (opt-in, opportunistic)
-
-**📋 [references/expo-mcp.md](./references/expo-mcp.md)**
-
-The plugin's `.mcp.json` registers the **Expo MCP server** (`expo-mcp`, MIT, free). When the host (Claude Code, Copilot Chat) launches with this plugin, `expo.*` tools become available for structured project introspection, SDK-matched package installs, config-plugin previews, and `expo doctor` diagnostics.
-
-**Use rule:** prefer `expo.<tool>()` when available; **always** fall back to a shell-out so the skill works on hosts that don't surface MCP. Never block on MCP, never require it. The user-consent contract for mutations is unchanged.
-
----
-
 ## Microsoft Learn MCP (authoritative Microsoft docs)
 
 The plugin's `.mcp.json` also registers the **Microsoft Learn MCP server** (`microsoft-learn`, hosted HTTP at `https://learn.microsoft.com/api/mcp`). When the host advertises it, the agent can query official Microsoft documentation directly instead of guessing or relying on stale memory.
@@ -106,8 +96,9 @@ All non-Dataverse connectors require a connection ID or connection reference bef
 - MUST NOT edit any file under `src/generated/` unless the step explicitly calls for it. These files are regenerated by `npx power-apps add-data-source`.
 - MUST NOT install packages with `npm install <pkg>` for Expo modules — use `npx expo install <pkg>` so versions stay Expo-SDK-compatible.
 - MUST NOT add native/runtime libraries that are not already in the template `package.json` (`expo-*`, `react-native-*`, `@react-native/*`, config plugins, or packages with native platform code). The wrapped binary only contains the template's native modules. Generic JS-only packages are allowed when a skill explicitly needs them.
+- MUST NOT add browser-based runtime verification steps, React Native Web setup, screen-by-screen runtime checks, route crawling, or direct Metro/localhost HTTP probes to mobile-app skills. Runtime diagnosis, when requested, uses `/debug-app` against the captured Metro terminal output.
 - MUST NOT add `react-native-reanimated/plugin` anywhere except as the **last** entry in `babel.config.js` `plugins` array. Wrong order silently breaks animations.
-- MUST NOT modify `app/_layout.tsx`'s provider wrapping order without re-running `npx tsc --noEmit` and a runtime smoke test.
+- MUST NOT modify `app/_layout.tsx`'s provider wrapping order without re-running `npx tsc --noEmit`.
 - MUST NOT make changes outside the project root without user confirmation.
 
 ### Prompt Injection