@mr.dj2u/knowledge 0.1.0 → 0.1.2

package/dist/content/checklists/{ship-test-loop.md → push-merge-loop.md}

@@ -1,4 +1,4 @@
-# Ship-Test Loop Checklist
+# Push-Merge Loop Checklist
 
 Use this checklist when running the PR loop into `test`.
 
@@ -14,3 +14,4 @@ Use this checklist when running the PR loop into `test`.
 10. Push and poll again.
 11. Repeat up to 5 cycles.
 12. Merge only when checks are green and blockers are cleared.
+

package/dist/content/checklists/unified-agent-bundle-validation.md

@@ -1,8 +1,9 @@
-# Unified Agent Bundle Validation Checklist
+# Unified Agent Bundle Validation Checklist
 
 Phase 9 validation artifact intent:
 
 1. Run Doctor (`--ci`) through the agent.
 2. Fetch one guide via MCP resource (`animation-performance`).
-3. Execute one CLI workflow (`mds continue` or `/ship-test-loop`).
+3. Execute one CLI workflow (`mds continue` or `/push-merge-loop`).
 4. Confirm tools/resources are visible in the target client.
+

package/dist/content/examples/{ship-test-loop.md → push-merge-loop.md}

@@ -1,6 +1,6 @@
-# Ship-Test Loop Example
+# Push-Merge Loop Example
 
-Example iteration log for `/ship-test-loop`:
+Example iteration log for `/push-merge-loop`:
 
 - Iteration 1:
   - Failed: `lint` and one requested review change.
@@ -11,3 +11,4 @@ Example iteration log for `/ship-test-loop`:
   - Fixes: update stale skill ID expectation.
   - Result: all checks green.
 - Merge: PR merged into `test`.
+

package/dist/content/guides/post-create-onboarding.md

@@ -19,14 +19,14 @@ onboarding pass.
    Uniwind repair for existing apps, Software Mansion core examples, Supabase or
    local data guidance, MCP/Codex/Claude instructions, and CI/release safeguards.
 6. Scaffold only selected pieces.
-7. Add generated cleanup scripts such as `clear-expo-start` and `free-port` (with `kill-port` compatibility alias).
+7. Add generated cleanup scripts such as `clear-expo-start` and `free-port`.
 8. Install added dependencies, run `expo install --fix`, install known missing
    Expo peers such as `expo-font` for `@expo/vector-icons`, then run Doctor.
 
 ## Agentic Onboarding (MCP)
 
 The terminal `mds onboard` command writes the project memory files. The
-agentic version is a conversation with Claude Code, Codex, or Cursor that
+agentic version is a conversation with Copilot, Claude Code, Codex, or Cursor that
 fills those files in collaboratively.
 
 Install **once, globally** (user scope, default) so every workspace gets
@@ -42,16 +42,17 @@ mds mcp install --dry-run         # preview merge before writing
 Restart the host (or run `claude mcp reload`) and the MDS prompts are
 available from any workspace.
 
-Two prompts ship with the server:
-
-- `create_expo_super_stack` — invoke from a **parent folder** (e.g.
-  `F:\ReactNativeApps`) when the app folder does not exist yet. The
-  agent confirms platforms, styling, data start, etc., then runs
-  `create-expo-super-stack`, verifies the generated app folder, and
-  offers to resolve TodoForContext markers.
-- `onboard_new_expo_app` — invoke from **inside an existing Expo app
-  folder** (a freshly generated one or a year-old project). Runs the
-  intake → normalize → plan → scaffold flow.
+Two prompts and several callable MDS MCP tools ship with the server:
+
+- `create_expo_super_stack` — invoke from a **parent folder** (e.g.
+  `F:\ReactNativeApps`) when the app folder does not exist yet. This is
+  now a thin orchestration prompt: the real guided intake happens
+  through `create_expo_super_stack_intake_step`, generation happens
+  through `create_expo_super_stack_generate`, and diagnostics come from
+  `mds_runtime_versions`.
+- `onboard_new_expo_app` — invoke from **inside an existing Expo app
+  folder** (a freshly generated one or a year-old project). Runs the
+  intake → normalize → plan → scaffold flow.
 
 After generation, the user-dev should open the generated app folder
 directly in a new agent session and run `mds continue`. That fresh
@@ -68,7 +69,7 @@ delete the marker line.
 error so the same blocker stops CI and editor surfaces until the user
 fills the section or deletes the marker line.
 
-### What's new in the agentic prompts
+### What's new in the agentic prompts and tools
 
 - **PHASE 0 file intake.** The agent offers to digest an existing
   `project/info.md` and `project/style.md` if the user has them already.
@@ -81,16 +82,23 @@ fills the section or deletes the marker line.
   with leanback config in `app.json`; Apple TV is a separate tvOS build
   target via `react-native-tvos`. Selecting either records the intent
   in project memory.
-- **Embedded flag map.** Both prompts now include the exact
-  create-expo-stack and `--mds-*` flag map so the agent does not have
-  to grep `node_modules` or scan source to translate answers into a
-  command. This was the biggest source of slowness in early test runs.
-- **Credits while waiting.** When generation kicks off, the agent
-  prints a recognition note for the upstream teams and individuals
-  whose work fills the MDS knowledge base.
+- **Shared CLI-backed intake contract.** The agentic CESS flow now uses
+  callable MCP tools backed by the shared `@mr.dj2u/cli` intake
+  contract. That keeps the questionnaire, defaults, dependency rules,
+  and flag mapping aligned with the published CLI behavior.
+- **No silent defaults.** Guided intake must explicitly collect answers
+  or explicitly present visible defaults. If the CESS intake tools are
+  unavailable, the agent should stop and tell the user to refresh the
+  plugin or MCP install instead of inventing `--mds-yes` defaults.
+- **Runtime version diagnostics.** `mds_runtime_versions` reports the
+  active MCP server version, CLI version, and the published
+  `create-expo-super-stack@latest` generation path in use.
+- **Credits while waiting.** When generation kicks off, the agent
+  prints a recognition note for the upstream teams and individuals
+  whose work fills the MDS knowledge base.
 - **Success message surfaced.** After a successful run, the agent
   quotes the generator's `MDS onboarding complete` tail block back
-  verbatim so the Mr. DJ thank-you text appears in chat the same way
+  verbatim so the Mr. DJ personal thank-you text appears in chat the same way
   it does in a terminal CLI run.
 - **MDS Continue handoff.** The agent runs `mds continue` from the
   generated app folder, then tells the user-dev to open that app folder
@@ -111,3 +119,37 @@ fills the section or deletes the marker line.
   `project/guidelines.md`.
 - Treat monorepo-aware scaffolding as a future step after the single-app MVP is
   stable.
+
+## VS Code & GitHub Copilot Integration
+
+This guide is authored as canonical knowledge consumed by agent bundles; it is not the agent itself. To enable the generated Copilot/VS Code surface and the custom MDS agent in a workspace, regenerate the VS Code bundle and install the generated prompts/settings into the target repository or your user profile.
+
+- Regenerate VS Code assets (from repository root):
+
+```powershell
+pnpm --filter @mr.dj2u/knowledge build:vscode
+```
+
+- Copy the generated workspace assets into your project (PowerShell):
+
+```powershell
+Copy-Item -Path .\plugins\vscode-copilot\.github\* -Destination . -Recurse -Force
+Copy-Item -Path .\plugins\vscode-copilot\.vscode\* -Destination .\.vscode -Recurse -Force
+```
+
+- Then restart VS Code. Ensure the `GitHub Copilot Chat` extension is installed and enabled. The generated `.vscode/settings.json` enables agent skill locations and prompt file lookup under `.github/prompts`.
+
+- If you prefer user-scope installs, copy the `user/.copilot` content into your user profile per the extension docs, or run `mds agent install --client codex --scope user` (if available) to automate the merge.
+
+## Install Path & What This MD Is For
+
+- This markdown is a human- and agent-facing guide. It documents the onboarding flow and explains what the agent prompts do. It is used as input to the `packages/knowledge` build which generates plugin/agent bundles for Codex, Claude Code, and VS Code Copilot.
+- The agent itself is not this file — it is a runtime that loads generated prompts/skills from the plugin bundles or the MCP server. To activate the agent surfaces you must either:
+  - Install the MCP prompts via `mds mcp install --client <client>` (user or project scope), or
+  - Copy the generated plugin files from `plugins/vscode-copilot` / `plugins/codex` / `plugins/claude-code` into the target workspace or user profile and restart the corresponding client.
+- If a host keeps using stale prompt or plugin behavior after republish,
+  refresh the local plugin cache, reinstall the MDS MCP server, and run
+  `mds_runtime_versions` from the host surface to confirm which version
+  is actually active.
+
+If you want, I can: regenerate the VS Code bundle now, copy the assets into the current workspace, and verify Copilot sees the prompts. Say "Do it" and I'll run the build and copy steps for you.

package/dist/content/patterns/project/configuration-patterns.md

@@ -51,8 +51,8 @@ Configuration patterns establish consistent strategies for managing app configur
     
     "platforms": ["ios", "android", "web"],
     
-    "sdkVersion": "55.0.0",
-    "runtimeVersion": "55.0.0",
+    "sdkVersion": "56.0.0",
+    "runtimeVersion": "56.0.0",
     
     "web": {
       "output": "static",
@@ -178,7 +178,7 @@ export default ({ config }) => {
   "dependencies": {
     "react": "^19.0.0",
     "react-native": "^0.83.0",
-    "expo": "^55.0.0",
+    "expo": "^56.0.0",
     "expo-router": "^3.0.0",
     "zustand": "^4.4.0",
     "drizzle-orm": "^0.30.0",
@@ -456,4 +456,4 @@ export function useConfig() {
 ---
 
 *Pattern extracted from production repositories: DJsPortfolio, time2pay, not-hot-dog*
-*Examples: app.json, app.config.js, metro.config.js, babel.config.js, tsconfig.json*
+*Examples: app.json, app.config.js, metro.config.js, babel.config.js, tsconfig.json*

package/dist/content/patterns/project/documentation-org.md

@@ -2,19 +2,19 @@
 
 ## Description
 
-Documentation organization establishes consistent structure for project metadata, guides, and architectural decisions. This pattern uses structured markdown files in dedicated `project/` directories alongside inline code documentation to keep knowledge accessible and maintainable.
-
-## MDS Project Memory Update
-
-New MDS onboarding uses four project memory files:
-
-- `project/info.md` for product intent and context.
-- `project/todo.md` for roadmap and next work.
-- `project/style.md` for visual/design direction only.
-- `project/guidelines.md` for technical rules, agent behavior, workflow, and architecture.
-
-Generated agent instructions should treat the `project/` folder as the source of
-truth and should not make changes that conflict with those files.
+Documentation organization establishes consistent structure for project metadata, guides, and architectural decisions. This pattern uses structured markdown files in dedicated `project/` directories alongside inline code documentation to keep knowledge accessible and maintainable.
+
+## MDS Project Memory Update
+
+New MDS onboarding uses four project memory files:
+
+- `project/info.md` for product intent and context.
+- `project/todo.md` for roadmap and next work.
+- `project/style.md` for visual/design direction only.
+- `project/guidelines.md` for technical rules, agent behavior, workflow, and architecture.
+
+Generated agent instructions should treat the `project/` folder as the source of
+truth and should not make changes that conflict with those files.
 
 ## When to Use
 
@@ -66,7 +66,7 @@ truth and should not make changes that conflict with those files.
 Personal portfolio and project showcase for David J Grimsley.
 
 ## Core Stack
-- **Framework**: Expo SDK 55 + React Native 0.83
+- **Framework**: Expo SDK 56 + React Native 0.85
 - **Routing**: Expo Router (file-based)
 - **Styling**: Uniwind v1.2.6 + Tailwind v4
 - **State**: Zustand (atomic stores)
@@ -503,4 +503,4 @@ pnpm typecheck        # Check types
 ---
 
 *Pattern extracted from production repositories: DJsPortfolio, not-hot-dog*
-*Examples: project/info.md, project/style.md, copilot-instructions.md*
+*Examples: project/info.md, project/style.md, copilot-instructions.md*

package/dist/content/patterns/project/monorepo-structure.md

@@ -179,7 +179,7 @@ ignore:
     
     "react": "^19.0.0",
     "react-native": "^0.83.0",
-    "expo": "^55.0.0",
+    "expo": "^56.0.0",
     "expo-router": "^3.0.0",
     "zustand": "^4.4.0"
   },
@@ -496,5 +496,5 @@ core-monorepo/
 
 ---
 
-*Pattern extracted from production monorepos: core-monorepo (3 apps, 6 packages), mds-dev-suite*
-*Examples: pnpm-workspace.yaml, turbo.json, tsconfig.base.json, workspace:* references*
+*Pattern extracted from production monorepos: core-monorepo (3 apps, 6 packages), Mr. DJ's Dev Suite*
+*Examples: pnpm-workspace.yaml, turbo.json, tsconfig.base.json, workspace:* references*

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

@@ -1,4 +1,4 @@
-# /continue-development
+# /continue-development
 
 Resume work on an onboarded project by following MDS phase order from `project/todo.md`.
 
@@ -8,18 +8,26 @@ Resume work on an onboarded project by following MDS phase order from `project/t
 
 ## MCP-First Workflow
 
-1. Confirm the `mds-dev-suite` MCP server is available.
+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.
 
+## MDS Routing Guardrails
+
+- Treat a request to continue development with MDS as a request for the MDS MCP tool and 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`
+   - `mds mcp install --client <client> --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
 

package/dist/content/prompts/create-expo-super-stack.md

@@ -1,29 +1,31 @@
-# /create-expo-super-stack
-
-Create a new Expo app with the MDS Super Stack flow, then hand off to phase-based continuation.
-
-## Arguments
-
-- `parentDir`: folder where the new app directory should be created.
-- `appName`: app folder name.
-
-## MCP-First Workflow
-
-1. Confirm the `mds-dev-suite` MCP server is available.
-2. Invoke the MCP prompt `create_expo_super_stack` from a parent directory.
-3. Follow the prompt intake flow and keep one question per turn until generation completes.
-4. 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:
-   - `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.
+# /create-expo-super-stack
+
+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.
+
+## Required MDS MCP Tool Flow
+
+1. Confirm the `mr-djs-dev-suite` MCP server is available.
+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`.
+
+## Failure Behavior
+
+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 the handoff to open a fresh agent session inside the new app folder and run `mds continue`.

package/dist/content/prompts/fix-seo.md

@@ -1,4 +1,4 @@
-# /fix-seo
+# /fix-seo
 
 Apply SEO metadata fixes for Expo web routes with MCP guidance and post-fix verification.
 
@@ -9,7 +9,7 @@ Apply SEO metadata fixes for Expo web routes with MCP guidance and post-fix veri
 
 ## MCP-First Workflow
 
-1. Confirm the `mds-dev-suite` MCP server is available.
+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.
@@ -18,7 +18,7 @@ Apply SEO metadata fixes for Expo web routes with MCP guidance and post-fix veri
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
-   - `mds mcp install --client codex --scope project`
+   - `mds mcp install --client <client> --scope project`
 2. Direct CLI checks:
    - `mds doctor <projectPath> --ci`
    - Run project-specific web build/preview commands to verify metadata output.

package/dist/content/prompts/prepare-deploy.md

@@ -1,4 +1,4 @@
-# /prepare-deploy
+# /prepare-deploy
 
 Prepare an Expo project for release using deployment-focused skills plus Doctor parity checks.
 
@@ -9,7 +9,7 @@ Prepare an Expo project for release using deployment-focused skills plus Doctor
 
 ## MCP-First Workflow
 
-1. Confirm the `mds-dev-suite` MCP server is available.
+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.
@@ -18,7 +18,7 @@ Prepare an Expo project for release using deployment-focused skills plus Doctor
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
-   - `mds mcp install --client codex --scope project`
+   - `mds mcp install --client <client> --scope project`
 2. Direct CLI path:
    - `mds doctor <projectPath> --ci`
    - Run project scripts: `lint`, `type-check`, `test`, and production build/profile scripts.

package/dist/content/prompts/project-research-plan.md

@@ -1,4 +1,4 @@
-# /project-research-plan
+# /project-research-plan
 
 Turn rough product notes/research into actionable MDS project memory and next-phase plan.
 
@@ -9,7 +9,7 @@ Turn rough product notes/research into actionable MDS project memory and next-ph
 
 ## MCP-First Workflow
 
-1. Confirm the `mds-dev-suite` MCP server is available.
+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.
@@ -18,7 +18,7 @@ Turn rough product notes/research into actionable MDS project memory and next-ph
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
-   - `mds mcp install --client codex --scope project`
+   - `mds mcp install --client <client> --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.

package/dist/content/prompts/{ship-test-loop.md → push-merge-loop.md}

@@ -1,4 +1,4 @@
-# /ship-test-loop
+# /push-merge-loop
 
 Execute the short PR iteration loop for the test branch with strict quality gates.
 
@@ -22,3 +22,4 @@ Push intentional changes with a meaningful commit message, open/update a PR to `
 - Do not skip Doctor between fix cycles.
 - Keep a concise changelog per iteration: what failed, what was changed, what passed.
 - If still failing after 5 cycles, stop and summarize remaining blockers with concrete next actions.
+

package/dist/content/prompts/review-expo-project.md

@@ -1,4 +1,4 @@
-# /review-expo-project
+# /review-expo-project
 
 Review an Expo project with MCP-first diagnostics and skill-guided remediation.
 
@@ -9,7 +9,7 @@ Review an Expo project with MCP-first diagnostics and skill-guided remediation.
 
 ## MCP-First Workflow
 
-1. Confirm the `mds-dev-suite` MCP server is available.
+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`).
@@ -18,7 +18,7 @@ Review an Expo project with MCP-first diagnostics and skill-guided remediation.
 ## CLI / Manual Fallback
 
 1. If MCP is not configured, install it manually:
-   - `mds mcp install --client codex --scope project`
+   - `mds mcp install --client <client> --scope project`
 2. If MCP still cannot run, use direct CLI flows:
    - `mds continue <projectPath>`
    - `mds doctor <projectPath> --ci`

package/dist/content/prompts/run-doctor.md

@@ -1,4 +1,4 @@
-# /run-doctor
+# /run-doctor
 
 Run MDS Doctor as the primary health check for an Expo project.
 
@@ -10,19 +10,27 @@ Run MDS Doctor as the primary health check for an Expo project.
 
 ## MCP-First Workflow
 
-1. Confirm the `mds-dev-suite` MCP server is available.
+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. Pull targeted implementation guidance with `get_skill` (typically `deployment`, `debugging`, or `dev-server-management`).
 
+## MDS Routing Guardrails
+
+- Treat a request to run MDS Doctor as a request for the MDS 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`
+   - `mds mcp install --client <client> --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
 

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

@@ -0,0 +1,67 @@
+# /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.

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.