monomind 2.2.0 → 2.3.1

package/packages/@monomind/cli/.claude/skills/mastermind-skills/taskdev.md

@@ -13,6 +13,8 @@ Execute a plan by dispatching a fresh subagent per task, with two-stage review a
 
 **Core principle:** Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
 
+**Narration:** between tool calls, narrate at most one short line — the progress ledger and the tool results carry the record.
+
 **Continuous execution:** Do not pause to check in with your human partner between tasks. Execute all tasks from the plan without stopping. The only reasons to stop are: BLOCKED status you cannot resolve, ambiguity that genuinely prevents progress, or all tasks complete. "Should I continue?" prompts and progress summaries waste their time — they asked you to execute the plan, so execute it.
 
 ---
@@ -75,12 +77,12 @@ digraph process {
         "Mark task complete in TodoWrite" [shape=box];
     }
 
-    "Read plan, extract all tasks with full text, note context, create TodoWrite" [shape=box];
+    "Read plan, note context and global constraints, create TodoWrite" [shape=box];
     "More tasks remain?" [shape=diamond];
     "Dispatch final code reviewer subagent for entire implementation" [shape=box];
     "Use mastermind:finish" [shape=box style=filled fillcolor=lightgreen];
 
-    "Read plan, extract all tasks with full text, note context, create TodoWrite" -> "Dispatch implementer subagent (./implementer-prompt.md)";
+    "Read plan, note context and global constraints, create TodoWrite" -> "Dispatch implementer subagent (./implementer-prompt.md)";
     "Dispatch implementer subagent (./implementer-prompt.md)" -> "Implementer subagent asks questions?";
     "Implementer subagent asks questions?" -> "Answer questions, provide context" [label="yes"];
     "Answer questions, provide context" -> "Dispatch implementer subagent (./implementer-prompt.md)";
@@ -103,6 +105,17 @@ digraph process {
 
 ---
 
+## Pre-Flight Plan Review
+
+Before dispatching Task 1, scan the plan once for conflicts:
+
+- tasks that contradict each other or the plan's Global Constraints
+- anything the plan explicitly mandates that the review rubric treats as a defect (a test that asserts nothing, verbatim duplication of a logic block)
+
+Present everything you find to your human partner as one batched question — each finding beside the plan text that mandates it, asking which governs — before execution begins, not one interrupt per discovery mid-plan. If the scan is clean, proceed without comment. The review loop remains the net for conflicts that only emerge from implementation. (In auto mode: resolve each conflict yourself, state the resolution explicitly, and log it as a decision with confidence.)
+
+---
+
 ## Model Selection
 
 Use the least powerful model that can handle each role to conserve cost and increase speed.
@@ -111,7 +124,13 @@ Use the least powerful model that can handle each role to conserve cost and incr
 
 **Integration and judgment tasks** (multi-file coordination, pattern matching, debugging): use a standard model.
 
-**Architecture, design, and review tasks**: use the most capable available model.
+**Architecture and design tasks**: use the most capable available model. The final whole-branch review is one of these — dispatch it on the most capable available model, not the session default.
+
+**Review tasks**: choose the model with the same judgment, scaled to the diff's size, complexity, and risk. A small mechanical diff does not need the most capable model; a subtle concurrency change does.
+
+**Always specify the model explicitly when dispatching a subagent.** An omitted model inherits your session's model — often the most capable and most expensive — which silently defeats this section.
+
+**Turn count beats token price.** Wall-clock and context cost scale with how many turns a subagent takes, and the cheapest models routinely take 2-3× the turns on multi-step work — costing more overall. Use a mid-tier model as the floor for reviewers and for implementers working from prose descriptions. When the task's plan text contains the complete code to write, the implementation is transcription plus testing: use the cheapest tier for that implementer. Single-file mechanical fixes also take the cheapest tier.
 
 **Task complexity signals:**
 - Touches 1-2 files with a complete spec → cheap model
@@ -124,7 +143,7 @@ Use the least powerful model that can handle each role to conserve cost and incr
 
 Implementer subagents report one of four statuses. Handle each appropriately:
 
-**DONE:** Proceed to spec compliance review.
+**DONE:** Generate the task's diff file from the BASE you recorded before dispatching the implementer (never `HEAD~1` — it silently drops all but the last commit of a multi-commit task), then proceed to spec compliance review with the brief, report, and diff file paths.
 
 **DONE_WITH_CONCERNS:** The implementer completed the work but flagged doubts. Read the concerns before proceeding. If the concerns are about correctness or scope, address them before review. If they're observations (e.g., "this file is getting large"), note them and proceed to review.
 
@@ -138,6 +157,54 @@ Implementer subagents report one of four statuses. Handle each appropriately:
 
 **Never** ignore an escalation or force the same model to retry without changes. If the implementer said it's stuck, something needs to change.
 
+**Async dispatches:** reviewer and implementer subagents may complete asynchronously even when dispatched synchronously. Wait for each result before acting on it — never proceed to the next gate, and never touch the files a dispatched subagent is working on, while its result is pending.
+
+---
+
+## Handling Reviewer ⚠️ Items
+
+A reviewer may report "⚠️ Cannot verify from diff" items — requirements that live in unchanged code or span tasks. These do not block the rest of the review, but you must resolve each one yourself before marking the task complete: you hold the plan and cross-task context the reviewer lacks. If you confirm an item is a real gap, treat it as a failed spec review — send it back to the implementer and re-review.
+
+---
+
+## Constructing Reviewer Prompts
+
+Per-task reviews are task-scoped gates. The broad review happens once, at the final whole-branch review. When you fill a reviewer template:
+
+- Do not add open-ended directives like "check all uses" or "run race tests if useful" without a concrete, task-specific reason
+- Do not ask a reviewer to re-run tests the implementer already ran on the same code — the implementer's report carries the test evidence
+- Do not pre-judge findings for the reviewer — never instruct a reviewer to ignore or not flag a specific issue. If you believe a finding would be a false positive, let the reviewer raise it and adjudicate it in the review loop. If the prompt you are writing contains "do not flag," "don't treat X as a defect," "at most Minor," or "the plan chose" — stop: you are pre-judging, usually to spare yourself a review loop.
+- The global-constraints block you hand the reviewer is its attention lens. Copy the binding requirements verbatim from the plan's Global Constraints section or the spec: exact values, exact formats, and the stated relationships between components ("same layout as X", "matches Y"). The reviewer's template already carries the process rules — the constraints block is for what THIS project's spec demands.
+- Hand the reviewer its diff as a file: run `git log --oneline BASE..HEAD`, `git diff --stat BASE..HEAD`, and `git diff -U10 BASE..HEAD`, redirected to one uniquely named file (e.g. `.monomind/taskdev/task-N-review.diff`), and pass the reviewer that path. The output never enters your own context, and the reviewer sees the commit list, stat summary, and full diff with context in one Read call. Use the BASE you recorded before dispatching the implementer — never `HEAD~1`, which silently truncates multi-commit tasks.
+- A dispatch prompt describes one task, not the session's history. Do not paste accumulated prior-task summaries ("state after Tasks 1-3") into later dispatches. A fresh subagent needs its task, the interfaces it touches, and the global constraints. Nothing else.
+- Dispatch fix subagents for Critical and Important findings. Record Minor findings in the progress ledger as you go, and point the final whole-branch review at that list so it can triage which must be fixed before merge. A roll-up nobody reads is a silent discard.
+- A finding labeled plan-mandated — or any finding that conflicts with what the plan's text requires — is the human's decision, like any plan contradiction: present the finding and the plan text, ask which governs. Do not dismiss the finding because the plan mandates it, and do not dispatch a fix that contradicts the plan without asking. (In auto mode: resolve it explicitly, log the decision, and prefer the spec over the plan's example code.)
+- The final whole-branch review gets a diff file too: generate it from the merge base (`git merge-base main HEAD`) to HEAD and include the path in the final review dispatch, so the final reviewer reads one file instead of re-deriving the branch diff with git commands.
+- Every fix dispatch carries the implementer contract: the fix subagent re-runs the tests covering its change and reports the results. Name the covering test files in the dispatch — a one-line fix does not need the whole suite. Before re-dispatching the reviewer, confirm the fix report contains the covering tests, the command run, and the output.
+- If the final whole-branch review returns findings, dispatch ONE fix subagent with the complete findings list — not one fixer per finding. Per-finding fixers each rebuild context and re-run suites; a real session's final-review fix wave cost more than all its tasks combined.
+
+---
+
+## File Handoffs
+
+Everything you paste into a dispatch prompt — and everything a subagent prints back — stays resident in your context for the rest of the session and is re-read on every later turn. Hand artifacts over as files:
+
+- **Task brief:** before dispatching an implementer, extract the task's full text from the plan into a uniquely named file (e.g. `.monomind/taskdev/task-N-brief.md`). Compose the dispatch so the brief stays the single source of requirements. Your dispatch should contain: (1) one line on where this task fits in the project; (2) the brief path, introduced as "read this first — it is your requirements, with the exact values to use verbatim"; (3) interfaces and decisions from earlier tasks that the brief cannot know; (4) your resolution of any ambiguity you noticed in the brief; (5) the report-file path and report contract. Exact values (numbers, magic strings, signatures, test cases) appear only in the brief.
+- **Report file:** name the implementer's report file after the brief (brief `…/task-N-brief.md` → report `…/task-N-report.md`) and put it in the dispatch prompt. The implementer writes the full report there and returns only status, commits, a one-line test summary, and concerns.
+- **Reviewer inputs:** each reviewer gets three paths — the same brief file, the report file, and the diff file — plus the global constraints that bind the task.
+- Fix dispatches append their fix report (with test results) to the same report file and return a short summary; re-reviews read the updated file.
+
+---
+
+## Durable Progress
+
+Conversation memory does not survive compaction. Controllers that lost their place have re-dispatched entire completed task sequences — the single most expensive failure observed. Track progress in a ledger file, not only in todos.
+
+- At skill start, check for a ledger: `cat "$(git rev-parse --show-toplevel)/.monomind/taskdev/progress.md"`. Tasks listed there as complete are DONE — do not re-dispatch them; resume at the first task not marked complete.
+- When a task's reviews come back clean, append one line to the ledger in the same message as your other bookkeeping: `Task N: complete (commits <base7>..<head7>, spec ✅ quality ✅)`.
+- The ledger is your recovery map: the commits it names exist in git even when your context no longer remembers creating them. After compaction, trust the ledger and `git log` over your own recollection.
+- The ledger is git-ignored scratch; if it's destroyed, recover from `git log`.
+
 ---
 
 ## Prompt Templates
@@ -145,6 +212,7 @@ Implementer subagents report one of four statuses. Handle each appropriately:
 - `./implementer-prompt.md` - Dispatch implementer subagent
 - `./spec-reviewer-prompt.md` - Dispatch spec compliance reviewer subagent
 - `./code-quality-reviewer-prompt.md` - Dispatch code quality reviewer subagent
+- `./final-reviewer-prompt.md` - Dispatch the final whole-branch reviewer (most capable model, diff as a file)
 
 ---
 
@@ -154,13 +222,13 @@ Implementer subagents report one of four statuses. Handle each appropriately:
 You: I'm using mastermind:taskdev to execute this plan.
 
 [Read plan file once: docs/mastermind/plans/feature-plan.md]
-[Extract all 5 tasks with full text and context]
+[Check ledger .monomind/taskdev/progress.md — empty, starting fresh]
 [Create TodoWrite with all tasks]
 
 Task 1: Hook installation script
 
-[Get Task 1 text and context (already extracted)]
-[Dispatch implementation subagent with full task text + context]
+[Extract Task 1 brief to .monomind/taskdev/task-1-brief.md; record BASE]
+[Dispatch implementer with brief + report paths + scene-setting context]
 
 Implementer: "Before I begin - should the hook be installed at user or system level?"
 
@@ -173,18 +241,18 @@ Implementer: "Got it. Implementing now..."
   - Self-review: Found I missed --force flag, added it
   - Committed
 
-[Dispatch spec compliance reviewer]
+[Generate diff file from recorded BASE, dispatch spec compliance reviewer]
 Spec reviewer: ✅ Spec compliant - all requirements met, nothing extra
 
-[Get git SHAs, dispatch code quality reviewer]
+[Dispatch code quality reviewer with the same diff file]
 Code reviewer: Strengths: Good test coverage, clean. Issues: None. Approved.
 
 [Mark Task 1 complete]
 
 Task 2: Recovery modes
 
-[Get Task 2 text and context (already extracted)]
-[Dispatch implementation subagent with full task text + context]
+[Extract Task 2 brief to .monomind/taskdev/task-2-brief.md; record BASE]
+[Dispatch implementer with brief + report paths + Task 1 interfaces]
 
 Implementer: [No questions, proceeds]
 Implementer:
@@ -240,8 +308,7 @@ Done!
 - Review checkpoints automatic
 
 **Efficiency gains:**
-- No file reading overhead (controller provides full text)
-- Controller curates exactly what context is needed
+- Controller curates exactly what context is needed; bulk artifacts move as files (briefs, reports, diffs), not pasted text
 - Subagent gets complete information upfront
 - Questions surfaced before work begins (not after)
 
@@ -267,14 +334,17 @@ Done!
 - Skip reviews (spec compliance OR code quality)
 - Proceed with unfixed issues
 - Dispatch multiple implementation subagents in parallel (conflicts)
-- Make subagent read plan file (provide full text instead)
+- Make a subagent read the whole plan file (hand it its task-brief file instead)
 - Skip scene-setting context (subagent needs to understand where task fits)
 - Ignore subagent questions (answer before letting them proceed)
 - Accept "close enough" on spec compliance (spec reviewer found issues = not done)
 - Skip review loops (reviewer found issues = implementer fixes = review again)
 - Let implementer self-review replace actual review (both are needed)
 - **Start code quality review before spec compliance is ✅** (wrong order)
-- Move to next task while either review has open issues
+- Move to next task while either review has open Critical/Important issues
+- Tell a reviewer what not to flag, or pre-rate a finding's severity in the dispatch prompt ("treat it as Minor at most") — the plan's example code is a starting point, not evidence that its weaknesses were chosen
+- Dispatch a reviewer without a diff file — generate it first from the recorded BASE and name the path in the prompt
+- Re-dispatch a task the progress ledger already marks complete — check the ledger (and `git log`) after any compaction or resume
 
 **If subagent asks questions:**
 - Answer clearly and completely

package/packages/@monomind/cli/.claude/skills/mastermind-skills/tdd.md

@@ -376,6 +376,36 @@ Can't check all boxes? You skipped TDD. Start over.
 
 ---
 
+## Testing Anti-Patterns
+
+Tests must verify real behavior, not mock behavior. Mocks are a means to isolate, not the thing being tested. **Test what the code does, not what the mocks do.**
+
+**The Iron Laws of mocking:**
+
+```
+1. NEVER test mock behavior
+2. NEVER add test-only methods to production classes
+3. NEVER mock without understanding dependencies
+```
+
+| Anti-pattern | The violation | The fix |
+|---|---|---|
+| **Testing mock behavior** | Asserting a `*-mock` element or mocked return exists — the test verifies the mock works, not the component | Test the real component, or don't assert on the mock at all |
+| **Test-only methods in production** | A method (e.g. `destroy()`) that only tests call, living on a production class | Move it to test utilities; production classes carry only production API |
+| **Mocking without understanding** | Mocking a method whose side effect the test depends on ("I'll mock this to be safe") — the test passes for the wrong reason or fails mysteriously | Run the test against the real implementation FIRST, observe what it needs, then mock minimally at the lowest slow/external level |
+| **Incomplete mocks** | Mocking only the fields your immediate test uses — downstream code reads omitted fields and fails silently in integration | Mirror the COMPLETE real data structure; if uncertain, include all documented fields |
+| **Tests as afterthought** | "Implementation complete, ready for testing" | Testing is part of implementation — TDD, tests first |
+
+**Gate before any mock:** What side effects does the real method have? Does this test depend on any of them? Do I fully understand what this test needs? If unsure — run against the real implementation first.
+
+**When mocks become too complex** (setup longer than test logic, mock missing methods real components have, test breaks when mock changes): ask "do we need a mock here at all?" — integration tests with real components are often simpler than complex mocks.
+
+**Red flags:** assertions on `*-mock` IDs · methods only called from test files · mock setup >50% of the test · test fails when you remove the mock · can't explain why the mock is needed · mocking "just to be safe".
+
+If TDD reveals you're testing mock behavior, you added mocks without watching the test fail against real code first — test real behavior or question why you're mocking at all.
+
+---
+
 ## Debugging Integration
 
 Bug found? Write failing test reproducing it. Follow TDD cycle. Test proves fix and prevents regression.

package/packages/@monomind/cli/dist/src/autopilot-state.js

@@ -109,8 +109,9 @@ export function loadState() {
             return merged;
         }
     }
-    catch {
-        // Corrupted state file — return defaults
+    catch (e) {
+        if (process.env.DEBUG || process.env.MONOMIND_DEBUG)
+            console.error('[autopilot-state] failed to load state file, using defaults:', e);
     }
     return defaults;
 }
@@ -214,8 +215,9 @@ export function loadLog() {
             return out;
         }
     }
-    catch {
-        // Corrupted log — return empty
+    catch (e) {
+        if (process.env.DEBUG || process.env.MONOMIND_DEBUG)
+            console.error('[autopilot-state] failed to load log file, returning empty:', e);
     }
     return [];
 }

package/packages/@monomind/cli/dist/src/browser/dashboard/server.js

@@ -125,7 +125,10 @@ export function getDashboardServer(port = DEFAULT_PORT) {
                             client.send(body);
                     }
                 }
-                catch { }
+                catch (e) {
+                    if (process.env.DEBUG || process.env.MONOMIND_DEBUG)
+                        console.error('[dashboard] /api/mastermind/event received invalid JSON, not broadcast:', e);
+                }
                 res.writeHead(200, { 'Content-Type': 'application/json' });
                 res.end('{"ok":true}');
             });

package/packages/@monomind/cli/dist/src/capabilities/manager.js

@@ -45,8 +45,10 @@ export class CapabilityManager {
             fs.writeFileSync(tmpPath, JSON.stringify({ active: [...this.active.keys()] }, null, 2));
             fs.renameSync(tmpPath, capsPath);
         }
-        catch {
+        catch (e) {
             // best-effort persistence; activation state still holds in-memory
+            if (process.env.DEBUG || process.env.MONOMIND_DEBUG)
+                console.error('[capabilities] failed to persist capabilities.json:', e);
         }
     }
     isActive(name) {

package/packages/@monomind/cli/dist/src/commands/agent-lifecycle.js

@@ -131,6 +131,16 @@ export const spawnCommand = {
                 priority: 'normal',
                 metadata: { name: agentName, capabilities: getAgentCapabilities(agentType) },
             });
+            // agent_spawn resolves (doesn't throw) on a tool-level failure like
+            // "agent store is unreadable" or "agent already exists" — callMCPTool
+            // only throws for registry/infra errors (tool not found/disabled), not
+            // for a handler's own {success:false} response. Without this check the
+            // CLI silently rendered a "spawned successfully" table full of
+            // undefined fields for a spawn that never actually happened.
+            if (result.success === false) {
+                output.printError(`Failed to spawn agent: ${result.error || 'unknown error'}`);
+                return { success: false, exitCode: 1 };
+            }
             output.writeln();
             output.printTable({
                 columns: [
@@ -230,6 +240,14 @@ export const statusCommand = {
         }
         try {
             const status = await callMCPTool('agent_status', { agentId, includeMetrics: true, includeHistory: false });
+            // agent_status resolves (doesn't throw) with {status:'not_found', error}
+            // for a nonexistent agent — callMCPTool only throws for registry/infra
+            // errors, not a handler's own not-found response. Without this check
+            // the CLI reported success:true for an agent that was never found.
+            if (status.error) {
+                output.printError(`Failed to get agent status: ${status.error}`);
+                return { success: false, exitCode: 1 };
+            }
             if (ctx.flags.format === 'json') {
                 output.printJson(status);
                 return { success: true, data: status };
@@ -296,6 +314,14 @@ export const stopCommand = {
             const result = await callMCPTool('agent_terminate', {
                 agentId, graceful: !force, reason: 'Stopped by user via CLI',
             });
+            // agent_terminate resolves (doesn't throw) with {success:false, error}
+            // for a nonexistent agent or an unreadable store — callMCPTool only
+            // throws for registry/infra errors. Without this check the CLI printed
+            // "stopped successfully" for an agent that was never actually stopped.
+            if (result.success === false) {
+                output.printError(`Failed to stop agent: ${result.error || 'unknown error'}`);
+                return { success: false, exitCode: 1 };
+            }
             if (!force) {
                 output.writeln(output.dim('  Completing current task...'));
                 output.writeln(output.dim('  Saving state...'));

package/packages/@monomind/cli/dist/src/commands/agent-ops.js

@@ -9,52 +9,36 @@ export const metricsCommand = {
     name: 'metrics',
     description: 'Show agent performance metrics',
     action: async (ctx) => {
-        const { existsSync, readFileSync, readdirSync, statSync } = await import('fs');
-        const { join } = await import('path');
+        // Previously read from .swarm/agents/*.json (one file per agent) — a
+        // directory nothing in the codebase has ever written to. agent_spawn
+        // (agent-tools.ts) persists to a single store.json at
+        // getMonomindDataRoot()/agents/store.json, keyed by agentId. This
+        // command was structurally incapable of reflecting a single real
+        // spawned agent; always reported zero regardless of activity. Read the
+        // real store instead.
+        const { loadAgentStore } = await import('../mcp-tools/agent-tools.js');
+        const store = loadAgentStore();
+        const agents = Object.values(store.agents);
         let totalAgents = 0;
         let activeAgents = 0;
         let tasksCompleted = 0;
         const typeCounts = {};
-        const swarmDir = join(process.cwd(), '.swarm');
-        const agentsDir = join(swarmDir, 'agents');
-        if (existsSync(agentsDir)) {
-            try {
-                const files = readdirSync(agentsDir).filter(f => f.endsWith('.json'));
-                for (const file of files) {
-                    try {
-                        const agentFilePath = join(agentsDir, file);
-                        if (statSync(agentFilePath).size > 512 * 1024)
-                            continue;
-                        const data = JSON.parse(readFileSync(agentFilePath, 'utf-8'));
-                        totalAgents++;
-                        const agType = data.type || 'unknown';
-                        if (!typeCounts[agType])
-                            typeCounts[agType] = { count: 0, tasks: 0, success: 0 };
-                        typeCounts[agType].count++;
-                        if (data.status === 'active' || data.status === 'running')
-                            activeAgents++;
-                        if (data.tasksCompleted) {
-                            typeCounts[agType].tasks += data.tasksCompleted;
-                            tasksCompleted += data.tasksCompleted;
-                        }
-                        if (data.successCount)
-                            typeCounts[agType].success += data.successCount;
-                    }
-                    catch { /* skip malformed */ }
-                }
-            }
-            catch { /* no agents dir */ }
-        }
-        const activityFile = join(swarmDir, 'swarm-activity.json');
-        if (existsSync(activityFile) && statSync(activityFile).size <= 10 * 1024 * 1024) {
-            try {
-                const activity = JSON.parse(readFileSync(activityFile, 'utf-8'));
-                if (activity.totalAgents && totalAgents === 0)
-                    totalAgents = activity.totalAgents;
-                if (activity.activeAgents && activeAgents === 0)
-                    activeAgents = activity.activeAgents;
-            }
-            catch { /* ignore */ }
+        for (const agent of agents) {
+            totalAgents++;
+            const agType = agent.agentType || 'unknown';
+            if (!typeCounts[agType])
+                typeCounts[agType] = { count: 0, tasks: 0 };
+            typeCounts[agType].count++;
+            if (agent.status !== 'terminated')
+                activeAgents++;
+            // AgentRecord tracks a single taskCount, not a completed/failed
+            // breakdown — this is the best available proxy for "task activity",
+            // not literally "completed" tasks. Success-rate data doesn't exist
+            // anywhere in the current agent store schema, so it's reported as
+            // N/A below rather than fabricated.
+            const taskCount = agent.taskCount || 0;
+            typeCounts[agType].tasks += taskCount;
+            tasksCompleted += taskCount;
         }
         let vectorCount = 0;
         try {
@@ -65,11 +49,9 @@ export const metricsCommand = {
         catch { /* backend unavailable */ }
         const byType = Object.entries(typeCounts).map(([type, data]) => ({
             type, count: data.count, tasks: data.tasks,
-            successRate: data.tasks > 0 ? `${Math.round((data.success / data.tasks) * 100)}%` : 'N/A',
+            successRate: 'N/A', // not tracked in the current agent store schema
         }));
-        const avgSuccessRate = tasksCompleted > 0
-            ? `${Math.round(Object.values(typeCounts).reduce((a, d) => a + d.success, 0) / tasksCompleted * 100)}%`
-            : 'N/A';
+        const avgSuccessRate = 'N/A'; // not tracked in the current agent store schema
         const metrics = {
             summary: {
                 totalAgents, activeAgents, tasksCompleted, avgSuccessRate, vectorCount,

package/packages/@monomind/cli/dist/src/commands/cleanup.d.ts

@@ -5,6 +5,24 @@
  * github.com/monoes/monomind
  */
 import type { Command } from '../types.js';
+/** A single stale-scratch candidate returned by {@link findStaleScratch}. */
+interface StaleScratchItem {
+    path: string;
+    description: string;
+    size: number;
+}
+/**
+ * Find stale mastermind scratch under `.monomind/taskdev/` and `.monomind/loops/`.
+ * Exported for tests. Never returns `progress.md` (the taskdev recovery ledger),
+ * directories, or loop JSON it cannot parse — deleting the unclassifiable loses data.
+ *
+ * A loop JSON is only ever classified as abandoned when it has a real, positive,
+ * numeric `nextRunAt` timestamp that is more than a day in the past. Live producers
+ * write `nextRunAt: 0` (real /do loops) or `nextRunAt: null` (dashboard) — those,
+ * along with missing/non-numeric values, are never eligible for deletion regardless
+ * of `status`, since a crashed daemon can leave a stale `status: 'running'` behind.
+ */
+export declare function findStaleScratch(cwd: string, now: number): StaleScratchItem[];
 /**
  * Cleanup command definition
  */

package/packages/@monomind/cli/dist/src/commands/cleanup.js

@@ -29,6 +29,95 @@ const KEEP_CONFIG_PATHS = [
     'monomind.config.json',
     join('.claude', 'settings.json'),
 ];
+/** Scratch pruning (--scratch): taskdev handoff files and loop state. */
+// monolean: manual flag only — upgrade path: invoke from the `cache` background worker so crashed-run scratch is pruned without anyone remembering the flag
+const SCRATCH_MAX_AGE_MS = 7 * 24 * 60 * 60 * 1000; // taskdev scratch older than this is stale
+const LOOP_STALE_GRACE_MS = 24 * 60 * 60 * 1000; // a live loop reschedules every <=1h; overdue by a day = abandoned
+/**
+ * Find stale mastermind scratch under `.monomind/taskdev/` and `.monomind/loops/`.
+ * Exported for tests. Never returns `progress.md` (the taskdev recovery ledger),
+ * directories, or loop JSON it cannot parse — deleting the unclassifiable loses data.
+ *
+ * A loop JSON is only ever classified as abandoned when it has a real, positive,
+ * numeric `nextRunAt` timestamp that is more than a day in the past. Live producers
+ * write `nextRunAt: 0` (real /do loops) or `nextRunAt: null` (dashboard) — those,
+ * along with missing/non-numeric values, are never eligible for deletion regardless
+ * of `status`, since a crashed daemon can leave a stale `status: 'running'` behind.
+ */
+export function findStaleScratch(cwd, now) {
+    const out = [];
+    const taskdevDir = join(cwd, '.monomind', 'taskdev');
+    if (existsSync(taskdevDir)) {
+        for (const f of readdirSync(taskdevDir)) {
+            if (f === 'progress.md')
+                continue; // the ledger is the recovery map — never auto-prune
+            try {
+                const st = lstatSync(join(taskdevDir, f));
+                if (st.isFile() && now - st.mtimeMs > SCRATCH_MAX_AGE_MS) {
+                    out.push({ path: join('.monomind', 'taskdev', f), description: 'stale taskdev scratch', size: st.size });
+                }
+            }
+            catch { /* raced away or unreadable — leave it */ }
+        }
+    }
+    const loopsDir = join(cwd, '.monomind', 'loops');
+    if (existsSync(loopsDir)) {
+        const entries = readdirSync(loopsDir);
+        const jsonStems = new Set(entries.filter(f => f.endsWith('.json')).map(f => f.replace(/\.json$/, '')));
+        for (const f of entries) {
+            try {
+                const st = lstatSync(join(loopsDir, f));
+                if (!st.isFile())
+                    continue;
+                if (f.endsWith('.json')) {
+                    const parsed = JSON.parse(readFileSync(join(loopsDir, f), 'utf8'));
+                    const { nextRunAt } = parsed;
+                    const isStale = typeof nextRunAt === 'number' &&
+                        Number.isFinite(nextRunAt) &&
+                        nextRunAt > 0 &&
+                        now - nextRunAt > LOOP_STALE_GRACE_MS;
+                    if (isStale) {
+                        out.push({ path: join('.monomind', 'loops', f), description: 'abandoned loop state', size: st.size });
+                    }
+                }
+                else if (f.endsWith('.stop') && !jsonStems.has(f.replace(/\.stop$/, ''))) {
+                    out.push({ path: join('.monomind', 'loops', f), description: 'orphaned loop stopfile', size: st.size });
+                }
+            }
+            catch { /* unparseable or unreadable — never delete what we cannot classify */ }
+        }
+    }
+    return out;
+}
+/**
+ * Report (dry run) or delete a batch of file/dir items, printing the same
+ * `[would remove]` / `[removed]` / `[failed]` lines used across cleanup modes.
+ * Shared by the scratch branch; the main artifact loop keeps its own copy
+ * because of the `--keep-config` `.claude/settings.json` preservation special case.
+ */
+function removeOrReport(cwd, items, dryRun) {
+    let removed = 0;
+    let removedSize = 0;
+    for (const item of items) {
+        const sizeStr = formatSize(item.size);
+        const typeLabel = item.type === 'dir' ? 'dir ' : 'file';
+        if (dryRun) {
+            output.writeln(output.warning(`  [would remove] ${typeLabel}  ${item.path}  (${sizeStr}) - ${item.description}`));
+        }
+        else {
+            try {
+                rmSync(join(cwd, item.path), { recursive: item.type === 'dir', force: true });
+                output.writeln(output.success(`  [removed] ${typeLabel}  ${item.path}  (${sizeStr}) - ${item.description}`));
+                removed++;
+                removedSize += item.size;
+            }
+            catch (err) {
+                output.writeln(output.error(`  [failed] ${typeLabel}  ${item.path}  - ${err instanceof Error ? err.message : String(err)}`));
+            }
+        }
+    }
+    return { removed, removedSize };
+}
 /**
  * Maximum directory recursion depth for size calculation.
  * Prevents stack overflow on deeply-nested or circular-symlink trees.
@@ -112,6 +201,13 @@ export const cleanupCommand = {
             type: 'boolean',
             default: false,
         },
+        {
+            name: 'scratch',
+            short: 's',
+            description: 'Prune only stale mastermind scratch (.monomind/taskdev, abandoned .monomind/loops state)',
+            type: 'boolean',
+            default: false,
+        },
     ],
     examples: [
         {
@@ -126,12 +222,37 @@ export const cleanupCommand = {
             command: 'cleanup --force --keep-config',
             description: 'Remove artifacts but keep configuration files',
         },
+        {
+            command: 'cleanup --scratch --force',
+            description: 'Delete stale taskdev scratch and abandoned loop state',
+        },
     ],
     action: async (ctx) => {
         const force = ctx.flags.force === true;
         const keepConfig = ctx.flags['keep-config'] === true;
         const cwd = ctx.cwd;
         const dryRun = !force;
+        if (ctx.flags.scratch === true) {
+            const now = Date.now();
+            output.writeln();
+            output.writeln(output.bold(dryRun ? 'Monomind Scratch Cleanup (dry run)' : 'Monomind Scratch Cleanup'));
+            output.writeln();
+            const stale = findStaleScratch(cwd, now);
+            if (stale.length === 0) {
+                output.writeln(output.info('No stale scratch found.'));
+                return { success: true, message: 'Nothing to clean' };
+            }
+            const { removed, removedSize } = removeOrReport(cwd, stale.map(item => ({ ...item, type: 'file' })), dryRun);
+            output.writeln();
+            if (dryRun) {
+                output.writeln(output.dim(`  ${stale.length} stale file(s). This was a dry run. Use --force to delete.`));
+                output.writeln();
+                return { success: true, message: `Dry run: ${stale.length} stale scratch file(s) found`, data: { found: stale, dryRun } };
+            }
+            output.writeln(`  Removed ${removed} file(s) totaling ${formatSize(removedSize)}`);
+            output.writeln();
+            return { success: true, message: `Removed ${removed} stale scratch file(s)`, data: { found: stale, removedCount: removed, removedSize, dryRun } };
+        }
         output.writeln();
         output.writeln(output.bold(dryRun
             ? 'Monomind Cleanup (dry run)'