@yemi33/minions 0.1.1882 → 0.1.1884

package/agents/lambert/charter.md

@@ -39,8 +39,7 @@
 
 ## How I Work
 
-- Read Ripley's exploration findings from `{{team_root}}/notes/inbox/ripley-findings-*.md`
-- Read Dallas's build summary from `{{team_root}}/notes/inbox/dallas-build-*.md`
+- Read recent teammate findings under `{{team_root}}/notes/inbox/` — filenames follow the engine-injected "Write Learnings" contract in each agent's dispatch prompt, so defer to that contract rather than matching ad-hoc filename globs here
 - Cross-reference against all `docs/`, agent `CLAUDE.md` files, and prototype instructions
 - Be exhaustive on missing features — better to over-document than under-document
 - Output the JSON to `{{team_root}}/prd/<plan-slug>.json` (the engine's `materializePlansAsWorkItems()` reads from that directory)

package/agents/ripley/charter.md

@@ -22,7 +22,7 @@
 - Always read `CLAUDE.md` files (root + per-agent) before anything else
 - Map the repo structure: `agents/`, `modules/`, `.devtools/`, `docs/`, `eval/`
 - Look for prototype instructions in: `docs/`, `agents/*/CLAUDE.md`, `README.md`, inline comments
-- Document findings in `notes/inbox/ripley-findings-{timestamp}.md` (relative to squad team root)
+- Document findings in the inbox file the dispatch prompt assigns under "Write Learnings" — that section is the single source of truth for the path and filename; do not re-derive it here
 - Never guess — if something is unclear, note it explicitly for human review
 
 ## Boundaries

package/dashboard/js/command-center.js

@@ -179,6 +179,29 @@ async function _ccDashboardHealth() {
   }
 }
 
+// Triggered by the CC "Restart Minions" recovery button when a stale dashboard
+// connection is killing CC streams with "Failed to fetch". Spawns the same
+// `minions restart` flow as the CLI command (kills + respawns engine AND
+// dashboard). The browser auto-reloads via refresh.js when it sees the new
+// dashboardStartedAt; if the POST itself fails (dashboard truly unreachable),
+// fall back to a plain location.reload() so behavior is never worse than before.
+async function ccRestartMinions(btn) {
+  if (btn) { try { btn.disabled = true; btn.textContent = 'Restarting...'; } catch {} }
+  try {
+    var res = await fetch('/api/dashboard/restart', { method: 'POST', headers: { 'Content-Type': 'application/json' } });
+    if (!res.ok) throw new Error('HTTP ' + res.status);
+    if (btn) { try { btn.textContent = 'Restarting Minions — page will reload...'; } catch {} }
+    // The dashboard process is about to be killed. refresh.js's status poll
+    // will detect the new dashboardStartedAt and call location.reload() once
+    // the new dashboard is online; this fallback handles the case where the
+    // poll hasn't fired (e.g., user closed the browser tab and reopened).
+    setTimeout(function() { try { location.reload(); } catch {} }, 8000);
+  } catch (e) {
+    if (btn) { try { btn.textContent = 'Restart failed — reloading...'; } catch {} }
+    setTimeout(function() { try { location.reload(); } catch {} }, 500);
+  }
+}
+
 function _ccIsReconnectableStreamError(err) {
   if (!err) return false;
   var name = String(err.name || '').toLowerCase();
@@ -764,7 +787,7 @@ async function _ccDoSend(message, skipUserMsg, forceTabId, intentMetadata) {
       var retryId = retryRequest && retryRequest.id ? retryRequest.id : '';
       return (extraHtml || '') +
         '<button onclick="ccRetryLast(' + _ccJsArg(retryTabId) + ',' + _ccJsArg(retryId) + ')" style="margin-top:6px;padding:4px 12px;background:var(--surface2);border:1px solid var(--border);border-radius:4px;color:var(--blue);cursor:pointer;font-size:11px">Retry</button>' +
-        (showReload ? ' <button onclick="location.reload()" style="margin-top:6px;padding:4px 12px;background:var(--orange);color:#fff;border:none;border-radius:4px;cursor:pointer;font-size:11px">Reload Page</button>' : '') +
+        (showReload ? ' <button onclick="ccRestartMinions(this)" style="margin-top:6px;padding:4px 12px;background:var(--orange);color:#fff;border:none;border-radius:4px;cursor:pointer;font-size:11px">Restart Minions</button>' : '') +
         ' <button onclick="ccNewTab()" style="margin-top:6px;padding:4px 12px;background:var(--surface2);border:1px solid var(--border);border-radius:4px;color:var(--muted);cursor:pointer;font-size:11px">New Session</button>';
     }
     // Start phase timer immediately so thinking text updates while waiting for SSE
@@ -913,7 +936,7 @@ async function _ccDoSend(message, skipUserMsg, forceTabId, intentMetadata) {
       if (!reconnectHealth.reachable || reconnectHealth.restarted) {
         _cleanupStreamDiv();
         var reconnectHint = reconnectHealth.restarted
-          ? '<div style="font-size:10px;color:var(--muted);margin-top:4px">Dashboard restarted while this response was streaming. Reload the page to reconnect to the new instance.</div>'
+          ? '<div style="font-size:10px;color:var(--muted);margin-top:4px">Dashboard restarted while this response was streaming. Restart Minions to reconnect to the new instance.</div>'
           : '<div style="font-size:10px;color:var(--muted);margin-top:4px">The request stream was interrupted, but the dashboard is still reachable. Retry or start a new session.</div>';
         var reconnectRetry = _ccStoreRetryRequest(activeTab, activeTabId, message);
         addMsg('assistant', (streamedText ? renderMd(streamedText) + _ccElapsedFooter('Stream interrupted after {seconds}s') : '') +
@@ -943,10 +966,10 @@ async function _ccDoSend(message, skipUserMsg, forceTabId, intentMetadata) {
       var connectionHint = '';
       if (isNetworkError) {
         connectionHint = dashboardHealth.restarted
-          ? '<div style="font-size:10px;color:var(--muted);margin-top:4px">Dashboard restarted while this response was streaming. Reload the page to reconnect to the new instance.</div>'
+          ? '<div style="font-size:10px;color:var(--muted);margin-top:4px">Dashboard restarted while this response was streaming. Restart Minions to reconnect to the new instance.</div>'
           : dashboardHealth.reachable
             ? '<div style="font-size:10px;color:var(--muted);margin-top:4px">The request stream was interrupted, but the dashboard is still reachable. Retry or start a new session.</div>'
-            : '<div style="font-size:10px;color:var(--muted);margin-top:4px">Dashboard connection lost. Reload the page to reconnect.</div>';
+            : '<div style="font-size:10px;color:var(--muted);margin-top:4px">Dashboard connection lost. Restart Minions to reconnect.</div>';
       }
       var errorRetry = _ccStoreRetryRequest(activeTab, activeTabId, message);
       addMsg('assistant', (streamedText ? renderMd(streamedText) + _ccElapsedFooter('Stream interrupted after {seconds}s') : '') +

package/dashboard.js

@@ -6428,6 +6428,27 @@ What would you like to discuss or change? When you're happy, say "approve" and I
     } catch (e) { return jsonReply(res, e.statusCode || 500, { error: e.message }); }
   }
 
+  // Spawns `node bin/minions.js restart` detached so it kills + respawns BOTH
+  // engine and dashboard. Used by the CC "Restart Minions" recovery button when
+  // a stale dashboard connection has CC streams failing with "Failed to fetch".
+  // The reply returns immediately — the new dashboard will be online seconds
+  // later and the browser's refresh poll auto-reloads on dashboardStartedAt change.
+  async function handleDashboardRestart(req, res) {
+    try {
+      const { spawn: cpSpawn } = require('child_process');
+      const minionsBin = path.join(MINIONS_DIR, 'bin', 'minions.js');
+      const childEnv = { ...process.env };
+      for (const key of Object.keys(childEnv)) {
+        if (key === 'CLAUDECODE' || key.startsWith('CLAUDE_CODE') || key.startsWith('CLAUDECODE_')) delete childEnv[key];
+      }
+      const proc = cpSpawn(process.execPath, [minionsBin, 'restart'], {
+        cwd: MINIONS_DIR, stdio: 'ignore', detached: true, env: childEnv, windowsHide: true,
+      });
+      proc.unref();
+      return jsonReply(res, 200, { ok: true, pid: proc.pid });
+    } catch (e) { return jsonReply(res, e.statusCode || 500, { error: e.message }); }
+  }
+
   function settingsClaudeConfig(config) {
     const claude = { ...shared.DEFAULT_CLAUDE, ...(config.claude || {}) };
     delete claude.permissionMode;
@@ -7606,6 +7627,7 @@ What would you like to discuss or change? When you're happy, say "approve" and I
       return jsonReply(res, 200, { ok: true, message: 'Wakeup signal sent' });
     }},
     { method: 'POST', path: '/api/engine/restart', desc: 'Force-kill engine and restart immediately', handler: handleEngineRestart },
+    { method: 'POST', path: '/api/dashboard/restart', desc: 'Run `minions restart` to kill+respawn engine AND dashboard (detached)', handler: handleDashboardRestart },
 
     // Runtimes (CLI fleet) — model discovery + capability surface
     { method: 'GET', path: '/api/runtimes', desc: 'List registered CLI runtimes and their capability flags', handler: (req, res) => {

package/docs/command-center.md

@@ -1,159 +1,7 @@
 # Command Center
 
-The Command Center (CC) is the minions's conversational AI brain. It powers the dashboard's chat panel, document editing modals, and plan steering — all through a single persistent Sonnet session with full minions awareness.
+The Command Center (CC) is the dashboard's conversational chat panel. It opens from the **CC** button in the top-right header and lets you drive the engine — dispatching work items, saving notes, approving plans, and asking questions about minions state — through a persistent Claude/Copilot session with full repo awareness.
 
-## Access
+CC is intentionally a thin wrapper around the runtime CLI: state changes happen via `Bash`-tool `curl` calls to the dashboard's own REST API, not via parsed delimiter blocks. The end-to-end flow is `dashboard/js/command-center.js` `_ccDoSend()` → `POST /api/command-center` (or `/api/command-center/stream`) in `dashboard.js` (`handleCommandCenter`) → `engine/llm.js` `callLLM({ direct: true })` → claude/copilot CLI session persisted in `engine/cc-sessions.json`. Per-turn API mutations are correlated via the `X-CC-Turn-Id` header and surfaced as standalone `role='action'` chips rendered outside the assistant bubble (`_ccActionResultLine` + `addMsg('action', ...)`).
 
-Click the **CC** button in the top-right header of the dashboard. A slide-out chat drawer opens on the right side.
-
-## Persistent Sessions
-
-CC maintains a true multi-turn session using Claude CLI's `--resume` flag. Unlike a typical stateless API call, each message resumes the same conversation — Claude retains full history including tool calls, intermediate reasoning, and file contents from prior turns.
-
-**Session lifecycle:**
-- **Created** on first message (or after the system prompt changes, or when you click **New Session**)
-- **Resumed** on subsequent messages via `--resume <sessionId>`
-- **Invalidated** only when the CC system prompt changes — detected by hashing `CC_STATIC_SYSTEM_PROMPT` into `_ccPromptHash` and comparing on each call. CC chat sessions do **not** auto-expire by TTL or turn count; `ENGINE_DEFAULTS.ccMaxTurns` (default 50) is a per-call tool-use cap inside the Claude CLI, not a session lifetime cap.
-- **Persisted** to `engine/cc-session.json` (legacy global session) and `engine/cc-sessions.json` (per-tab sessions) — both survive dashboard restarts and engine cleanup ticks
-- **Frontend messages** saved to `localStorage` — survive page refresh
-- **Removed** only when the user explicitly closes a tab via the **×** button on the tab strip — that fires `DELETE /api/cc-sessions/:id` to evict the persisted session
-
-Click **New Session** in the drawer header to start fresh; click the **×** on a tab to remove it permanently.
-
-### Fresh State Each Turn
-
-The system prompt is baked into the session at creation (persona, rules, action format, tool access). Dynamic minions state is injected as a preamble in each user message, so CC always sees current data even in a resumed session.
-
-```
-Turn 1: system prompt (static) + [Current Minions State] + user message
-Turn 2+: [Updated Minions State] + user message  (system prompt already in session)
-```
-
-## What It Knows
-
-Full minions context is injected every turn:
-
-| Context | Details |
-|---------|---------|
-| Agents | Statuses, current tasks, full charters (expertise/roles) |
-| Routing | Who's preferred/fallback for each work type |
-| Config | Tick interval, max concurrent, timeouts, max turns |
-| Work items | Active, pending, failed across all projects with failure reasons |
-| Pull requests | Status, review status, build status, branch, URL |
-| Plans | Full `.md` plan contents + PRD JSON summaries + archived plans |
-| PRD items | All items with status, priority, dependencies |
-| Dispatch | Active agents + last 15 completions with result summaries |
-| Skills | All reusable agent workflows with triggers |
-| Knowledge base | Recent entries (architecture, conventions, build reports, reviews) |
-| Team notes | Recent consolidated notes |
-
-## Tool Access
-
-CC can use tools to look beyond the pre-loaded context:
-
-- **Bash** — Run shell commands (git, build tools, scripts)
-- **Read** — Open any file (agent output logs, code, config, plans)
-- **Write** — Create or overwrite files
-- **Edit** — Make targeted edits to existing files
-- **Glob** — Find files by pattern (e.g., `agents/*/output.log`)
-- **Grep** — Search file contents (find functions, search agent outputs)
-- **WebFetch/WebSearch** — Look up external resources
-
-## Unified Brain
-
-All LLM-powered features in the dashboard route through the same CC session:
-
-| Feature | Endpoint | How It Works |
-|---------|----------|-------------|
-| **CC chat panel** | `POST /api/command-center` | Direct CC interaction |
-| **Doc chat modal** | `POST /api/doc-chat` | Routes through CC via `ccDocCall()` |
-| **Doc steer** | `POST /api/steer-document` | Routes through CC via `ccDocCall()` |
-| **Plan revision** | `POST /api/plans/revise` | Routes through CC via `ccDocCall()` |
-
-This means:
-- A question in the doc chat modal shares context with the CC panel
-- CC remembers what you discussed in a document editing session
-- Doc modals can cross-reference other minions knowledge, PRs, work items
-- All turns accumulate in the same session
-
-## Actions
-
-When you ask CC to *do* something, it includes structured action blocks in its response.
-
-| Action | What It Does | Example Prompt |
-|--------|-------------|----------------|
-| `dispatch` | Create a work item | "Have dallas fix the login bug" |
-| `note` | Save a decision/reminder | "Remember we need to migrate to v3" |
-| `plan` | Create an implementation plan | "Plan the GitHub integration feature" |
-| `cancel` | Stop a running agent | "Cancel whatever ripley is doing" |
-| `retry` | Retry failed work items | "Retry the three failed tasks" |
-| `pause-plan` | Pause a PRD | "Pause the officeagent PRD" |
-| `approve-plan` | Approve a PRD | "Approve the new plan" |
-| `edit-prd-item` | Edit a PRD item | "Change P003's priority to high" |
-| `remove-prd-item` | Remove a PRD item | "Remove P011 from the plan" |
-| `delete-work-item` | Delete a work item | "Delete work item W025" |
-
-For endpoints without a named action, CC may emit a local API fallback action with `endpoint`, `method`, and `params`. The server only invokes safe local `/api/...` paths, validates the requested method against the route index when available, sends GET params as query strings, and rejects streaming/recursive CC/doc-chat endpoints.
-
-## Error Handling
-
-- **Frontend timeout**: 10-minute `AbortSignal` on the fetch — prevents infinite "thinking" spinner
-- **Backend timeout**: 5-minute kill timer on the claude process
-- **Resume failure**: If `--resume` fails (corrupted/deleted session), automatically retries with a fresh session
-- **Concurrency guard**: Only one CC call at a time — concurrent requests get a 429 "CC is busy" response
-- **Phase indicators**: Thinking indicator shows progressive phases ("Thinking..." → "Analyzing..." → "Timing out soon...")
-
-## Architecture
-
-```
-User message (CC panel, doc modal, or steer)
-    │
-    ▼
-POST /api/command-center  (or /api/doc-chat, /api/steer-document)
-    │
-    ├── Validate session (prompt-hash check — invalidate if `_ccPromptHash` drifted)
-    ├── Build dynamic state preamble (buildCCStatePreamble)
-    ├── callLLM() with sessionId (resume) or without (new)
-    │     model: sonnet
-    │     maxTurns: 25 (CC) or 10 (doc-plan) or 1 (doc-other)
-    │     allowedTools: Bash, Read, Write, Edit, Glob, Grep, WebFetch, WebSearch
-    │     timeout: 600s (CC) or 300s (doc-plan) or 60s (doc-other)
-    │
-    ▼
-engine/llm.js callLLM({ direct: true })  (bypasses engine/spawn-agent.js — CC + doc-chat only)
-    │
-    ├── Resolves claude CLI binary path from engine/claude-caps.json
-    ├── If --resume: pass -p --resume <id> (no system prompt file)
-    ├── If new: pass -p --system-prompt-file <file>
-    │
-    ▼
-claude CLI (persistent session on disk)
-    │
-    ▼
-Parse response
-    ├── Extract sessionId from stream-json result
-    ├── Extract ===ACTIONS=== block (CC)
-    ├── Extract ---DOCUMENT--- block (doc chat/steer)
-    ├── Update cc-session.json
-    │
-    ▼
-Frontend
-    ├── Render chat message
-    ├── Execute actions / apply doc edits
-    ├── Save sessionId + messages to localStorage
-```
-
-## Key Files
-
-| File | Role |
-|------|------|
-| `engine/llm.js` | `callLLM()` / `callLLMStreaming()` — single LLM function with optional `sessionId` for resume; `direct: true` spawns claude CLI directly (used by CC + doc-chat) |
-| `engine/spawn-agent.js` | Agent dispatch wrapper — resolves claude CLI path and invokes it. **Not used by CC/doc-chat** (direct spawn path). |
-| `engine/shared.js` | `parseStreamJsonOutput()` extracts `sessionId` from result |
-| `engine/cc-session.json` | Persisted session state (sessionId, turnCount, timestamps) |
-| `dashboard.js` | CC endpoint, `buildCCStatePreamble()`, `ccDocCall()`, `parseCCActions()` |
-| `dashboard/js/` | Frontend: localStorage persistence, session indicator, New Session button |
-
-## Command Bar
-
-The command bar at the top of the dashboard routes all input to the CC panel. Typing in the command bar opens the CC drawer and sends the message as a CC turn.
+For canonical detail (system prompt, session lifecycle, turn-ID surfacing pipeline, doc-chat integration, and CC API contract), read [`CLAUDE.md`](../CLAUDE.md) — see the **CC API Contract** and **Sessions** sections — and the source in [`dashboard/js/command-center.js`](../dashboard/js/command-center.js), [`dashboard.js`](../dashboard.js) (`handleCommandCenter`), and [`prompts/cc-system.md`](../prompts/cc-system.md). This pointer file exists so the docs index has an entry for "Command Center"; the implementation details are deliberately not duplicated here because they drift.

package/docs/index.html

@@ -3,8 +3,8 @@
 <head>
 <meta charset="UTF-8">
 <meta name="viewport" content="width=device-width, initial-scale=1.0">
-<title>Minions — Multi-Agent AI Dev Team</title>
-<meta name="description" content="5 autonomous AI agents, one engine, one dashboard. Minions orchestrates Claude-powered agents to plan, implement, review, and ship code autonomously.">
+<title>Minions &mdash; Multi-Agent AI Dev Team</title>
+<meta name="description" content="Five autonomous coding agents, one engine, and one dashboard. Minions orchestrates Claude or GitHub Copilot agents to plan, implement, review, verify, and ship code.">
 <style>
   :root { --bg: #0d1117; --surface: #161b22; --border: #30363d; --text: #c9d1d9; --muted: #8b949e; --blue: #58a6ff; --green: #3fb950; --yellow: #d29922; --red: #f85149; --purple: #bc8cff; }
   * { margin: 0; padding: 0; box-sizing: border-box; }
@@ -83,15 +83,15 @@
 <!-- Hero -->
 <div class="hero">
   <h1>Minions <span>Mission Control</span></h1>
-  <p class="tagline">5 autonomous AI agents, one engine, one dashboard. Plan, implement, review, and ship code &mdash; hands-free.</p>
+  <p class="tagline">Five autonomous coding agents, one engine, one dashboard. Plan, implement, review, verify, and ship code with human control at every gate.</p>
   <div class="hero-badges">
-    <span class="hero-badge green">Zero Dependencies</span>
-    <span class="hero-badge blue">Claude-Powered</span>
+    <span class="hero-badge green">Node.js 18+</span>
+    <span class="hero-badge blue">Claude or Copilot</span>
     <span class="hero-badge yellow">Multi-Project</span>
-    <span class="hero-badge purple">Self-Improving</span>
+    <span class="hero-badge purple">Dashboard + CLI</span>
   </div>
   <div class="cta">
-    <a href="https://github.com/yemi33/minions" class="cta-primary">View on GitHub</a>
+    <a href="https://www.npmjs.com/package/@yemi33/minions" class="cta-primary">Install from npm</a>
     <a href="#quickstart" class="cta-secondary">Quick Start</a>
   </div>
 </div>
@@ -108,24 +108,25 @@
 <!-- Features -->
 <div class="container">
 <div class="features">
-  <div class="feature"><h3>Autonomous Dispatch</h3><p>Engine discovers work from plans, PRs, pipelines, and queues &mdash; routes to the right agent based on skills and availability.</p></div>
-  <div class="feature"><h3>Plan Lifecycle</h3><p>Plan &rarr; Approve &rarr; PRD &rarr; Execute &rarr; Review &rarr; Verify. Human-in-the-loop at every gate.</p></div>
+  <div class="feature"><h3>Autonomous Dispatch</h3><p>Engine discovers work from plans, PRs, schedules, pipelines, and queues &mdash; then routes to the right agent by role, skill, and availability.</p></div>
+  <div class="feature"><h3>Plan Lifecycle</h3><p>Plan &rarr; Approve &rarr; PRD &rarr; Execute &rarr; Review &rarr; Verify. Completed plans stay available until you manually archive them.</p></div>
   <div class="feature"><h3>Team Meetings</h3><p>Multi-agent meetings with investigate, debate, and conclude rounds. Agents research, discuss, and produce actionable conclusions.</p></div>
   <div class="feature"><h3>Multi-Stage Pipelines</h3><p>Chain tasks, meetings, plans, and more into automated workflows. Cron triggers or manual. Artifacts flow between stages.</p></div>
-  <div class="feature"><h3>Eval Loop</h3><p>After implementation, auto-dispatches review &rarr; fix cycles. Configurable iterations and cost ceiling per work item.</p></div>
+  <div class="feature"><h3>Review / Fix Loop</h3><p>After implementation, Minions can dispatch reviews, react to human PR comments, and send fixes back to the original author agent.</p></div>
   <div class="feature"><h3>Git Worktree Isolation</h3><p>Each agent works in its own worktree. No conflicts, no cross-contamination, safe parallel execution.</p></div>
-  <div class="feature"><h3>Knowledge Consolidation</h3><p>Agent findings auto-consolidate into team notes and a searchable knowledge base. The team learns as it works.</p></div>
-  <div class="feature"><h3>PR Integration</h3><p>Auto-syncs PRs from Azure DevOps and GitHub. Detects review feedback, build failures, and human comments.</p></div>
-  <div class="feature"><h3>Scheduled Tasks</h3><p>Cron-style recurring work: nightly tests, weekly audits, daily standups. Visual cron builder in the dashboard.</p></div>
-  <div class="feature"><h3>Command Center</h3><p>Natural language interface for delegating work to agents. CC orchestrates &mdash; agents implement.</p></div>
-  <div class="feature"><h3>Live Dashboard</h3><p>Real-time mission control on port 7331. Paginated views, optimistic updates, and visibility-aware polling.</p></div>
-  <div class="feature"><h3>One-Command Updates</h3><p><code>minions update</code> pulls latest from npm and applies. Config and charters preserved automatically.</p></div>
+  <div class="feature"><h3>Knowledge Consolidation</h3><p>Agent findings, quick notes, pinned notes, and feedback consolidate into team notes and a categorized knowledge base.</p></div>
+  <div class="feature"><h3>PR Integration</h3><p>Tracks Azure DevOps and GitHub PRs, including review votes, build status, merge status, human comments, and context-only links.</p></div>
+  <div class="feature"><h3>Scheduled Tasks &amp; Watches</h3><p>Cron-style recurring work plus watches for PRs, work items, dispatches, meetings, pipelines, agents, and status changes.</p></div>
+  <div class="feature"><h3>Command Center &amp; Doc Chat</h3><p>Natural language orchestration, persistent CC tabs, document Q&amp;A/editing, issue filing, routing updates, and local API actions.</p></div>
+  <div class="feature"><h3>Pluggable Runtimes</h3><p>Run agents through Claude Code or GitHub Copilot CLI, with runtime-specific models, effort, session resume, and permission handling.</p></div>
+  <div class="feature"><h3>Live Dashboard</h3><p>Real-time mission control on port 7331 with paginated views, optimistic updates, live streams, metrics, and settings.</p></div>
+  <div class="feature"><h3>One-Command Updates</h3><p><code>minions update</code> pulls the latest npm package, reapplies files, and restarts while preserving config and customizations.</p></div>
 </div>
 
 <!-- Demo scenarios -->
 <div class="scenario">
   <div class="scenario-header"><div class="scenario-num">1</div><h2>Dashboard Overview</h2></div>
-  <p>Home page with agent status cards, project bar, and setup guidance. All agents visible at a glance.</p>
+  <p>Home page with agent status cards, project bar, setup guidance, and engine state. All agents visible at a glance.</p>
   <div class="demo-frame">
     <img src="demo/01-dashboard-overview.png" alt="Dashboard overview with agent cards">
     <div class="demo-caption">Home page showing Minions Members, project bar, and engine status badge</div>
@@ -134,7 +135,7 @@
 
 <div class="scenario">
   <div class="scenario-header"><div class="scenario-num">2</div><h2>Work Items</h2></div>
-  <p>Paginated table with status, type, priority, agent, and linked PRs. <span class="badge badge-yellow">PENDING</span> <span class="badge badge-blue">DISPATCHED</span> <span class="badge badge-green">DONE</span> <span class="badge badge-red">FAILED</span>. Retry, delete, and archive with optimistic updates.</p>
+  <p>Paginated table with status, type, priority, agent, dependencies, artifacts, and linked PRs. <span class="badge badge-yellow">PENDING</span> <span class="badge badge-blue">DISPATCHED</span> <span class="badge badge-green">DONE</span> <span class="badge badge-red">FAILED</span>. Retry, delete, archive, and add feedback with optimistic updates.</p>
   <div class="demo-frame">
     <img src="demo/02-work-items.png" alt="Work items table">
     <div class="demo-caption">Work items page &mdash; 20 per page with create, edit, retry, and delete actions</div>
@@ -143,7 +144,7 @@
 
 <div class="scenario">
   <div class="scenario-header"><div class="scenario-num">3</div><h2>Plans &amp; PRD</h2></div>
-  <p>Plan cards with Approve / Discuss &amp; Revise / Reject. PRD dependency graph with per-item retry. Archive completed plans.</p>
+  <p>Plan cards with Approve / Discuss &amp; Revise / Reject. PRD dependency graph with per-item retry, reopening, verification, and manual archive.</p>
   <div class="demo-frame">
     <img src="demo/03-plans-prd.png" alt="Plans and PRD progress">
     <div class="demo-caption">Plans page with status-colored cards, PRD dependency graph, and action buttons</div>
@@ -152,7 +153,7 @@
 
 <div class="scenario">
   <div class="scenario-header"><div class="scenario-num">4</div><h2>Pull Requests</h2></div>
-  <p>PR tracker sorted by date, with review, build, and merge status. Linked to work items and PRD items. Manual PR linking supported.</p>
+  <p>PR tracker sorted by date, with review, build, merge, conflict, and human-comment status. Linked to work items and PRD items. Manual PR linking and context-only observation supported.</p>
   <div class="demo-frame">
     <img src="demo/04-pull-requests.png" alt="Pull requests tracker">
     <div class="demo-caption">PRs sorted newest-first with build status, review status, and agent attribution</div>
@@ -170,7 +171,7 @@
 
 <div class="scenario">
   <div class="scenario-header"><div class="scenario-num">6</div><h2>Pipelines</h2></div>
-  <p>Multi-stage workflows chaining tasks, meetings, plans, and more. Cron triggers or manual. Artifact tracking between stages.</p>
+  <p>Multi-stage workflows chaining tasks, meetings, plans, tests, docs, and more. Cron triggers or manual runs. Artifact tracking between stages.</p>
   <div class="demo-frame">
     <img src="demo/06-pipelines.png" alt="Pipelines page">
     <div class="demo-caption">Pipeline cards with stage flow visualization, run history, and progress bars</div>
@@ -179,7 +180,7 @@
 
 <div class="scenario">
   <div class="scenario-header"><div class="scenario-num">7</div><h2>Notes &amp; Knowledge Base</h2></div>
-  <p>Inbox for agent findings, consolidated team notes, and categorized knowledge base. Inline Q&amp;A on any document.</p>
+  <p>Inbox for agent findings, quick notes, pinned notes, consolidated team notes, and categorized knowledge base. Inline Q&amp;A/editing on documents.</p>
   <div class="demo-frame">
     <img src="demo/07-notes-kb.png" alt="Notes and knowledge base">
     <div class="demo-caption">Notes inbox, team notes, and knowledge base with category tabs and pagination</div>
@@ -188,7 +189,7 @@
 
 <div class="scenario">
   <div class="scenario-header"><div class="scenario-num">8</div><h2>Scheduled Tasks</h2></div>
-  <p>Cron-style recurring work with visual builder. Natural language parsing &mdash; type "every weekday at 9am" and it generates the cron.</p>
+  <p>Cron-style recurring work with a visual builder. Schedule work items, tests, docs, plans, asks, meetings, and recurring maintenance.</p>
   <div class="demo-frame">
     <img src="demo/08-schedules.png" alt="Schedules page">
     <div class="demo-caption">Schedule list with cron expressions, last-run times, and enable/disable toggles</div>
@@ -197,7 +198,7 @@
 
 <div class="scenario">
   <div class="scenario-header"><div class="scenario-num">9</div><h2>Engine &amp; Metrics</h2></div>
-  <p>Dispatch queue, engine log, agent metrics, token usage, and context pressure. All paginated.</p>
+  <p>Dispatch queue, engine log, agent metrics, token usage, runtime/model data, quality signals, and context pressure. All paginated.</p>
   <div class="demo-frame">
     <img src="demo/09-engine.png" alt="Engine page">
     <div class="demo-caption">Active/pending dispatches, completed history, engine log, and per-agent quality metrics</div>
@@ -206,7 +207,7 @@
 
 <div class="scenario">
   <div class="scenario-header"><div class="scenario-num">10</div><h2>Command Center</h2></div>
-  <p>Natural language delegation. CC orchestrates &mdash; agents implement. Session persists across refreshes. Actions auto-execute.</p>
+  <p>Natural language delegation. CC orchestrates &mdash; agents implement. Sessions persist across refreshes and tabs; actions can create work, notes, plans, watches, PR links, and issues.</p>
   <div class="demo-frame">
     <img src="demo/10-command-center.png" alt="Command Center panel">
     <div class="demo-caption">Command Center side panel with conversation history, action execution, and session indicator</div>
@@ -216,17 +217,27 @@
 <!-- Quick Start -->
 <div class="quickstart" id="quickstart">
   <h2>Quick Start</h2>
-  <pre><span class="comment"># Install</span>
+  <pre><span class="comment"># Prerequisites: Node.js 18+, Git, and at least one agent runtime</span>
+<span class="comment"># Install Claude Code or GitHub Copilot CLI separately, then install Minions</span>
 npm install -g @yemi33/minions
 
-<span class="comment"># Initialize &mdash; prompts for project locations, starts engine + dashboard</span>
+<span class="comment"># Bootstrap ~/.minions/ and scan/link repositories</span>
 minions init
 
+<span class="comment"># Or add a specific project later</span>
+minions add ~/my-project
+
+<span class="comment"># Start engine + dashboard, then open http://localhost:7331</span>
+minions restart --open
+minions dash
+
 <span class="comment"># Give your first task</span>
 minions work "Explore the codebase and document the architecture"
 
-<span class="comment"># Open dashboard at http://localhost:7331</span>
-minions dash
+<span class="comment"># Useful operations</span>
+minions status
+minions doctor
+minions config set-cli copilot --model gpt-5.4
 
 <span class="comment"># Update to latest</span>
 minions update</pre>
@@ -241,7 +252,7 @@ minions update</pre>
   │                                                     │
   │   engine.js ──── 60s tick loop ────┐                │
   │       │                            │                │
-  │   discover work    spawn agents    poll PRs          │
+  │   discover work    spawn agents    poll PRs/comments │
   │       │                │              │             │
   │   ┌───┴───┐    ┌──────┴──────┐   ┌──┴───┐         │
   │   │ Plans │    │  Worktrees  │   │ ADO  │         │
@@ -250,10 +261,11 @@ minions update</pre>
   │   └───────┘    └─────────────┘   └──────┘         │
   │                                                     │
   │   dashboard.js ── port 7331 ── mission control      │
+  │   runtimes/ ── Claude Code or GitHub Copilot CLI    │
   │   meetings/ ── multi-agent discussions              │
   │   pipelines/ ── multi-stage workflows               │
-  │   notes.md ── consolidated team knowledge           │
-  │   knowledge/ ── searchable KB by category           │
+  │   schedules + watches ── recurring/conditional work │
+  │   notes.md + knowledge/ ── team memory and KB       │
   └─────────────────────────────────────────────────────┘
   </pre>
 </div>
@@ -261,7 +273,7 @@ minions update</pre>
 </div>
 
 <footer>
-  <p>Minions &mdash; <a href="https://github.com/yemi33/minions">GitHub</a> &mdash; <a href="https://www.npmjs.com/package/@yemi33/minions">npm</a> &mdash; MIT License &mdash; Zero dependencies, powered by Claude</p>
+  <p>Minions &mdash; <a href="https://www.npmjs.com/package/@yemi33/minions">npm</a> &mdash; <a href="https://yemi33.github.io/minions/">Public site</a> &mdash; MIT License &mdash; Claude Code or GitHub Copilot CLI runtime</p>
 </footer>
 
 </body>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.1882",
+  "version": "0.1.1884",
   "description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
   "bin": {
     "minions": "bin/minions.js"