@monoes/monomindcli 2.10.10 → 2.10.14

package/.claude/skills/mastermind-my-issues/SKILL.md

@@ -18,7 +18,7 @@ This skill is invoked by `mastermind:my-issues` or directly via `/mastermind:my-
 - `action`: list | assign-self | unassign | close
 - `assignee_id`: user/agent id to filter by (default: local-operator)
 - `issue_id`: issue id (required for assign-self / unassign / close)
-- `status_filter`: open | in_progress | all (default: open+in_progress)
+- `status_filter`: active | todo | in_progress | blocked | in_review | done | cancelled | all (default: active = todo+in_progress)
 - `caller`: command | master
 
 ---
@@ -41,6 +41,38 @@ issuesFile=".monomind/orgs/${org_name}-issues.json"
 assigneeFilter="${assignee_id:-local-operator}"
 ```
 
+Normalize any legacy records written by a pre-2.10 version of these skills. Idempotent — safe to run on every load.
+
+```bash
+python3 - "$issuesFile" <<'PYEOF'
+import json, sys
+path = sys.argv[1]
+data = json.load(open(path))
+RENAME = {
+    "assignee_id": "assigneeId", "assigned_to": "assigneeId",
+    "created_at": "createdAt", "updated_at": "updatedAt",
+    "closed_at": "closedAt", "project_id": "projectId",
+    "parent_id": "parentId", "recovery_status": "recoveryStatus",
+    "lastActivityAt": "updatedAt",
+}
+changed = False
+for iss in data.get("issues", []):
+    for old, new in RENAME.items():
+        if old in iss:
+            iss.setdefault(new, iss.pop(old))
+            iss.pop(old, None)
+            changed = True
+    if iss.get("status") == "open":
+        iss["status"] = "todo"
+        changed = True
+if changed:
+    tmp = path + ".tmp"
+    with open(tmp, "w") as f:
+        json.dump(data, f, indent=2)
+    import os; os.replace(tmp, path)
+PYEOF
+```
+
 ---
 
 ## Step 2 — Execute Action
@@ -57,19 +89,19 @@ echo "────────────────────────
 jq -r --arg uid "$assigneeFilter" --arg sf "$statusFilter" '
   (.issues // [])[] |
   select(
-    (.assigneeId == $uid or .assigned_to == $uid) and
-    (if $sf == "active" then (.status == "open" or .status == "in_progress")
+    (.assigneeId == $uid) and
+    (if $sf == "active" then (.status == "todo" or .status == "in_progress")
      elif $sf == "all" then true
      else .status == $sf
      end)
   ) |
-  [.id, (.status // "open"), (.priority // "medium"), (.title // "(no title)")] | @tsv
+  [.id, (.status // "todo"), (.priority // "medium"), (.title // "(no title)")] | @tsv
 ' "$issuesFile" | while IFS=$'\t' read -r id st pri title; do
   printf "%-24s %-12s %-10s %s\n" "$id" "$st" "$pri" "$title"
 done
 
 total=$(jq -r --arg uid "$assigneeFilter" \
-  '[(.issues // [])[] | select(.assigneeId == $uid or .assigned_to == $uid)] | length' \
+  '[(.issues // [])[] | select(.assigneeId == $uid)] | length' \
   "$issuesFile")
 echo ""
 echo "Total assigned: $total"
@@ -88,7 +120,7 @@ ts=$(date -u +%Y-%m-%dT%H:%M:%SZ)
 tmp="${issuesFile}.tmp"
 jq --arg id "$issue_id" --arg uid "$assigneeFilter" --arg ts "$ts" \
   '.issues = [(.issues // [])[] | if .id == $id then
-     .assigneeId = $uid | .lastActivityAt = $ts
+     .assigneeId = $uid | .assigneeUserId = $uid | .assigneeAgentId = null | .updatedAt = $ts
    else . end]' \
   "$issuesFile" > "$tmp" && mv "$tmp" "$issuesFile"
 
@@ -104,7 +136,7 @@ ts=$(date -u +%Y-%m-%dT%H:%M:%SZ)
 tmp="${issuesFile}.tmp"
 jq --arg id "$issue_id" --arg ts "$ts" \
   '.issues = [(.issues // [])[] | if .id == $id then
-     .assigneeId = null | .lastActivityAt = $ts
+     .assigneeId = null | .assigneeUserId = null | .assigneeAgentId = null | .updatedAt = $ts
    else . end]' \
   "$issuesFile" > "$tmp" && mv "$tmp" "$issuesFile"
 
@@ -120,7 +152,7 @@ ts=$(date -u +%Y-%m-%dT%H:%M:%SZ)
 tmp="${issuesFile}.tmp"
 jq --arg id "$issue_id" --arg ts "$ts" \
   '.issues = [(.issues // [])[] | if .id == $id then
-     .status = "done" | .closedAt = $ts | .lastActivityAt = $ts
+     .status = "done" | .closedAt = $ts | .updatedAt = $ts
    else . end]' \
   "$issuesFile" > "$tmp" && mv "$tmp" "$issuesFile"
 

package/.claude/skills/mastermind-org/SKILL.md

@@ -14,3 +14,5 @@ Use the `monomind org` commands as the portable organization control surface.
 - Stop a running organization with `monomind org stop <name>`.
 
 Before changing organization configuration, inspect its current status and preserve the user's explicit goal, budget, and safety constraints. Use the platform's native task and agent interfaces when available; otherwise keep the CLI as the functional source of truth.
+
+The org runtime does not read `<org>-issues.json`. Work is driven by the org definition's roles and goal plus an optional `--task` string.

package/.claude/skills/mastermind-plan/SKILL.md

@@ -40,6 +40,7 @@ If the spec covers multiple independent subsystems, it should have been broken i
 
 Before defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.
 
+- Check `brain_context` for relevant prior lessons or patterns for this domain/project — past task-granularity mistakes, file-organization conventions, known gotchas — and apply them to the decomposition below. Note when a decomposition choice is informed by recalled history.
 - Design units with clear boundaries and well-defined interfaces. Each file should have one clear responsibility.
 - You reason best about code you can hold in context at once, and your edits are more reliable when files are focused. Prefer smaller, focused files over large ones that do too much.
 - Files that change together should live together. Split by responsibility, not by technical layer.
@@ -73,7 +74,7 @@ A task is the smallest unit that carries its own test cycle and is worth a fresh
 ```markdown
 # [Feature Name] Implementation Plan
 
-> **For agentic workers:** REQUIRED SUB-SKILL: Use `Skill("mastermind-taskdev")` (recommended) or `Skill("mastermind-execute")` to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
+> **For agentic workers:** REQUIRED SUB-SKILL: Use `Skill("mastermind-execute")` to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
 
 **Goal:** [One sentence describing what this builds]
 
@@ -196,22 +197,12 @@ Wait for the user's response. If they request changes, make them inline and re-r
 
 After the plan is approved (or in auto mode, after self-review):
 
-**In confirm mode (default):** Ask the user to choose execution mode:
+**In confirm mode (default):** Ask the user to confirm execution:
 
-**"Plan complete and saved to `docs/mastermind/plans/<filename>.md`. Two execution options:**
+**"Plan complete and saved to `docs/mastermind/plans/<filename>.md`. Execute it now with `mastermind-execute`?"**
 
-**1. Subagent-Driven (recommended)** — Invoke `Skill("mastermind-taskdev")`: dispatches a fresh subagent per task, reviews between tasks, fast iteration.
+**In auto mode:** Skip the question — invoke `Skill("mastermind-execute")` immediately.
 
-**2. Inline Execution** — Invoke `Skill("mastermind-execute")`: batch execution with checkpoints.
-
-**Which approach?"**
-
-**In auto mode:** Skip the question. Default to subagent-driven — invoke `Skill("mastermind-taskdev")` immediately.
-
-**If Subagent-Driven chosen (or auto mode):**
-- Invoke `Skill("mastermind-taskdev")`
-- Fresh subagent per task + two-stage review
-
-**If Inline Execution chosen:**
+**On execution:**
 - Invoke `Skill("mastermind-execute")`
-- Batch execution with checkpoints for review
+- It loads the plan, reviews it critically, and works task-by-task with checkpoints for review

package/.claude/skills/mastermind-plan-to-tasks/SKILL.md

@@ -70,15 +70,24 @@ Read the plan carefully and apply these rules:
 
 **Decomposition output:**
 
-For each issue extracted from the plan, produce:
-```
-ISSUE: <title>
-  assignee:    <agent-id or UNASSIGNED>
-  priority:    low | medium | high | urgent
-  blockedBy:   <issue-title> (or none)
-  description: <1-2 sentence summary of the deliverable>
+For each issue extracted from the plan, emit one object into a JSON array and write the
+whole array to `.monomind/orgs/<org_name>-plan-decomposition.json` using the Write tool:
+
+```json
+[
+  {
+    "title": "Short imperative deliverable name",
+    "description": "1-2 sentence summary of the deliverable",
+    "assignee": "<agent-id from the org roster, or null if unassigned>",
+    "priority": "low | medium | high | urgent",
+    "blockedBy": ["<exact title of a blocking issue in this same array>"]
+  }
+]
 ```
 
+Titles must be unique within the array — `blockedBy` is resolved by exact title match.
+Use `[]` for `blockedBy` when an issue has no blockers.
+
 **Quality checklist before creating:**
 - [ ] Enough detail that assignees can act without re-asking
 - [ ] Every concrete deliverable is an issue
@@ -91,31 +100,130 @@ ISSUE: <title>
 
 ## Step 4 — Create Issues (unless dry_run=true)
 
+Reads the decomposition written in Step 3, assigns collision-free ids, validates assignees
+against the org roster, resolves `blockedBy` titles into `blockedByIssueIds`, and appends
+to the issues file atomically. Fails loudly on any unresolved or ambiguous reference —
+an unresolved blocker silently dropped is exactly what produces a `blocked` issue with an
+empty `blockedByIssueIds`, which `mastermind-liveness` reports as stalled.
+
 ```bash
 issuesFile=".monomind/orgs/${org_name}-issues.json"
+decompFile=".monomind/orgs/${org_name}-plan-decomposition.json"
 [ ! -f "$issuesFile" ] && echo '{"issues":[]}' > "$issuesFile"
+[ ! -f "$decompFile" ] && { echo "ERROR: $decompFile not found — Step 3 must write it first."; exit 1; }
 
 ts=$(date -u +%Y-%m-%dT%H:%M:%SZ)
 
-# Issues are created from the decomposition above
-# Each issue gets:
-#   id: issue-<timestamp>-<N>
-#   title, description, priority, status: open
-#   assigneeId (from matched agent)
-#   projectId, workspaceId (if provided)
-#   blockedByIssueIds (resolved after all issues are created)
-#   createdAt, updatedAt
-
-echo ""
-if [ "${dry_run:-false}" = "true" ]; then
-  echo "DRY RUN — no issues were created."
-  echo "Remove --dry-run to create these issues."
-else
-  echo "CREATED ISSUES:"
-  # (issue creation happens inline above as each issue is decomposed)
-fi
+python3 - "$issuesFile" "$decompFile" "$orgFile" "${project_id:-}" "${workspace_id:-}" "${dry_run:-false}" "$ts" <<'PYEOF'
+import json, os, sys, time
+
+issues_path, decomp_path, org_path, project_id, workspace_id, dry_run, ts = sys.argv[1:]
+dry = dry_run == "true"
+
+VALID_PRIORITY = {"low", "medium", "high", "urgent"}
+
+decomp = json.load(open(decomp_path))
+if not isinstance(decomp, list) or not decomp:
+    print("ERROR: decomposition must be a non-empty JSON array.")
+    sys.exit(1)
+
+roster = {r.get("id") for r in json.load(open(org_path)).get("roles", [])}
+data   = json.load(open(issues_path))
+issues = data.setdefault("issues", [])
+
+# --- Validate before mutating anything ---
+errors, titles = [], {}
+for n, item in enumerate(decomp, 1):
+    title = (item.get("title") or "").strip()
+    if not title:
+        errors.append(f"item {n}: missing title")
+        continue
+    if title in titles:
+        errors.append(f"item {n}: duplicate title {title!r} — titles must be unique to resolve blockedBy")
+    titles[title] = None
+    pri = item.get("priority") or "medium"
+    if pri not in VALID_PRIORITY:
+        errors.append(f"{title!r}: priority {pri!r} must be one of {sorted(VALID_PRIORITY)}")
+    asgn = item.get("assignee")
+    if asgn and asgn not in roster:
+        errors.append(f"{title!r}: assignee {asgn!r} is not a role in this org (roster: {sorted(roster)})")
+
+existing_by_title = {i.get("title"): i.get("id") for i in issues}
+for item in decomp:
+    for b in item.get("blockedBy") or []:
+        if b not in titles and b not in existing_by_title:
+            errors.append(f"{item.get('title')!r}: blockedBy {b!r} matches no issue in this batch or in the existing file")
+
+if errors:
+    print("ERROR: decomposition did not validate — no issues were created.")
+    for e in errors:
+        print(f"  · {e}")
+    sys.exit(1)
+
+# --- Assign ids (batch-stable, collision-free) ---
+batch = int(time.time() * 1000)
+for n, item in enumerate(decomp, 1):
+    titles[item["title"].strip()] = f"issue-{batch}-{n:03d}"
+
+def resolve(t):
+    return titles.get(t) or existing_by_title[t]
+
+created = []
+for item in decomp:
+    title = item["title"].strip()
+    created.append({
+        "id": titles[title],
+        "title": title,
+        "description": item.get("description") or "",
+        "status": "todo",
+        "priority": item.get("priority") or "medium",
+        "assigneeId": item.get("assignee") or None,
+        "assigneeAgentId": item.get("assignee") or None,
+        "assigneeUserId": None,
+        "parentId": None,
+        "projectId": project_id or None,
+        "workspaceId": workspace_id or None,
+        "blockedByIssueIds": [resolve(b) for b in (item.get("blockedBy") or [])],
+        "createdAt": ts,
+        "updatedAt": ts,
+    })
+
+if dry:
+    print("DRY RUN — no issues were created. Would create:")
+    for c in created:
+        blockers = ", ".join(c["blockedByIssueIds"]) or "none"
+        print(f"  {c['id']}  [{c['priority']:<6}] {c['title']}")
+        print(f"      assignee: {c['assigneeId'] or 'UNASSIGNED'}   blockedBy: {blockers}")
+    print(f"\n  {len(created)} issue(s) would be created.")
+    sys.exit(0)
+
+issues.extend(created)
+tmp = issues_path + ".tmp"
+with open(tmp, "w") as f:
+    json.dump(data, f, indent=2)
+os.replace(tmp, issues_path)
+
+print("CREATED ISSUES:")
+for c in created:
+    blockers = ", ".join(c["blockedByIssueIds"]) or "none"
+    print(f"  {c['id']}  [{c['priority']:<6}] {c['title']}")
+    print(f"      assignee: {c['assigneeId'] or 'UNASSIGNED'}   blockedBy: {blockers}")
+print(f"\n  {len(created)} issue(s) created in {issues_path}")
+
+roots = [c for c in created if not c["blockedByIssueIds"]]
+print(f"  {len(roots)} issue(s) are unblocked and can start in parallel.")
+PYEOF
+
+rm -f "$decompFile"
 ```
 
+> **These issues are not auto-consumed by the org runtime.** `OrgDaemon` builds its `TaskDag`
+> fresh in memory on every start and never reads `<org>-issues.json` (verified: zero references
+> in `packages/@monomind/cli/src/orgrt/`). Issues created here are tracked by the
+> `mastermind-issues` / `mastermind-my-issues` / `mastermind-liveness` skills and shown in the
+> dashboard, but running `monomind org run <org>` will not pick them up. Drive execution from
+> this file with `mastermind-execute`, or pass work explicitly via `org run --task`.
+
 ---
 
 ## Step 5 — Return Output

package/.claude/skills/mastermind-protocol/SKILL.md

@@ -30,17 +30,19 @@ Execute at the START of every mastermind run (master or standalone domain comman
 
 **Step A — Tier 3 core principles (all domains):**
 Try `mcp__monomind__memory_hierarchical-recall` with query `"mastermind principles"`, topK 20.
-If it returns `"LanceDB bridge not available"` or any error, fall back to:
+If it returns an error, fall back to:
 `mcp__monomind__memory_pattern-search` with query `"mastermind principles"`, namespace `"mastermind:principles"`, limit 20.
+Record the entry ids of whichever call actually returned results — `results[].id` from `memory_hierarchical-recall`, or `patterns[].id` from the `memory_pattern-search` fallback — into a running list: `recalled_entry_ids`.
 
 **Step B — Tier 2 weekly summary for this domain:**
 Try `mcp__monomind__memory_context-synthesize` with query `[current prompt keywords]`, maxEntries 10.
 If it fails, fall back to:
 `mcp__monomind__memory_pattern-search` with query `[current prompt keywords]`, namespace `"mastermind:<domain>:weekly"`, limit 10.
+`memory_context-synthesize` returns only a `context` string and a `sources` count — no entry ids — so it cannot add to `recalled_entry_ids`. Only the `memory_pattern-search` fallback contributes ids (`patterns[].id`); append them to `recalled_entry_ids` when that fallback runs.
 
 **Step C — Relevant graph nodes:**
 Call `mcp__monomind__monograph_query` with question `[3-5 keywords extracted from current prompt]`, depth 2.
-If the graph is not built yet (error: "No graph found"), skip this tier — continue without graph context.
+If the graph is not built yet (error: "No graph found"), skip this tier — continue without graph context. Graph nodes are not memory entries and never contribute to `recalled_entry_ids`.
 
 Combine all results into a **BRAIN CONTEXT** block. Insert this block before any planning, decomposition, or agent spawning step. Format:
 
@@ -54,19 +56,30 @@ Combine all results into a **BRAIN CONTEXT** block. Insert this block before any
 
 If any MCP call fails or returns empty, continue without that tier — do not abort the run.
 
+**Step D — Visible recall confirmation:**
+Immediately after loading, print one short line as part of the calling skill's normal output — not buried inside the BRAIN CONTEXT block or an internal note the user never sees:
+- If anything was recalled: `Remembered: <one-line gist of the single most relevant recalled item>`
+- If every tier came back empty: `Nothing relevant recalled.`
+
+Keep `recalled_entry_ids` in scope for the rest of the run — the Brain Write Procedure's feedback step below needs it. Memory tools are stateless between calls, so the calling skill (not the MCP server) is what carries this list forward.
+
 ---
 
 ## Brain Write Procedure
 
 Execute at the END of every mastermind run. Always runs even if execution was partial or blocked.
 
-**Step 1 — Score this run:**
-```
-score = confidence × (1 / (days_since_run + 1)) × log(uses + 1)
-```
-- `confidence`: average of all decision confidence values from the unified output schema
-- `days_since_run`: 0 (this is a fresh run)
-- `uses`: 1 (first write)
+**Step 1 — Close the feedback loop on recalled memory:**
+If `recalled_entry_ids` from the Brain Load Procedure is non-empty, call `mcp__monomind__memory_feedback`:
+- `taskId`: the `run_id` used in this run's unified output schema (ISO8601 timestamp) — also the idempotency key, so a retried or duplicated call for the same run never double-applies the rating
+- `entryIds`: `recalled_entry_ids`
+- `quality`: average of `decisions[].confidence` (0.0-1.0) from this run's unified output schema; omit if `decisions` is empty
+- `success`: `true` when `status: complete`, or `status: partial` with no `outcome: reverted` decisions and no user rejection/correction of the recalled guidance during the run; otherwise `false`
+- `agent`: `<domain>` (this skill's domain)
+
+This applies an EWMA update to `feedback_weight` on each recalled entry (idempotent per `taskId`) and appends a feedback-event record via the same tool call. If `recalled_entry_ids` is empty — e.g. Brain Load only got a hit from `memory_context-synthesize`, which returns no entry ids — skip this call; there is nothing to rate.
+
+`score` referenced in Steps 2-3 below is this same value: the average of `decisions[].confidence` from this run's unified output schema. The old day/use decay factors were already constants on a fresh write (day 0, first use), so this is equivalent and simpler.
 
 **Step 2 — Append to Tier 1 raw log:**
 Try `mcp__monomind__memory_hierarchical-store` with:
@@ -74,7 +87,7 @@ Try `mcp__monomind__memory_hierarchical-store` with:
 - content: [full unified output schema YAML from this run, as a string]
 - metadata: `{ score, project, run_id, date: ISO8601, domain }`
 
-If LanceDB is unavailable, fall back to `mcp__monomind__memory_pattern-store`:
+If hierarchical storage is unavailable, fall back to `mcp__monomind__memory_pattern-store`:
 - key: `mastermind:<domain>:run:<run_id>`
 - value: [JSON-encoded unified output schema]
 - namespace: `mastermind:<domain>:raw`
@@ -82,7 +95,7 @@ If LanceDB is unavailable, fall back to `mcp__monomind__memory_pattern-store`:
 
 **Step 3 — Check weekly compaction trigger:**
 Try `mcp__monomind__memory_health` on namespace `mastermind:<domain>:raw`.
-If unavailable, call `mcp__monomind__memory_stats` and check entry count manually.
+If unavailable, call `mcp__monomind__memory_health` and check entry count manually.
 If `entry_count >= 20` OR `days_since_last_compaction >= 7`:
 1. Retrieve all Tier 1 entries since last compaction
 2. Produce a per-domain weekly summary (use LLM synthesis: "Summarize the key decisions, patterns, and lessons from these run logs in under 300 words")
@@ -94,7 +107,7 @@ Call `mcp__monomind__monograph_community` for nodes matching `mastermind:<domain
 If 3+ similar memory nodes are detected in a cluster:
 1. Merge into a single principle via LLM: "Distill these memories into one clear principle in 1-2 sentences"
 2. Store principle: `mcp__monomind__memory_hierarchical-store` namespace `mastermind:principles`
-3. Add `EXCEPTION` edge in Monograph for any conflicting memory: `mcp__monomind__monograph_add_fact`
+3. Add `EXCEPTION` edge in Monograph for any conflicting memory: `mcp__monomind__memory_kg_ingest`
 
 ---
 
@@ -126,19 +139,17 @@ Empty fields use `[]`. The `status` field reflects the highest-level result: `co
 
 ---
 
-## Memory Scoring Formula
+## Memory Feedback Loop
 
-```
-score = confidence × (1 / (days_since_run + 1)) × log(uses + 1)
-```
+Recalled memories are rated for real via `mcp__monomind__memory_feedback` (Brain Write Procedure, Step 1) — not a locally-computed formula. `score` (used by Steps 2-3 for the newly-stored run entry) is the average of `decisions[].confidence` from the unified output schema.
 
-| Variable | Source |
+| Concept | Mechanism |
 |---|---|
-| `confidence` | Average of `decisions[].confidence` from output schema |
-| `days_since_run` | 0 on day of run, increases 1 per calendar day |
-| `uses` | Incremented each time this memory is returned by brain load |
-| Archive threshold | score < 0.1 |
-| Reinforcement | Increment `uses` on every brain load hit |
+| `feedback_weight` | Per-entry EWMA, updated by `memory_feedback`'s `quality`/`success` params, blended into future ranking (`bridgeApplyFeedback` in `memory-bridge.ts`) |
+| `frequency_weight` | Incremented automatically on every recall hit, inside the `memory_hierarchical-recall` / `memory_pattern-search` handlers themselves — protects frequently-used entries from GC |
+| Idempotency | `memory_feedback`'s `taskId` is the idempotency key — the same `run_id` never double-applies a rating |
+| Archive threshold | score < 0.1 (Step 3 above) |
+| GC protection | `bridgeConsolidate` never collects entries with `feedback_weight > 0.6` or `frequency_weight >= 3` |
 
 ---
 

package/.claude/skills/mastermind-runorg/SKILL.md

@@ -30,14 +30,33 @@ no curl emissions, no delivery gaps.
    if step 3 ran).
    - Valid → step 5.
    - Invalid → surface the validator output and stop.
-5. **Start.**
+5. **Estimate scope and budget.** Before starting, read the numbers already sitting in
+   the org config and print a short summary — this is a read-and-summarize step, not a
+   spend prediction, so the user sees scope and the configured ceiling before any agent-hour
+   is spent, not only after the run stops on a budget:
+   ```bash
+   orgFile=".monomind/orgs/<name>.json"
+   roleCount=$(jq '.roles | length' "$orgFile")
+   maxConcurrent=$(jq -r '.run_config.max_concurrent_agents // 4' "$orgFile")
+   orgBudgetTokens=$(jq -r '.run_config.budget_tokens // 1000000' "$orgFile")
+   roleBudgets=$(jq -r '.roles[] | "  - \(.id): budget_tokens=\(.budget_tokens // "org-default split"), budget_usd=\(.budget_usd // "none")"' "$orgFile")
+   echo "About to run ${roleCount} role(s) (max ${maxConcurrent} concurrent)."
+   echo "Org-wide token budget ceiling: ${orgBudgetTokens}"
+   echo "Per-role overrides:"
+   echo "${roleBudgets}"
+   ```
+   Print this summary unconditionally (auto and confirm mode alike) before step 6.
+6. **Start.**
    - One-shot (no `schedule` in config): run in background bash:
      `monomind org run <name> --task "<optional task from params>"`
    - Scheduled (`schedule` set): ensure the daemon host is up:
      `monomind org serve` (background) — it picks up every scheduled org.
-6. **Confirm liveness.** Within ~15 s: `monomind org status <name>` shows
+7. **Confirm liveness.** Within ~15 s: `monomind org status <name>` shows
    `running`. Surface the dashboard link (`<CTRL_URL>/orgs`) and
    `monomind org logs <name> --follow` as the tail command.
-7. **Never** spawn a boss Task agent, create monotask boards, or emit
+8. **Never** spawn a boss Task agent, create monotask boards, or emit
    dashboard events manually. If the user explicitly asks for the legacy
    behavior, direct them to `/mastermind:runorgv1` (deprecated).
+
+The org runtime does not read `<org>-issues.json`. Work is driven by the org
+definition's roles and goal plus an optional `--task` string.

package/.claude/skills/mastermind-skill-builder/SKILL.md

@@ -192,7 +192,7 @@ Use words Claude would search for:
 ```markdown
 # GOOD: Explicit requirement marker
 **REQUIRED SUB-SKILL:** Use Skill("mastermind-worktree")
-**REQUIRED BACKGROUND:** You MUST understand Skill("mastermind-finish")
+**REQUIRED BACKGROUND:** You MUST understand Skill("mastermind-review")
 
 # BAD: Unclear if required
 See mastermind/worktree.md

package/.claude/skills/mastermind-tasks/SKILL.md

@@ -5,6 +5,11 @@ type: domain-skill
 default_mode: auto
 ---
 
+> **LEGACY-ORG-V1 — writes to a monotask board, not to `<org>-issues.json`.** This skill's
+> `parent_id`, `status` (`todo | doing | done`), and card model belong to the pre-v2
+> board-backed runner. For v2 issue tracking — including sub-issues — use
+> `/mastermind:issues --action create --parent-id <id>`.
+
 # Mastermind Tasks
 
 This skill is invoked by `mastermind:tasks` or directly via `/mastermind:tasks`.

package/.claude/skills/mastermind-techport/SKILL.md

@@ -54,7 +54,7 @@ IF health.commitsBehind > 0 OR health.status != "fresh":
 ```
 Call mcp__monomind__monograph_god_nodes({})         // load-bearing files — porting near them is dangerous
 Call mcp__monomind__monograph_community({})          // module cluster structure — boundary map
-Call mcp__monomind__monograph_bridge({})             // cross-community connectors — architectural seams
+Call mcp__monomind__monograph_surprises({})          // cross-community connectors — architectural seams
 Call mcp__monomind__monograph_stats({})              // fan-in/out percentile distribution
 Call mcp__monomind__monograph_query({ query: focus_hint OR "core architecture skills commands hooks agents" })
 ```

package/.claude/skills/monodesign/scripts/detector/engines/browser/drivers.mjs

@@ -28,11 +28,20 @@
 // Selection: MONODESIGN_BROWSER_DRIVER=monobrowse|puppeteer forces one;
 // otherwise monobrowse is tried first and puppeteer is the fallback.
 
-import { Socket } from 'node:net';
+import { createServer } from 'node:net';
+import { mkdtempSync, rmSync } from 'node:fs';
+import { tmpdir } from 'node:os';
+import { join } from 'node:path';
 
 const DRIVER_ENV = 'MONODESIGN_BROWSER_DRIVER';
-const CDP_PORT_RELEASE_TIMEOUT_MS = 5_000;
+// Windows CI teardown is the slow case: Chrome acknowledges Browser.close long
+// before the process exits and hands the socket back, and closeBrowser()'s
+// force-kill safety net is itself a deferred 1s timer. 5s is comfortable
+// locally but cuts into a loaded runner's teardown, so give CI more runway —
+// same reasoning as launchTimeoutMs below.
+const CDP_PORT_RELEASE_TIMEOUT_MS = process.env.CI ? 15_000 : 5_000;
 const CDP_PORT_RELEASE_POLL_MS = 25;
+const PROFILE_CLEANUP_RETRY_MS = 2_000;
 
 // Ports we launch headless Chrome on for detection runs. Deliberately away
 // from 9222 (the default `monomind browse` port): we must never attach to a
@@ -60,25 +69,36 @@ function withTimeout(promise, ms, label) {
   return Promise.race([promise, timeout]).finally(() => clearTimeout(handle));
 }
 
-function isPortListening(port) {
+// "Released" has to mean BINDABLE, not merely unreachable. A connect probe
+// stops succeeding as soon as Chrome's listener socket closes, which happens
+// early in its shutdown — while the process is still alive holding both the
+// port and the --user-data-dir singleton lock for this port. On Windows that
+// gap is wide and the socket stays unbindable across it (node does not set
+// SO_REUSEADDR there), so close() reported success and the next launch on the
+// same forced port sat until its timeout: "Chrome failed to start on port N
+// within 30000ms". Binding is the question the next launch actually asks, so
+// ask it directly. A listener that never accepted a connection leaves no
+// TIME_WAIT behind, so probing this way does not itself hold the port.
+function isPortBindable(port) {
   return new Promise((resolve) => {
-    const socket = new Socket();
-    const done = (listening) => {
-      socket.removeAllListeners();
-      socket.destroy();
-      resolve(listening);
-    };
-    socket.once('connect', () => done(true));
-    socket.once('error', () => done(false));
-    socket.setTimeout(250, () => done(false));
-    socket.connect(port, '127.0.0.1');
+    const server = createServer();
+    server.once('error', () => resolve(false));
+    server.listen(port, '127.0.0.1', () => server.close(() => resolve(true)));
   });
 }
 
+function removeProfileDir(dir) {
+  try {
+    rmSync(dir, { recursive: true, force: true });
+  } catch {
+    /* reclaimed by the OS's temp cleanup instead */
+  }
+}
+
 async function waitForCdpPortRelease(port) {
   const deadline = Date.now() + CDP_PORT_RELEASE_TIMEOUT_MS;
   while (Date.now() < deadline) {
-    if (!(await isPortListening(port))) return;
+    if (await isPortBindable(port)) return;
     await new Promise(resolve => setTimeout(resolve, CDP_PORT_RELEASE_POLL_MS));
   }
   throw new Error(`Chrome did not release CDP port ${port} within ${CDP_PORT_RELEASE_TIMEOUT_MS}ms`);
@@ -178,7 +198,20 @@ async function launchMonobrowseBrowser(options = {}) {
   // browser starts fine, just later. Give CI more runway; local dev keeps
   // the tighter default so a genuinely broken launch still fails fast.
   const launchTimeoutMs = options.launchTimeoutMs ?? (process.env.CI ? 30000 : undefined);
-  const launchedPort = await mb.launchBrowser({ port, headless, args: launchArgs, launchTimeoutMs });
+  // Throwaway profile per launch. monobrowse defaults --user-data-dir to
+  // tmpdir()/monomind-browser-<port>, which is right for `monomind browse`
+  // (a later process reattaches to the same session by port) but wrong here:
+  // detection launches are stateless, and keying the profile on the port
+  // means two launches on the SAME port share one profile. Chrome enforces
+  // single-instance-per-profile, so the second launch rendezvouses with the
+  // first instead of starting its own — it hands over its command line and
+  // exits without ever opening a debugging port, which surfaces as "Chrome
+  // failed to start on port N" after the full launch timeout. Windows is
+  // where this bites: its singleton lock survives the previous Chrome being
+  // force-killed, and outlives the port being released. A unique dir removes
+  // the sharing entirely rather than racing the lock's cleanup.
+  const userDataDir = mkdtempSync(join(tmpdir(), 'monodesign-cdp-'));
+  const launchedPort = await mb.launchBrowser({ port, headless, args: launchArgs, launchTimeoutMs, userDataDir });
   // Control connection (to the initial about:blank tab) — used for lifecycle
   // commands; detection pages get their own dedicated connections.
   const control = await mb.connectToTarget(launchedPort);
@@ -217,6 +250,14 @@ async function launchMonobrowseBrowser(options = {}) {
         await waitForCdpPortRelease(launchedPort);
       } finally {
         control.client.close();
+        // Best effort, twice: Chrome is still flushing profile data when the
+        // port comes back, so an immediate delete gets a few files recreated
+        // under it. The unref'd retry lands after that (same pattern as
+        // monobrowse's own post-close force-kill net) and never holds the
+        // process open. Whatever still survives is a few KB under tmpdir that
+        // nothing reuses, so neither attempt may fail close().
+        removeProfileDir(userDataDir);
+        setTimeout(() => removeProfileDir(userDataDir), PROFILE_CLEANUP_RETRY_MS).unref?.();
       }
     },
   };

package/.claude/skills/performance-analysis/SKILL.md

@@ -280,7 +280,7 @@ instance and let Grafana draw the trends.
 - **`mastermind-debug`** — Phase 1 root-cause methodology underpins this skill
 - **`swarm-orchestration`** — topology decisions driven by bottleneck findings
 - **`verification-quality`** — confirm the optimization actually held
-- **`mastermind-verify`** — evidence-before-claims for "is it faster?"
+- **`mastermind-review`** — evidence-before-claims for "is it faster?"
 
 ## Quick Reference