refactor(mobile-app): move Metro logging into .powernative

Replace the process-owning Metro wrapper design with template-owned
logging. The template metro.config.js now writes sanitized Metro output
to .powernative/metro-logs during normal npm run dev, so manual starts
and agent starts use the same log source and there is no second-Metro-on-
8082 failure mode.

The logger captures both stdout/stderr and HTTP bundle failures. A probe
against a generated app confirmed the important distinction: stdout tee
alone captures startup logs, but bundle failures are returned as HTTP
responses and do not hit stdout. The middleware wrapper logs non-2xx
responses so /debug-app can see UnableToResolveError and similar bundle
failures.

metro-session.js is reduced from a process manager to a small status/tail
helper. It no longer starts, stops, detaches, or owns Metro; it only
locates the latest .powernative log, verifies the logged PID still owns
the logged port, and tails by byte cursor for /debug-app.

Docs and skills now describe npm run dev as the normal path, .powernative
as the authoritative debug source, and terminal IDs as optional-only UI
context. The old wrapper-owned .expo/metro-session state/log story is
removed.

Validation: node --check for the helper and template Metro config, 29
mobile script tests pass, and all repository validators pass.

Author: Shubham Agarwal

plugins/mobile-apps/AGENTS.md

@@ -26,7 +26,7 @@ README.md                      ← Plugin overview
 agents/                        ← native-app-planner, data-model-architect, screen-planner, screen-builder
 shared/                        ← shared-instructions, references, samples, memory-bank template
 skills/                        ← /create-mobile-app, /add-dataverse, /add-connector, /add-native, ...
-scripts/                       ← shared helpers: validate-mobile-files.js for skill-owned changed-file validation, metro-session.js for cross-host Metro session ownership/logging
+scripts/                       ← shared helpers: validate-mobile-files.js for skill-owned changed-file validation, metro-session.js for `.powernative` log status/tail
 hooks/                         ← Validator implementations invoked explicitly by mobile workflows
 ```
 
@@ -73,7 +73,7 @@ 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. **Metro lifecycle is project-local** — `/create-mobile-app` installs `scripts/metro-session.js` into the generated app and wires `npm run dev` through it; `/debug-app` reads `.expo/metro-session/state.json` and the sanitized `metro.log` with a persisted byte cursor. Do not restore required `BashOutput`/terminal-ID behavior. Host terminal APIs may be optional conveniences only. Never write unsanitized Metro output to disk, and never signal a recorded PID unless the port probe proves the process is still ours.
+11. **Metro lifecycle is project-local** — template `metro.config.js` writes sanitized `.powernative/metro-logs/` files during normal `npm run dev`; `/debug-app` uses `scripts/metro-session.js` only to locate/tail the latest live log with a persisted byte cursor. Do not restore required `BashOutput`/terminal-ID behavior. Host terminal APIs may be optional conveniences only. Never write unsanitized Metro output to disk, and never diagnose a log unless the port probe proves the logged PID still owns the port.
 
 ## Decisions made
 

plugins/mobile-apps/README.md

@@ -80,25 +80,20 @@ connector wiring.
 
 5. Start mobile app:
 
-	`/create-mobile-app` starts Metro automatically through the plugin's
-    project-local session manager. It stores sanitized logs and process state in
-    `.expo/metro-session/`, so `/debug-app` works after switching between VS Code,
-    Copilot CLI, and Claude Code without asking for a terminal ID.
+	`/create-mobile-app` starts Metro with the app's normal `npm run dev` command.
+    The template's Metro config stores sanitized logs in `.powernative/metro-logs/`,
+    so `/debug-app` works after switching between VS Code, Copilot CLI, and
+    Claude Code without asking for a terminal ID.
 
 	To start Metro manually instead, run the command below from the app directory.
-    Created apps wire this command through the same project-local wrapper, so
-    manual starts and `/debug-app` use the same captured log.
+    Manual starts and `/debug-app` use the same `.powernative` log source.
 
     ```bash
     npm run dev
     ```
 
-    Use `npm run dev:expo` only when you explicitly want raw Expo terminal
-    behavior and do not need `/debug-app` log capture.
-
-    The wrapper removes common credentials, tokens, keys, and signed-query
-    values before writing `metro.log`. The complete `.expo/` folder is ignored
-    by the template's `.gitignore`.
+    The Metro config removes sensitive lines before writing logs. The complete
+    `.powernative/` folder is ignored by the template's `.gitignore`.
 
 6. Preview the app by scanning the QR code with the Power Apps Developer app
 
@@ -227,7 +222,7 @@ Example edit flows:
 | `/add-native` | ✅ v0 | Add a supported native capability/control (camera, image-picker, barcode/QR scanner, document-picker, PDF viewer/report, pen/signature, secure-store, file-system, sharing, etc.) — verifies the module already ships in the template and writes typed wrappers under `src/native/` without installing native packages or editing `app.config.js` |
 | `/list-connections` | ✅ v0 | Finds or creates a Power Platform connection ID, or resolves a solution connection reference, for `npx power-apps add-data-source`. Use when adding non-Dataverse connectors or re-binding after a 401. |
 | `/edit-app` | ✅ v0 | Post-generation app editor — updates affected sections of `native-app-plan.md`, applies Dataverse/native/design/connector changes, rebuilds affected screens, runs verification, updates `memory-bank.md`, and regenerates `preview.html` when UI changed. `--plan-only` preserves the old docs-only behavior. |
-| `/debug-app` | ✅ v0 | Monitors the wrapper-owned `.expo/metro-session/metro.log` with a durable byte cursor, diagnoses runtime and silent data-path failures, applies bounded fixes, and verifies against newly appended output without depending on host terminal IDs. |
+| `/debug-app` | ✅ v0 | Monitors the latest live `.powernative/metro-logs/` file with a durable byte cursor, diagnoses runtime and silent data-path failures, applies bounded fixes, and verifies against newly appended output without depending on host terminal IDs. |
 | `/deploy` | ✅ v0 | Build + push — `npm run build` then `npx power-apps push` to the env in `power.config.json`. **Does not** drive `expo run:ios` or `expo run:android` (out of scope for v0). |
 | `/open-wrap-url` | ✅ v0 | Opens the Wrap URL in browser for an app ID using `https://make.powerapps.com/environments/<envID>/wrap?appID=<appID>`. Requires both `--app-id` and `--env-id`. |
 | `/report-issue` | ✅ v0 | Read-only diagnostic — collects env / Expo / Node versions, project context, recent errors, and renders a copy-paste-ready GitHub issue body. Sanitizes secrets. |