@mr.dj2u/knowledge 0.1.7 → 0.1.9

package/dist/content/prompts/wrap-up.md

@@ -1,67 +1,70 @@
-# /wrap-up
-
-Run the post-testing release wrap-up flow: final local checks, git inclusion confirmation, PR loop, and merge handling.
-
-## Goal
-
-When the developer says testing is complete, finish the handoff safely by:
-
-1. Marking completed todo items.
-2. Running `mds doctor --ci`.
-3. Reviewing `git status` and confirming intentionally excluded files.
-4. Running the publish/PR/check loop.
-5. Handling merge according to policy defaults and repo overrides.
-
-## Required Flow Order
-
-1. Update `project/todo.md` only for tasks clearly completed in this session.
-2. Run `mds doctor --ci` before any git mutation.
-3. Review `git status --short` and list changed files.
-4. Confirm any intentionally omitted files with the developer before staging.
-5. Publish through GitHub flow (branch push + PR).
-6. Poll checks and unresolved feedback.
-7. Fix failures locally, rerun Doctor, push updates, and poll again.
-8. Repeat up to 5 cycles total.
-
-## GitHub Skill Routing
-
-Use GitHub workflows in this order when available:
-
-1. `github` for repo/PR context and routing.
-2. `yeet` for commit/push/open-or-update PR flow.
-3. `gh-fix-ci` for failed checks/log inspection and CI-driven fix loops.
-4. `gh-address-comments` when unresolved review threads are blocking merge.
-
-## Merge Policy
-
-Evaluate policy in this order:
-
-1. Explicit user instruction in the current session.
-2. Optional repo config at `project/release-policy.json`.
-3. Defaults if config is absent.
-
-Supported repo config shape:
-
-```json
-{
-  "wrapUp": {
-    "autoMergeTest": true,
-    "autoMergeMain": false
-  }
-}
-```
-
-Default behavior:
-
-- Auto-merge to `test`: enabled.
-- Per-repo override: allowed.
-- Auto-merge to `main`: never allowed.
-
-If the workflow targets `main` directly (no `test` branch flow), stop before merge and tell the developer to merge manually.
-
-## Guardrails
-
-- Never auto-merge to `main`.
-- Do not skip `mds doctor --ci` between fix cycles.
-- Do not assume omitted files are intentional; confirm them.
-- If checks or blocking threads still fail after 5 cycles, stop and request human help with a concise blocker summary.
+# /wrap-up
+
+Run the post-testing release wrap-up flow: final local checks, git inclusion confirmation, PR loop, and merge handling.
+
+## Goal
+
+When the developer says testing is complete, finish the handoff safely by:
+
+1. Marking completed todo items.
+2. Running `mds doctor --ci`.
+3. Reviewing `git status` and confirming intentionally excluded files.
+4. Running the publish/PR/check loop.
+5. Handling merge according to policy defaults and repo overrides.
+
+## Required Flow Order
+
+1. Preserve `project/todo.md` exactly except for the verified completion of
+   the exact task worked in this session; add its nested GitHub PR link only
+   after the mapping and final-base reachability are proven, or a reachable
+   commit link for directly verified pre-PR work.
+2. Run `mds doctor --ci` before any git mutation.
+3. Review `git status --short` and list changed files.
+4. Confirm any intentionally omitted files with the developer before staging.
+5. Publish through GitHub flow (branch push + PR).
+6. Poll checks and unresolved feedback.
+7. Fix failures locally, rerun Doctor, push updates, and poll again.
+8. Repeat up to 5 cycles total.
+
+## GitHub Skill Routing
+
+Use GitHub workflows in this order when available:
+
+1. `github` for repo/PR context and routing.
+2. `yeet` for commit/push/open-or-update PR flow.
+3. `gh-fix-ci` for failed checks/log inspection and CI-driven fix loops.
+4. `gh-address-comments` when unresolved review threads are blocking merge.
+
+## Merge Policy
+
+Evaluate policy in this order:
+
+1. Explicit user instruction in the current session.
+2. Optional repo config at `project/release-policy.json`.
+3. Defaults if config is absent.
+
+Supported repo config shape:
+
+```json
+{
+  "wrapUp": {
+    "autoMergeTest": true,
+    "autoMergeMain": false
+  }
+}
+```
+
+Default behavior:
+
+- Auto-merge to `test`: enabled.
+- Per-repo override: allowed.
+- Auto-merge to `main`: never allowed.
+
+If the workflow targets `main` directly (no `test` branch flow), stop before merge and tell the developer to merge manually.
+
+## Guardrails
+
+- Never auto-merge to `main`.
+- Do not skip `mds doctor --ci` between fix cycles.
+- Do not assume omitted files are intentional; confirm them.
+- If checks or blocking threads still fail after 5 cycles, stop and request human help with a concise blocker summary.

package/dist/content/reference/create-expo-stack-uniwind.md

@@ -1,29 +1,29 @@
-# create-expo-stack Uniwind Exploration
-
-Source: https://github.com/roninoss/create-expo-stack
-
-## Findings
-
-- The project describes itself as an interactive CLI for `rn-new`.
-- It already supports multiple styling choices, including NativeWind,
-  Unistyles, StyleSheets, and Tamagui.
-- The README describes a per-file template model: base files live in a base
-  template folder, while optional package features live in package template
-  folders and use EJS to patch shared files.
-
-## Phase 1 Decision
-
-A friendly upstream Uniwind contribution should stay small:
-
-- add Uniwind as another styling option,
-- follow the existing package-slice template convention,
-- include `web` in Expo Router generated `app.json` platforms when web config
-  and dependencies are generated,
-- add focused Software Mansion core package options where they are not already
-  covered,
-- avoid MDS project memory files, MCP config, agent prompts, or richer
-  boilerplate,
-- keep the deeper post-create setup in `mds onboard` and
-  `create-expo-super-stack`.
-
-No local Phase 1 code should depend on the upstream fork or PR existing.
+# create-expo-stack Uniwind Exploration
+
+Source: https://github.com/roninoss/create-expo-stack
+
+## Findings
+
+- The project describes itself as an interactive CLI for `rn-new`.
+- It already supports multiple styling choices, including NativeWind,
+  Unistyles, StyleSheets, and Tamagui.
+- The README describes a per-file template model: base files live in a base
+  template folder, while optional package features live in package template
+  folders and use EJS to patch shared files.
+
+## Phase 1 Decision
+
+A friendly upstream Uniwind contribution should stay small:
+
+- add Uniwind as another styling option,
+- follow the existing package-slice template convention,
+- include `web` in Expo Router generated `app.json` platforms when web config
+  and dependencies are generated,
+- add focused Software Mansion core package options where they are not already
+  covered,
+- avoid MDS project memory files, MCP config, agent prompts, or richer
+  boilerplate,
+- keep the deeper post-create setup in `mds onboard` and
+  `create-expo-super-stack`.
+
+No local Phase 1 code should depend on the upstream fork or PR existing.

package/dist/content/reference/doctor-dogfood.md

@@ -19,7 +19,7 @@ prove Doctor handles real Expo and monorepo shapes without crashing.
 
 - `doctor --json --scripts=false` completes for each target.
 - Reports include project docs, package scripts, env hygiene, Expo config, SSR,
-  SEO, and app architecture where applicable.
+  runtime security, SEO, and app architecture where applicable.
 - Findings are actionable and avoid leaking env values.
 
 ## Phase 1 Run Summary

package/dist/content/reference/mcp-sdk-transport.md

@@ -1,30 +1,30 @@
-# MCP SDK Transport Pattern
-
-Source pattern: `mds-app-mcp/src/index.ts`.
-
-## Core Shape
-
-- Create a high-level `McpServer` from `@modelcontextprotocol/sdk/server/mcp.js`.
-- Register static markdown resources with stable `mds://` URIs.
-- Register tools with schemas and handlers that return MCP text content.
-- Register prompts for reusable agent workflows.
-- Connect with `StdioServerTransport` for local agent use.
-- Keep HTTP/SSE transport as a later hosting concern unless a client needs it.
-
-## MDS Suite Decision
-
-Phase 1 uses stdio as the production MCP transport because it works for local
-Codex/Claude workflows and avoids server lifecycle complexity. The server
-still exposes pure functions for tests and direct CLI verification:
-
-- `createMrdjMcpServer()`
-- `startStdioServer()`
-- `listResources()`
-- `readResource(uri)`
-- `executeTool(name, input)`
-
-## Resource Rule
-
-MCP resources must be generated from `packages/knowledge`, not hand-copied into
-`packages/mcp-server`.
-
+# MCP SDK Transport Pattern
+
+Source pattern: `mds-app-mcp/src/index.ts`.
+
+## Core Shape
+
+- Create a high-level `McpServer` from `@modelcontextprotocol/sdk/server/mcp.js`.
+- Register static markdown resources with stable `mds://` URIs.
+- Register tools with schemas and handlers that return MCP text content.
+- Register prompts for reusable agent workflows.
+- Connect with `StdioServerTransport` for local agent use.
+- Keep HTTP/SSE transport as a later hosting concern unless a client needs it.
+
+## MDS Suite Decision
+
+Phase 1 uses stdio as the production MCP transport because it works for local
+Codex/Claude workflows and avoids server lifecycle complexity. The server
+still exposes pure functions for tests and direct CLI verification:
+
+- `createMrdjMcpServer()`
+- `startStdioServer()`
+- `listResources()`
+- `readResource(uri)`
+- `executeTool(name, input)`
+
+## Resource Rule
+
+MCP resources must be generated from `packages/knowledge`, not hand-copied into
+`packages/mcp-server`.
+

package/dist/content/reference/reference-repo-evacuation.md

@@ -1,31 +1,31 @@
-# Reference Repo Evacuation
-
-Phase 1 captured the useful patterns from the temporary multi-root workspace so
-Mr. DJ's Dev Suite can run from a clean single-folder workspace.
-
-## Captured Sources
-
-| Source repo | Captured knowledge | Suite destination |
-| --- | --- | --- |
-| `mds-app-mcp` | MCP SDK server construction, stdio transport, resource registration, prompt registration, and guide loading pattern. | `reference/mcp-sdk-transport.md`, MCP server implementation |
-| `mds-pokemon-mcp` | MCP family naming and guide/resource convention. | Knowledge resource URI rules |
-| `mds-fne-mcp` | MCP family naming and tool/resource split. | Knowledge resource URI rules |
-| `time2pay` | Uniwind setup, CI-equivalent checks, env handling, Expo deployment shape, Doctor dogfood target. | Patterns, Doctor fixtures, `reference/doctor-dogfood.md` |
-| `DJsPortfolio` | API route proxy patterns, Drizzle schema examples, docs organization, route structure, Doctor dogfood target. | API/database/project patterns |
-| `PokePages` | Dynamic route hierarchies, Zustand stores, Drizzle migrations, Doctor dogfood target. | Routing/state/database patterns |
-| `not-hot-dog` | Small app route structure and docs memory convention. | Project/routing patterns |
-| `expo-super-template` | Post-create defaults, Uniwind Metro/global CSS setup, onboarding target shape, Doctor dogfood target. | Styling/onboarding guides |
-| `core-monorepo` | Turborepo package layout, shared package exports, package-manager detection, Doctor dogfood target. | Project/deployment patterns |
-| `mercury-bank-sdk` | Library package export fields, npm workspace scripts, build/test/typecheck workflow. | Project/library and package CI patterns |
-| `ads-sdk` | Small TypeScript SDK package shape and publish build workflow. | Package/CI reference notes |
-| `quantum-api` | Dual ESM/CJS SDK build pattern and generated package metadata workflow. | Package/CI reference notes |
-
-## Evacuation Rules
-
-- Keep repo names and relative file paths as source notes; do not depend on
-  machine-specific absolute paths.
-- Keep reference repos read-only during harvest.
-- Delete `temp/` clones after their patterns are promoted or intentionally
-  discarded.
-- A new engineer should be able to open only Mr. DJ's Dev Suite and still access
-  all Phase 1 knowledge through `packages/knowledge`.
+# Reference Repo Evacuation
+
+Phase 1 captured the useful patterns from the temporary multi-root workspace so
+Mr. DJ's Dev Suite can run from a clean single-folder workspace.
+
+## Captured Sources
+
+| Source repo | Captured knowledge | Suite destination |
+| --- | --- | --- |
+| `mds-app-mcp` | MCP SDK server construction, stdio transport, resource registration, prompt registration, and guide loading pattern. | `reference/mcp-sdk-transport.md`, MCP server implementation |
+| `mds-pokemon-mcp` | MCP family naming and guide/resource convention. | Knowledge resource URI rules |
+| `mds-fne-mcp` | MCP family naming and tool/resource split. | Knowledge resource URI rules |
+| `time2pay` | Uniwind setup, CI-equivalent checks, env handling, Expo deployment shape, Doctor dogfood target. | Patterns, Doctor fixtures, `reference/doctor-dogfood.md` |
+| `DJsPortfolio` | API route proxy patterns, Drizzle schema examples, docs organization, route structure, Doctor dogfood target. | API/database/project patterns |
+| `PokePages` | Dynamic route hierarchies, Zustand stores, Drizzle migrations, Doctor dogfood target. | Routing/state/database patterns |
+| `not-hot-dog` | Small app route structure and docs memory convention. | Project/routing patterns |
+| `expo-super-template` | Post-create defaults, Uniwind Metro/global CSS setup, onboarding target shape, Doctor dogfood target. | Styling/onboarding guides |
+| `core-monorepo` | Turborepo package layout, shared package exports, package-manager detection, Doctor dogfood target. | Project/deployment patterns |
+| `mercury-bank-sdk` | Library package export fields, npm workspace scripts, build/test/typecheck workflow. | Project/library and package CI patterns |
+| `ads-sdk` | Small TypeScript SDK package shape and publish build workflow. | Package/CI reference notes |
+| `quantum-api` | Dual ESM/CJS SDK build pattern and generated package metadata workflow. | Package/CI reference notes |
+
+## Evacuation Rules
+
+- Keep repo names and relative file paths as source notes; do not depend on
+  machine-specific absolute paths.
+- Keep reference repos read-only during harvest.
+- Delete `temp/` clones after their patterns are promoted or intentionally
+  discarded.
+- A new engineer should be able to open only Mr. DJ's Dev Suite and still access
+  all Phase 1 knowledge through `packages/knowledge`.

package/dist/content/resource-index.json

@@ -39,6 +39,7 @@
   "prompts/prepare-deploy.md",
   "prompts/project-research-plan.md",
   "prompts/push-merge-loop.md",
+  "prompts/retrospective-project-onboarding.md",
   "prompts/review-expo-project.md",
   "prompts/review-motion.md",
   "prompts/run-doctor.md",

package/dist/content/rules/env-hygiene.md

@@ -7,3 +7,13 @@ Treat names containing `SECRET`, `SERVICE_ROLE`, `PRIVATE`, `PASSWORD`,
 `TOKEN`, or `STRIPE_SECRET` as unsafe when they are prefixed with
 `EXPO_PUBLIC_`.
 
+Document every `EXPO_PUBLIC_*` key from `.env.local` in a committed
+`.env.example` (empty or placeholder values only). Example/template env files
+must not contain live-looking secrets.
+
+Doctor also reports context-gated hardcoded credential values in source and
+configuration files, including Stripe `sk_`/`pk_`, OpenAI `sk-`, AWS `AKIA`
+keys, and Bearer/JWT tokens. Reports must identify only the file, line, safe
+identifier, detector, and remediation; never print the credential value itself.
+Real gitignored env files are the correct place for secrets.
+

package/dist/content/rules/ssr-safety.md

@@ -7,3 +7,10 @@ Warn on unguarded `window`, `document`, `localStorage`, `sessionStorage`, and
 `navigator` references in route files. Prefer `useEffect`, explicit
 `typeof window !== 'undefined'` guards, or a storage adapter.
 
+Do not import server-only modules into client routes. Database clients
+(`prisma`, `drizzle-orm`), Node server frameworks (`express`), `'use server'`
+files, and `*.server.ts` modules belong behind API routes or server entry
+points. Client code may only read `EXPO_PUBLIC_*` (plus `NODE_ENV` and
+`EXPO_OS`). Doctor's `runtime security` check enforces this server-on-client
+boundary; the browser-global scan remains a separate warning.
+

package/dist/content/skills/api-routes.md

@@ -1,33 +1,34 @@
-# Skill: API Routes
-
-Use when creating, reviewing, or debugging Expo Router API route handlers.
-
-## Main rule
-
-Keep route handlers thin and defensive: validate input, enforce auth/authorization before data access, and return consistent typed responses.
-
-## Checks
-
-- Confirm each endpoint handles allowed methods explicitly and rejects unsupported methods.
-- Validate request params/body with schema guards before business logic executes.
-- Enforce auth first for privileged operations; never rely on client-provided roles.
-- Keep service-role credentials on server-only paths and avoid exposing them to client bundles.
-- Confirm error responses are structured and safe (no stack traces or secret values).
-
-## Preferred structure
-
-- Use one route module per resource concern.
-- Parse and validate request data first, then call feature/service logic.
-- Keep DB and external API logic in service modules, not inline in route files.
-- Use a shared response envelope pattern for success and failure paths.
-
-## Example fix
-
-- Problem: A `POST` route writes directly to DB with unchecked body data.
-- Fix: Add schema validation, early auth check, and move write logic into a service function before returning a typed response object.
-
-## Agent behavior
-
-- Apply the smallest safe refactor that adds validation/auth boundaries first.
-- Delegate framework primitive questions to official Expo API route guidance, then layer MDS project-specific rules (env boundaries, doc updates, Doctor compatibility).
-
+# Skill: API Routes
+
+Use when creating, reviewing, or debugging Expo Router API route handlers.
+
+## Main rule
+
+Keep route handlers thin and defensive: validate input, enforce auth/authorization before data access, and return consistent typed responses.
+
+## Checks
+
+- Confirm each endpoint handles allowed methods explicitly and rejects unsupported methods.
+- Validate request params/body with schema guards before business logic executes.
+- Enforce auth first for privileged operations; never rely on client-provided roles.
+- Keep service-role credentials on server-only paths and avoid exposing them to client bundles.
+- Confirm error responses are structured and safe (no stack traces or secret values).
+- Doctor flags these patterns via the `api safety` check (`mds explain "api safety"`).
+
+## Preferred structure
+
+- Use one route module per resource concern.
+- Parse and validate request data first, then call feature/service logic.
+- Keep DB and external API logic in service modules, not inline in route files.
+- Use a shared response envelope pattern for success and failure paths.
+
+## Example fix
+
+- Problem: A `POST` route writes directly to DB with unchecked body data.
+- Fix: Add schema validation, early auth check, and move write logic into a service function before returning a typed response object.
+
+## Agent behavior
+
+- Apply the smallest safe refactor that adds validation/auth boundaries first.
+- Delegate framework primitive questions to official Expo API route guidance, then layer MDS project-specific rules (env boundaries, doc updates, Doctor compatibility).
+

package/dist/content/skills/continue-development.md

@@ -1,32 +1,49 @@
-# Skill: Continue Development
-
-Use when resuming work on an onboarded app and selecting the next task from `project/todo.md`.
-
-## Main rule
-
-Continue phase-by-phase: finish in-progress phase items first, and only defer/move tasks with an explicit note and user confirmation.
-
-## Checks
-
-- Confirm project memory files are present and current before task selection.
-- Identify the active phase and incomplete tasks in `project/todo.md`.
-- Confirm blockers/context markers are resolved before feature implementation.
-- Confirm any deferral includes a clear reason and destination note.
-- Re-run Doctor/checks after significant phase tasks are completed.
-
-## Preferred structure
-
-- Start each session by summarizing current phase state and next recommended task.
-- Keep task updates minimal and explicit in `project/todo.md`.
-- Keep roadmap changes aligned with product intent in `project/info.md`.
-
-## Example fix
-
-- Problem: Agent jumps to a later phase feature while current phase has unresolved blockers.
-- Fix: Return to active phase tasks, complete or formally defer blockers, then proceed to later phase work.
-
-## Agent behavior
-
-- Optimize for forward progress without losing roadmap integrity.
-- Avoid silently reordering roadmap priorities; ask for confirmation before major sequencing changes.
-- Treat this as an MDS-only workflow skill: use official Expo or React Native guidance for framework mechanics, then apply MDS phase order, project memory, and Doctor checks.
+# Skill: Continue Development
+
+Use when resuming work on an onboarded app and selecting the next task from `project/todo.md`.
+
+## Main rule
+
+Continue phase-by-phase: finish in-progress phase items first, and only defer/move tasks with an explicit note and user confirmation.
+
+## Checks
+
+- Confirm project memory files are present and current before task selection.
+- Identify the relevant phase and incomplete tasks in `project/todo.md`.
+  Phase order expresses product evolution and priority; explicit dependencies
+  and user priority decide whether a later-phase task may start.
+- Confirm blockers/context markers are resolved before feature implementation.
+- If `continue_project` or `mds continue` reports `priority: expo-sdk-upgrade`, load the official Expo skill `upgrading-expo`. Do not call MDS `get_skill` for an upgrade skill, and do not take the next todo until the user declines or the upgrade is done.
+- Confirm any deferral includes a clear reason and destination note.
+- Re-run Doctor/checks after significant phase tasks are completed.
+- When this MDS workflow itself adds a package, use an MDS-owned tool
+  (`mds library add` for catalog items) or immediately run the project's
+  package manager, then confirm `node_modules` contains the new package.
+  Do not treat the task as complete if install failed. MDS cannot install
+  packages added by a third-party agent outside those tools.
+
+## Preferred structure
+
+- Start each session by summarizing the relevant phase state, explicit
+  dependencies, and next recommended task.
+- Preserve every existing TODO line. After direct verification, mark only the
+  exact completed checkbox and add a nested GitHub PR link when its
+  final-base reachability is proven; use a reachable commit link for directly
+  verified pre-PR work. Append new work only with human-approved wording to
+  the end of its explicitly selected phase. Record a defect once in the
+  central `## Bug Fixes & Regressions` queue as
+  `[Bug · Origin: Phase N]`, not in both that queue and its origin phase.
+- Keep roadmap changes aligned with product intent in `project/info.md`.
+
+## Example fix
+
+- Problem: Agent jumps to a later phase feature while current phase has unresolved blockers.
+- Fix: Return to active phase tasks, complete or formally defer blockers, then proceed to later phase work.
+- Problem: Agent picks the first unchecked todo while the app's declared Expo SDK is a major behind official latest stable.
+- Fix: Honor `expo-sdk-upgrade` from `continue_project` / `mds continue` and load official `upgrading-expo` instead of implementing the stale todo.
+
+## Agent behavior
+
+- Optimize for forward progress without losing roadmap integrity.
+- Avoid silently reordering roadmap priorities; ask for confirmation before major sequencing changes.
+- Treat this as an MDS-only workflow skill: use official Expo or React Native guidance for framework mechanics, then apply MDS phase order, project memory, and Doctor checks.

package/dist/content/skills/debugging.md

@@ -1,32 +1,32 @@
-# Skill: Debugging
-
-Use when diagnosing broken behavior, flaky tooling, or unclear failures in Expo projects.
-
-## Main rule
-
-Debug by narrowing scope quickly: reproduce, isolate, capture evidence, apply the smallest safe fix, then verify.
-
-## Checks
-
-- Reproduce the issue consistently and record exact command/path/error output.
-- Confirm environment assumptions (platform, output mode, env vars, script path) match the failing context.
-- Run targeted checks first (`mds doctor`, focused tests, route/file scans) before broad reruns.
-- Separate root-cause signals from secondary cascade errors.
-- Re-verify with the same reproduction path after the fix.
-
-## Preferred structure
-
-- Keep debugging notes concise in task output or project memory when the issue is recurring.
-- Prefer deterministic scripts over ad-hoc manual sequences.
-- Escalate from narrow test scope to broader validation only after targeted checks pass.
-
-## Example fix
-
-- Problem: Route crashes only on web server output with ambiguous stack traces.
-- Fix: Reproduce in server mode, isolate browser-global usage in shared module, add guards, rerun targeted test and Doctor scan.
-
-## Agent behavior
-
-- Start with high-risk failures (security, data loss, crashers), then address lower-risk warnings.
-- Keep users unblocked with concrete next commands and avoid speculative broad refactors before evidence is clear.
-- Delegate framework primitive questions to official Expo or React Native guidance, then apply MDS reproduction discipline, Doctor checks, and project-memory context.
+# Skill: Debugging
+
+Use when diagnosing broken behavior, flaky tooling, or unclear failures in Expo projects.
+
+## Main rule
+
+Debug by narrowing scope quickly: reproduce, isolate, capture evidence, apply the smallest safe fix, then verify.
+
+## Checks
+
+- Reproduce the issue consistently and record exact command/path/error output.
+- Confirm environment assumptions (platform, output mode, env vars, script path) match the failing context.
+- Run targeted checks first (`mds doctor`, focused tests, route/file scans) before broad reruns.
+- Separate root-cause signals from secondary cascade errors.
+- Re-verify with the same reproduction path after the fix.
+
+## Preferred structure
+
+- Keep debugging notes concise in task output or project memory when the issue is recurring.
+- Prefer deterministic scripts over ad-hoc manual sequences.
+- Escalate from narrow test scope to broader validation only after targeted checks pass.
+
+## Example fix
+
+- Problem: Route crashes only on web server output with ambiguous stack traces.
+- Fix: Reproduce in server mode, isolate browser-global usage in shared module, add guards, rerun targeted test and Doctor scan.
+
+## Agent behavior
+
+- Start with high-risk failures (security, data loss, crashers), then address lower-risk warnings.
+- Keep users unblocked with concrete next commands and avoid speculative broad refactors before evidence is clear.
+- Delegate framework primitive questions to official Expo or React Native guidance, then apply MDS reproduction discipline, Doctor checks, and project-memory context.