@yemi33/minions 0.1.2363 → 0.1.2365

package/docs/onboarding.md

@@ -1,246 +1,124 @@
-# Minions Onboarding — Your First 30 Minutes
+# Minions Onboarding: Your First 30 Minutes
 
-A fast, hands-on walkthrough for new contributors. Follow the eight steps below in order. Each step is independent enough that you can stop, take a break, and resume without losing state.
+This condensed operator walkthrough gets one repository from installation to a
+completed first dispatch. For deeper, progressive exercises, use the
+[full tutorial track](tutorials/README.md).
 
-> **Prerequisites:** Node.js 22.5+ (required by `package.json#engines` for the `node:sqlite` runtime backing the state DB), Git, and a working Claude Code CLI (`npm install -g @anthropic-ai/claude-code`) authenticated against your Anthropic API key or Claude Max subscription. See the top-level [README.md](../README.md#prerequisites) for the full list.
+## Prerequisites
 
-> **Screenshots:** This walkthrough is intentionally text-only on the first pass. If you want annotated dashboard screenshots, run the [`capture-demos`](../README.md#dashboard) skill after Step 5; it drives Playwright over the running dashboard and writes images you can drop alongside each section.
+- Node.js 22.5 or newer
+- Git
+- One supported runtime CLI with working authentication
+- A local Git repository you are comfortable allowing an agent to change
 
----
+Minions defaults to GitHub Copilot CLI. Claude Code and Codex are also
+supported.
 
-## Step 1 — Clone the repo
-
-You only need to clone if you intend to modify Minions itself. End users normally `npm install -g @yemi33/minions` instead, but a checkout is the right starting point for contributors.
-
-```bash
-git clone https://github.com/yemi33/minions.git ~/minions-dev
-cd ~/minions-dev
-npm install     # installs dev tooling (Playwright, ESLint) only; the engine itself has zero runtime deps (Node built-ins)
-```
-
-You should now have:
-
-- `engine.js` — the orchestrator entry point
-- `dashboard.js` — the HTTP/UI server (binds `:7331`)
-- `minions.js` — the CLI shim that maps `minions <cmd>` to the right script
-- `playbooks/`, `agents/`, `prompts/`, `docs/` — content the engine renders into agent prompts
-- `test/` — `unit.test.js`, the integration suite, and Playwright specs
-
-If you cloned to somewhere other than `~/.minions`, the CLI will still work — `minions init` writes runtime state under `~/.minions/` regardless of where the source lives. The `node` scripts under your checkout will use the checkout as the runtime root when invoked directly (e.g. `node ./engine.js start`).
-
----
-
-## Step 2 — Run `minions doctor`
-
-`minions doctor` runs the same preflight checks the engine runs at startup. It is safe to run any time and never mutates state.
+## 1. Install and initialize
 
 ```bash
+npm install -g @yemi33/minions
+minions init
 minions doctor
 ```
 
-A healthy Mac/Linux run looks roughly like:
+Resolve every doctor `FAIL` before continuing. To select another runtime:
 
+```bash
+minions config set-cli claude
+# or: minions config set-cli codex
 ```
-  Runtime:
-
-    ✓ node: v20.11.1 (>= 18 required)
-    ✓ git: git version 2.45.0
-    ✓ claude CLI: 1.0.x found on PATH
-
-  Authentication:
-
-    ✓ ANTHROPIC_API_KEY: set
-    ✓ gh auth: logged in as <you>
 
-  Filesystem:
+`minions init` creates `~/.minions/`. Primary migrated runtime state lives in
+`engine/state.db` (SQLite, WAL mode). Files such as `engine/dispatch.json` and
+`engine/metrics.json` are passive diagnostic mirrors; `engine/control.json`
+remains a live JSON control file.
 
-    ✓ ~/.minions writable
-    ✓ engine/ writable
+## 2. Link a project
 
-  All checks passed.
+```bash
+minions add C:\code\sample-project
+minions list
 ```
 
-What to look for:
-
-- `✓` (green) means OK. `!` is a warning the engine can usually work around. `✗` (critical) will block dispatch — fix it before continuing.
-- The most common failure is `claude CLI: not found` — re-install with `npm install -g @anthropic-ai/claude-code` and re-run.
-- On Windows, runtime resolution prefers native `claude.exe` over the POSIX bash shim; if you see runtime-resolution warnings, `gh auth status` and `where.exe claude` are good first stops.
-
-If `doctor` reports any `✗`, stop and resolve it. The remaining steps assume a clean preflight.
-
----
+Use the corresponding local path on macOS or Linux. Confirm the detected
+repository host, remote, main branch, and project description. Write the
+description as a responsibility, such as "Billing API and webhook ingestion,"
+because agents use it when routing project-agnostic work.
 
-## Step 3 — Bootstrap state with `minions init`
-
-`minions init` scaffolds `~/.minions/` with a default config, five agent charters, default playbooks, an empty knowledge base, and the engine state files.
+## 3. Start the engine and dashboard
 
 ```bash
-minions init
+minions start --open
 ```
 
-After init you will have (under `~/.minions/`):
+`start` is idempotent and starts both services. If the browser does not open:
 
-- `config.json` — projects, agents, schedules
-- `agents/<name>/charter.md` — the personality + boundaries for each of the five default agents (`ripley`, `dallas`, `lambert`, `rebecca`, `ralph`)
-- `engine/dispatch.json`, `engine/control.json`, `engine/metrics.json` — empty queues, ready for first dispatch
-- `pinned.md`, `notes.md` — empty team-memory surfaces
-- `playbooks/`, `prompts/`, `routing.md` — agent prompt scaffolding
+```bash
+minions dash
+```
 
-`init` is safe to re-run; existing customizations to `config.json`, charters, notes, knowledge, and routing are preserved. To force overwrites after a major version bump, use `minions init --force`.
+The dashboard normally binds to port 7331 and records the actual port if it has
+to scan for a free one.
 
----
+The main pages are **Home**, **Work**, **PRs**, **Plans**, **Inbox**, **Tools**,
+**Schedule**, **Watches**, **Pipelines**, **Meetings**, **QA**, and **Engine**.
+Settings are available from the application controls.
 
-## Step 4 — Link your first project with `minions add`
+## 4. Dispatch one bounded task
 
-A "project" tells Minions which repo to discover work for and where to spawn worktrees. The CLI auto-detects host (GitHub/ADO), org, repo name, and main branch from the directory's git remote.
+Use a small task with an obvious result:
 
 ```bash
-minions add ~/code/your-repo
+minions work "Add a Development section to README.md that names the existing test command"
+minions dispatch
+minions queue
 ```
 
-You will be prompted to confirm or override the auto-detected fields, plus a one-line description. The description is **important** — agents read it during routing to decide whether a work item belongs to your repo. Keep it specific (e.g. "Internal billing API and webhook ingestion service") rather than generic ("Backend code").
+For explicit project selection, create the item from **Work** or Command Center
+and choose your project rather than Auto.
 
-After `minions add` returns, `~/.minions/config.json` has a new `projects[]` entry, and `~/.minions/projects/<name>/` holds the per-project `work-items.json` + `pull-requests.json` trackers.
+Watch the assigned agent from **Home**, then open its **Live Output**. A
+mutating dispatch receives an isolated worktree, the matching playbook, project
+context, and the configured runtime.
 
-To link several at once interactively, run `minions scan` (default: scans `~` to depth 3 for git repos and lets you multi-select).
-
----
-
-## Step 5 — Start engine + dashboard with `minions restart`
-
-`minions restart` starts (or restarts) both the engine daemon and the dashboard server. Use `restart` rather than `start` whenever you have edited engine code or playbooks — it ensures the daemon picks up your changes.
+## 5. Inspect completion
 
 ```bash
-minions restart
+minions status
+minions queue
 ```
 
-You should see logs like `Engine started (pid=…)` and `Dashboard listening on http://localhost:7331`. Open the dashboard:
+Open the item on **Work** to inspect its output, branch, artifacts, and linked
+pull request. If the item remains pending, read `_pendingReason`. If it fails,
+inspect the failure class before retrying:
 
 ```bash
-minions dash    # opens http://localhost:7331 in your default browser
+minions wi show <work-item-id>
+minions wi retry <work-item-id>
 ```
 
-A quick tour of the panels you will use most often during onboarding:
-
-| Panel | What it shows | When to use it |
-|---|---|---|
-| **Projects bar** (top) | All linked projects with descriptions | Confirm Step 4 worked |
-| **Minions Members** | Five agent cards with status, current task, last result | Watch dispatches happen in real time |
-| **Live Output** (per agent) | Streaming `live-output.log` | Tail an agent while it runs — refreshes every 3 s |
-| **Command Center** (CC button, top-right) | Conversational chat with Claude over your full Minions state | Ask questions, queue work, draft plans |
-| **Work Items** | Paginated table of all work, filterable by project/status | Inspect / retry / archive |
-| **Plans & PRD** | Plan markdown drafts and approved PRDs | Approve, discuss-and-revise, or reject plans |
-| **Pull Requests** | Cached PR status (build, review, merge) | Track the PRs your agents create |
-| **Engine** | Dispatch queue, engine log, LLM call performance | Diagnose timing / token issues |
-
-The engine ticks every 10 seconds. If the dashboard says "Engine: stopped", run `minions restart` again — the dashboard auto-restarts a dead engine on its next health check, but a manual restart is faster.
-
----
-
-## Step 6 — Your first dispatch via the Command Center
+Correct authentication, configuration, workspace-manifest, or checkout
+failures before retrying.
 
-The fastest way to give Minions a task is the Command Center (CC).
+## 6. Try a plan
 
-1. Click the **CC** button in the top-right of the dashboard.
-2. In the slide-out chat, type a one-line description, e.g.:
-   ```
-   Add a brief comment to README.md explaining what minions doctor does
-   ```
-3. CC will propose an action (usually `POST /api/work-items` or `POST /api/plan`). Confirm.
+In Command Center:
 
-Within one tick (≤10 s), the engine will:
-
-1. Pick an idle agent that matches the work type (per `routing.md`).
-2. Create a git worktree for that agent under `<your-repo>/.worktrees/<work-item-id>/`.
-3. Render the appropriate playbook (`playbooks/implement.md` for an implement task) with your project context, charter, pinned notes, and recent team notes.
-4. Spawn `engine/spawn-agent.js`, which invokes the Claude CLI with the rendered prompt.
-
-Watch the **Minions Members** card for that agent flip to "working", and click into the **Live Output** tab to tail the streaming agent log.
-
-You can do the same thing from the CLI: `minions work "Add a brief comment to README.md…"`.
-
----
-
-## Step 7 — Your first plan via `/plan`
-
-For multi-step work, use a plan instead of a one-shot work item. In the Command Center, type:
-
-```
-/plan Audit our README and propose three concrete improvements with examples
+```text
+/plan Add a health endpoint, tests, and operator documentation to SampleProject.
+Keep the changes as separately testable items with explicit dependencies.
 ```
 
-CC will queue a `plan` work item. The plan agent writes a markdown draft to `~/.minions/plans/<project>-<date>.md`, then chains automatically to a `plan-to-prd` agent that produces a structured PRD JSON in `~/.minions/prd/`. The PRD lands with `status: "awaiting-approval"`.
-
-Open **Plans & PRD** in the dashboard. You will see the new plan with three buttons:
-
-- **Approve** — materializes one work item per PRD entry, with `depends_on` honored.
-- **Discuss & Revise** — opens a doc-chat modal where you can iterate on the plan with Claude.
-- **Reject** — closes the plan with a reason.
-
-After approving, agents start picking up the materialized work items on the next tick. When all PRD items complete, the engine auto-dispatches a `verify` task that builds + tests the changes and writes a manual testing guide. Archiving (after verify) is a manual dashboard action — see [docs/plan-lifecycle.md](plan-lifecycle.md) for the full pipeline.
-
----
-
-## Step 8 — Your first PR review
-
-When an `implement` agent finishes a work item, it pushes a branch and opens a PR. The engine polls PR status every `prPollStatusEvery` ticks (≈12 minutes by default) and dispatches a `review` agent automatically.
-
-To watch the cycle end-to-end on your first task:
-
-1. Open **Pull Requests** in the dashboard. Find the PR your agent just opened.
-2. Wait for the next status poll (or run `minions dispatch` to wake the daemon immediately). The PR's `reviewStatus` will flip from `pending` to `waiting`, then a review agent will spawn.
-3. Click the agent card to watch the live review. The reviewer reads the diff, runs targeted checks, then posts a comment that starts with `VERDICT: APPROVE` or `VERDICT: REQUEST_CHANGES`.
-4. If the verdict is `REQUEST_CHANGES`, the engine queues a `fix` task for the original author with a feedback note. The cycle repeats until approved or capped by the eval-loop config.
-
-You can also trigger reviews manually by commenting on the PR — see [docs/pr-review-fix-loop.md](pr-review-fix-loop.md).
-
-> **Note on self-approval:** Minions agents share a single GitHub identity, so `gh pr review --approve` is blocked by GitHub's self-approval rule. Reviewers post a `VERDICT:` **comment** instead, and the engine treats that comment as authoritative.
-
----
-
-## Debugging — Where to look when something goes wrong
-
-When an agent gets stuck, hangs, or produces unexpected output, these files are your first stops. They live under `~/.minions/` (or wherever your runtime root is).
-
-| File | What it tells you |
-|---|---|
-| `agents/<id>/live-output.log` | Real-time streaming output from the agent's Claude CLI session — same content the dashboard's Live Output tab shows. Tail this with `tail -f ~/.minions/agents/<id>/live-output.log`. |
-| `agents/<id>/last-prompt.txt` | The most recent rendered prompt the agent received (playbook + system prompt + injected context). Inspect this to see exactly what the agent was asked to do, including pinned notes, team notes, charter, and dispatch context. If your install does not surface this file yet, the live equivalents are `engine/tmp/prompt-<dispatch-id>.md` (while the agent is running) and `engine/contexts/<dispatch-id>.md` (when the prompt was sidecarred because it exceeded `maxDispatchPromptBytes`). |
-| `agents/<id>/output.log` | The agent's final output after completion (post-mortem read; `live-output.log` is the during-run read). |
-| `agents/<id>/history.md` | Last 20 tasks for that agent with timestamps, results, projects, and branches. Useful when a single agent is misbehaving over multiple tasks. |
-| `engine/log.json` | Audit trail of engine actions (last 2500 entries, rotated to 2000). Filter with `jq` for a specific agent or work item. |
-| `engine/dispatch.json` | Pending / active / completed dispatch queue. If an agent appears idle on the dashboard but the queue says `active`, the engine likely lost process tracking — try `minions restart`. |
-| `engine/metrics.json` | Per-agent token usage, runtime, error counts. Useful for spotting agents that are silently retrying. |
-| `notes/inbox/` | Raw findings agents drop after each task. Look here for the latest learnings before the consolidator merges them into `notes.md`. |
-| `pinned.md` and `notes.md` | Team memory that gets injected into every agent prompt. If an agent keeps making the same mistake, pin a correction here. |
-
-Other quick debugging knobs:
-
-- `minions status` — text snapshot of agents, projects, dispatch queue, and quality metrics.
-- `minions queue` — focused view of the dispatch queue (pending, active, completed).
-- `minions kill` — kills all active agents and resets their dispatches to `pending`. Use when an agent is wedged.
-- `minions cleanup` — manually run the temp-file / worktree / zombie sweep that normally runs every 10 ticks.
-
-For deeper dives: [docs/engine-restart.md](engine-restart.md), [docs/auto-discovery.md](auto-discovery.md), and [docs/self-improvement.md](self-improvement.md).
-
----
-
-## What's next
-
-You have:
-
-- Linked a project, started the engine, opened the dashboard.
-- Dispatched a one-shot task via Command Center.
-- Authored a plan, approved it, and watched the PRD materialize into work items.
-- Watched an agent open and review a PR.
-- Located the files you need to debug a stuck agent.
-
-From here, sensible next reads are:
+Review the generated PRD on **Plans**. Use **Discuss & Revise** until its
+acceptance criteria and dependencies are concrete, then approve it. Approval
+materializes work items. When all items complete, Minions creates a verification
+item. Archiving remains a manual action after you review the final result.
 
-- [README.md](../README.md) — the full feature catalog and CLI reference.
-- [CLAUDE.md](../CLAUDE.md) — engineering conventions, tick cycle, locking rules. Read this before editing engine code.
-- [docs/plan-lifecycle.md](plan-lifecycle.md) — plan → PRD → implement → verify → archive in detail.
-- [docs/command-center.md](command-center.md) — full CC capabilities, including doc-chat and plan steering.
-- [docs/pr-review-fix-loop.md](pr-review-fix-loop.md) — how the review/fix cycle is bounded and steered.
+## Where to go next
 
-Welcome to the team.
+- [Tutorial 2: Ship Your First Task](tutorials/02-first-task.md)
+- [Tutorial 3: Build a Feature from a Plan](tutorials/03-plan-driven-feature.md)
+- [Tutorial 8: Operate and Recover Minions](tutorials/08-operations-and-recovery.md)
+- [Plan Lifecycle](plan-lifecycle.md)
+- [Command Center](command-center.md)

package/docs/preflight.md

@@ -1,8 +1,9 @@
 # Preflight & Doctor
 
-`minions doctor` (and the lighter `minions preflight` that runs on every CLI
-invocation) inspects the local environment for the conditions Minions needs
-to dispatch agents reliably. Every row is one of: `OK`, `WARN`, `FAIL`.
+`minions doctor` is the user-facing environment check. A lighter internal
+preflight also runs during `minions init` and engine startup. Together they
+inspect the conditions Minions needs to dispatch agents reliably. Every row is
+one of: `OK`, `WARN`, `FAIL`.
 
 This page documents the rows that are not self-explanatory from their message.
 

package/docs/tutorials/01-install-and-connect.md

@@ -0,0 +1,87 @@
+# Tutorial 1: Install and Connect a Project
+
+You will install Minions, verify the default Copilot runtime, link one Git
+repository, and start the engine and dashboard.
+
+## Prerequisites
+
+- Node.js 22.5 or newer
+- Git
+- GitHub Copilot CLI, Claude Code, or Codex CLI with working authentication
+- A local Git repository with an `origin` remote
+
+Minions defaults to GitHub Copilot CLI. Install it if you have not selected a
+different runtime:
+
+```bash
+npm install -g @github/copilot
+```
+
+## 1. Install and initialize
+
+```bash
+npm install -g @yemi33/minions
+minions init
+```
+
+Initialization creates the operator home at `~/.minions/`, including agent
+charters, playbooks, routing, prompts, and the SQLite state database.
+
+## 2. Verify the host
+
+```bash
+minions doctor
+```
+
+Resolve every `FAIL` before dispatching. Warnings are non-blocking but should be
+read: a permission-flag warning can mean that the selected CLI will stop for an
+interactive prompt during a headless dispatch.
+
+To choose another runtime:
+
+```bash
+minions config set-cli claude
+# or
+minions config set-cli codex
+```
+
+Run `minions doctor` again after switching.
+
+## 3. Link a repository
+
+```bash
+minions add C:\code\sample-project
+```
+
+On macOS or Linux, use the corresponding path such as
+`~/code/sample-project`. Confirm the detected host, repository, main branch,
+and description. The description helps agents route project-agnostic work, so
+describe the repository's responsibility rather than its implementation
+language.
+
+Confirm the result:
+
+```bash
+minions list
+```
+
+## 4. Start Minions
+
+```bash
+minions start --open
+```
+
+`start` is idempotent and starts both the engine and dashboard. If browser
+launch is blocked, run `minions dash`.
+
+## Checkpoint
+
+```bash
+minions status
+```
+
+You should see the engine running, your project listed, and no failed
+dispatches. In the dashboard, verify that the project appears in the project
+picker and that the agent cards are idle.
+
+Next: [ship your first task](02-first-task.md).

package/docs/tutorials/02-first-task.md

@@ -0,0 +1,73 @@
+# Tutorial 2: Ship Your First Task
+
+You will queue a small documentation change, observe routing and live output,
+and inspect the resulting work item and pull request.
+
+## 1. Choose a bounded task
+
+Start with a task that has one clear result and a cheap validation step:
+
+```bash
+minions work "Add a short Development section to README.md that names the existing test command"
+```
+
+For precise project selection, use the dashboard's **Work** page or Command
+Center and select the linked project instead of Auto. A project-scoped task is
+better than auto-routing while learning the lifecycle.
+
+## 2. Wake and inspect the queue
+
+The engine checks for work on its normal tick. You can wake it immediately:
+
+```bash
+minions dispatch
+minions queue
+```
+
+The item normally moves from `pending` to `dispatched`. If it remains pending,
+open its detail view and read `_pendingReason`; common reasons are an unmet
+dependency, no available agent, cooldown, or concurrency limits.
+
+## 3. Follow the agent
+
+In the dashboard:
+
+1. Open **Home** and select the working agent.
+2. Watch **Live Output** for repository exploration, edits, and checks.
+3. Open **Work** and select the item to inspect its branch, output, and
+   artifacts.
+
+The engine chooses an agent from `routing.md`, creates an isolated worktree for
+mutating work, renders the work-type playbook, and invokes the configured
+runtime adapter.
+
+## 4. Inspect the outcome
+
+```bash
+minions status
+minions queue
+```
+
+A successful code-changing task should finish with a branch and pull request.
+If the runtime reports success without the required artifact, the work item can
+still be flagged for lifecycle follow-up.
+
+If the item fails, read its failure class and output before retrying:
+
+```bash
+minions wi show <work-item-id>
+minions wi retry <work-item-id>
+```
+
+Do not retry authentication, invalid configuration, or workspace-permission
+failures without correcting the cause first.
+
+## Checkpoint
+
+You have observed the full path:
+
+```text
+work item -> routing -> worktree -> runtime -> checks -> branch/PR -> completion
+```
+
+Next: [build a feature from a plan](03-plan-driven-feature.md).

package/docs/tutorials/03-plan-driven-feature.md

@@ -0,0 +1,73 @@
+# Tutorial 3: Build a Feature from a Plan
+
+Use a plan when the outcome spans several independently verifiable changes.
+You will create a plan, review its PRD, approve it, and follow dependency-aware
+implementation through verification.
+
+## 1. Draft the request
+
+Open Command Center and enter:
+
+```text
+/plan Add a health endpoint to SampleProject, document it, and add automated
+tests. Keep implementation, tests, and documentation as separate items with
+explicit dependencies.
+```
+
+The plan agent writes Markdown under `plans/`. The plan-to-PRD step then creates
+structured items under `prd/` with acceptance criteria and `depends_on`
+relationships.
+
+You can also provide plan text from the CLI:
+
+```bash
+minions plan "Add a health endpoint, tests, and operator documentation" SampleProject
+```
+
+## 2. Review before approval
+
+Open **Plans** and inspect:
+
+- every item has a concrete deliverable;
+- acceptance criteria can be tested;
+- dependencies use item IDs and are acyclic;
+- each item names the correct project;
+- rejected or out-of-scope ideas are explicit.
+
+Use **Discuss & Revise** for corrections. Approval is the human gate that
+materializes work items, so do not approve a vague PRD and expect routing to
+repair it.
+
+## 3. Approve and observe dependency gating
+
+Approve the plan, then inspect **Work**. Independent items can dispatch in
+parallel. Dependent items stay pending until their prerequisites are done.
+
+At spawn time, Minions resolves completed dependencies to their pull-request
+branches and merges those branches into the dependent item's worktree. This
+lets later items build on code that has not reached the main branch yet.
+
+## 4. Follow verification
+
+When all implementation items finish, Minions creates a `verify` work item.
+Verification builds and tests the combined result and must attach a pull
+request when its contract requires one. A completed plan remains visible until
+you archive it manually.
+
+Archive only after reviewing the verify result:
+
+```bash
+minions plans list
+minions plans archive <plan-or-prd-id>
+```
+
+Archived PRDs remain retained in place; the source plan Markdown moves to
+`plans/archive/`.
+
+## Checkpoint
+
+You should have an approved PRD, materialized work items, dependency-aware
+branches, and a final verification result. See
+[Plan Lifecycle](../plan-lifecycle.md) for status and archive details.
+
+Next: [configure runtimes and project tools](04-runtimes-and-harness.md).

package/docs/tutorials/04-runtimes-and-harness.md

@@ -0,0 +1,77 @@
+# Tutorial 4: Choose Runtimes and Propagate Project Tools
+
+Minions can dispatch with Copilot CLI, Claude Code, or Codex. This tutorial
+switches the fleet runtime, separates Command Center from agent settings, and
+checks which skills, commands, and MCP configurations reach a worktree.
+
+## 1. Inspect the current fleet
+
+```bash
+minions status
+minions doctor --harness
+```
+
+The harness report is read-only. It lists runtime asset directories, skill
+roots, slash-command roots, and MCP configuration paths.
+
+## 2. Select a fleet runtime
+
+```bash
+minions config set-cli copilot --model gpt-5.4
+minions restart
+```
+
+Use a model ID supported by your installed CLI. Omit `--model` to let the CLI
+choose its default. To clear a persisted model while switching:
+
+```bash
+minions restart --cli claude --model ""
+```
+
+Fleet resolution is:
+
+```text
+agent.cli -> engine.defaultCli -> copilot
+agent.model -> engine.defaultModel -> runtime default
+```
+
+Command Center has independent `engine.ccCli` and `engine.ccModel` overrides.
+Changing CC does not silently switch dispatched agents.
+
+## 3. Add a project-local skill
+
+In the linked repository's main checkout, create a committed skill under:
+
+```text
+.claude/skills/<skill-name>/SKILL.md
+```
+
+Describe when the skill applies and provide the exact existing project command
+to run. Commit the skill if every worktree should receive it. Uncommitted
+project-local assets can be propagated from the live checkout when
+`engine.harnessPropagateProjectLocal` is enabled, but committed assets are more
+reproducible.
+
+## 4. Verify propagation
+
+```bash
+minions doctor --harness
+```
+
+Dispatch a small task that clearly matches the skill. The completion report's
+`harnessUsed` section distinguishes assets that were available from those the
+agent reports actually using.
+
+For a known-empty execution environment, enable `hermeticHarness` for an agent
+or the fleet. This removes user asset directories and project harness
+propagation; use it for reproducibility tests, not as an MCP process-launch
+control.
+
+## Checkpoint
+
+The selected runtime passes doctor, your project asset appears in the harness
+survey, and a matching dispatch reports whether it used that asset.
+
+Reference: [Runtime Adapters](../runtime-adapters.md),
+[Harness Propagation](../harness-propagation.md), and
+[Harness Transparency](../harness-transparency.md).