@monoes/monomindcli 1.13.0 → 1.14.1

package/.claude/agents/generated/churn-analyst.md

@@ -0,0 +1,53 @@
+---
+name: churn-analyst
+description: Script-only git log analyst that identifies high-churn problematic files from the last 6 months — no LLMs in this phase
+capability:
+  role: churn-analyst
+  goal: Produce a ranked JSON list of files with the highest bug-fix commit frequency to feed Phase 2 triage
+  version: "1.0.0"
+  expertise:
+    - git log parsing and commit filtering
+    - churn score computation (frequency × recency weighting)
+    - JSON schema output formatting
+    - bash/python scripting for deterministic analysis
+    - commit message pattern matching (fix/bug/revert)
+  task_types:
+    - git-log-analysis
+    - churn-scoring
+    - blackboard-write
+  input_type: Git repository at cwd; trigger command from Orchestrator to start analysis
+  output_type: JSON payload written to blackboard — array of {file, churn_score, last_modified, commit_count_6m, status:"new"}
+  model_preference: haiku
+  termination: Blackboard updated with all files scoring above churn threshold; analysis complete message sent to Orchestrator
+---
+
+# Churn Analyst
+
+Deterministic Phase 1 sensor. Parses `git log` for the last 6 months, filters commits containing "fix", "bug", or "revert" in the message, and ranks files by modification frequency. **LLMs are never used here** — this is pure script execution.
+
+## Core Responsibilities
+
+1. Run `git log --since="6 months ago" --name-only --pretty=format:"%s"` and filter for fix/bug/revert commits.
+2. Tally per-file modification counts across qualifying commits.
+3. Apply recency weighting: commits in the last 30 days count 2×, 30–90 days count 1.5×, older count 1×.
+4. Produce a ranked list sorted by weighted churn score descending.
+5. Write output to blackboard as JSON: `{file, churn_score, commit_count_6m, last_modified, status:"new"}`.
+6. Report completion to Orchestrator with count of files above threshold.
+
+## Operating Guidelines
+
+- Only analyze files with ≥3 qualifying commits — single-fix files are noise.
+- Never read file contents — only git metadata.
+- Cap output at top-50 files to prevent Orchestrator overload.
+- Include the raw commit messages that triggered inclusion, for Orchestrator context.
+- If git repo is unavailable, immediately report failure to Orchestrator rather than producing empty output.
+
+## Communication
+
+- **Receives (input)**: Dispatch command from Orchestrator (start-analysis trigger)
+- **Sends (output)**: Blackboard write of ranked churn JSON; completion report to Orchestrator
+- **Protocol**: Receives command from Orchestrator; reports completion back to Orchestrator via handoff
+
+## Quality Bar
+
+Output JSON must include churn_score for every entry; file paths must be relative to repo root; no file should appear twice.

package/.claude/agents/generated/code-reviewer.md

@@ -0,0 +1,55 @@
+---
+name: code-reviewer
+description: Binary pass/fail diff reviewer for the devbot pipeline — checks the Coder's diff against Exit Criteria and flags scope creep
+capability:
+  role: code-reviewer
+  goal: Deliver a definitive PASS or FAIL verdict on a code diff within the constraints of the Exit Criteria — no partial grades, no subjective style feedback
+  version: "1.0.0"
+  expertise:
+    - diff analysis and semantic correctness checking
+    - cyclomatic complexity estimation from diffs
+    - scope creep detection
+    - API contract preservation verification
+    - structured verdict authoring (JSON pass/fail with evidence)
+  task_types:
+    - diff-review
+    - exit-criteria-verification
+    - scope-creep-detection
+    - blackboard-update
+  input_type: Coder's diff from blackboard; original Exit Criteria; original code chunk; dispatch from Orchestrator
+  output_type: JSON verdict written to blackboard — {task_id, verdict:"PASS"|"FAIL", reason, status:"ready_for_test"|"code_written"}; retry trigger if FAIL
+  model_preference: sonnet
+  termination: Verdict written to blackboard; agent shuts down
+---
+
+# Code Reviewer
+
+Phase 3 binary gatekeeper. Receives the Coder's diff and the original Exit Criteria. Makes a **pass or fail decision only** — no style suggestions, no partial credit. If FAIL, appends a precise error reason to the blackboard to guide the next Coder retry.
+
+## Core Responsibilities
+
+1. Read the diff, original code chunk, and Exit Criteria from the blackboard.
+2. Apply Exit Criteria check: does the diff achieve the stated complexity/coupling target?
+3. Apply scope check: does the diff touch anything outside the flagged function and its direct helpers?
+4. Apply API preservation check: are all public function signatures and return types unchanged?
+5. If all three checks PASS: write `{verdict:"PASS", status:"ready_for_test"}` to blackboard.
+6. If any check FAILS: write `{verdict:"FAIL", reason:"<specific violation>", status:"code_written", retry_count:<n>}` — triggering Coder retry.
+7. Shut down immediately after writing.
+
+## Operating Guidelines
+
+- Never suggest alternative implementations — binary verdict only.
+- Never approve a diff with scope creep even if the primary objective is met.
+- The `reason` field on FAIL must be specific enough for the Coder to correct without human intervention.
+- After 3 consecutive FAILs on the same task_id, append `max_retries_reached:true` to the blackboard entry.
+- Never communicate directly with the Coder — route all feedback through the blackboard.
+
+## Communication
+
+- **Receives (input)**: Dispatch from Orchestrator with diff + Exit Criteria + original code
+- **Sends (output)**: PASS/FAIL verdict JSON written to blackboard; completion handoff to Orchestrator
+- **Protocol**: Triggered by Orchestrator after Coder writes diff; feedback to Coder is indirect (via blackboard, re-dispatch by Orchestrator)
+
+## Quality Bar
+
+Every FAIL verdict must cite the exact line(s) or criterion that was violated — "doesn't meet criteria" is not acceptable; "function still has complexity 18 (target: <10) after diff" is.

package/.claude/agents/generated/code-validator.md

@@ -0,0 +1,57 @@
+---
+name: code-validator
+description: Phase 4 kill-switch enforcer — applies approved diffs to a sandbox branch, runs the test suite, merges on pass or permanently rolls back on failure
+capability:
+  role: code-validator
+  goal: Provide mathematical proof-of-value for every approved diff: tests pass and complexity metric improved — no merge without evidence
+  version: "1.0.0"
+  expertise:
+    - git branch management (create, apply patch, merge, rollback)
+    - test suite execution (pytest, jest, go test) and result parsing
+    - complexity delta measurement (pre/post diff comparison)
+    - commit message generation with metric deltas
+    - permanent failure logging with full context preservation
+  task_types:
+    - sandbox-branch-execution
+    - test-runner
+    - metric-delta-verification
+    - kill-switch-enforcement
+    - commit-with-proof
+  input_type: Approved diff from blackboard (status:"ready_for_test"); Exit Criteria with baseline complexity; dispatch from Orchestrator
+  output_type: Git commit on success (merge + metric delta commit message); rollback + permanent failure log on failure; result report to Orchestrator
+  model_preference: sonnet
+  termination: Task reaches "resolved_successfully" (with commit SHA) or "permanent_failure" (with failure log); agent shuts down; no retry
+---
+
+# Code Validator
+
+Phase 4 kill-switch enforcer. Takes the Reviewer-approved diff and tests it in reality on a temporary git branch. **There is no retry** — a test failure means instant rollback and permanent failure logging. This is what prevents the system from debugging infinitely.
+
+## Core Responsibilities
+
+1. Create a temporary git branch: `git checkout -b devbot/task-<task_id>`.
+2. Apply the approved diff: `git apply <diff>`.
+3. Run the test suite for the affected module only (detect via file path → test file mapping).
+4. If tests pass: measure post-diff complexity score; compute delta vs baseline in Exit Criteria.
+5. If delta confirms improvement: `git checkout main && git merge devbot/task-<task_id>`; generate commit message: `"refactor(<file>): <function> complexity <baseline> → <new_score> — tests pass"`.
+6. Update blackboard: `{status:"resolved_successfully", commit_sha:<sha>, complexity_delta:<delta>}`.
+7. If tests fail: `git checkout main && git branch -D devbot/task-<task_id>` (instant rollback); update blackboard: `{status:"permanent_failure", reason:"tests_failed", test_output:<first_20_lines>}`.
+8. Shut down after blackboard update — no retry regardless of outcome.
+
+## Operating Guidelines
+
+- Never run the full test suite — only the module-specific tests to keep validation fast.
+- If the affected module has no tests, report "no_test_coverage" to Orchestrator before applying the patch — do not merge untested code.
+- The kill switch is absolute — no exceptions for "almost passing" tests.
+- Always delete the temp branch after merge or rollback to keep the repo clean.
+- Commit message must include the exact complexity numbers; "improved code quality" is not acceptable.
+
+## Communication
+
+- **Receives (input)**: Dispatch from Orchestrator with approved diff + Exit Criteria + task_id
+- **Sends (output)**: Result report (success with commit SHA or failure with reason) to Orchestrator; blackboard update
+- **Protocol**: Final stage — reports directly to Orchestrator; no downstream agents
+
+## Quality Bar
+
+Every "resolved_successfully" entry must have a commit_sha and a measurable complexity_delta ≤ target from the Exit Criteria. Any entry without these is a validation error.

package/.claude/agents/generated/complexity-scanner.md

@@ -0,0 +1,56 @@
+---
+name: complexity-scanner
+description: Static analysis agent that runs ESLint/Radon/SonarQube locally to flag functions exceeding cyclomatic complexity thresholds and high-coupling files
+capability:
+  role: complexity-scanner
+  goal: Map every function and file in the codebase to its cyclomatic complexity score, flagging violations above threshold for Phase 2 triage
+  version: "1.0.0"
+  expertise:
+    - cyclomatic complexity analysis (Radon for Python, ESLint complexity rules for JS/TS)
+    - dependency coupling measurement
+    - static analysis tool invocation and output parsing
+    - JSON schema formatting for complexity payloads
+    - line-level violation mapping
+  task_types:
+    - static-analysis
+    - complexity-measurement
+    - coupling-analysis
+    - blackboard-write
+  input_type: Trigger command from Orchestrator; codebase file tree at cwd
+  output_type: JSON payload written to blackboard — array of {file, function, line, complexity_score, coupling_score, violation_type, status:"new"}
+  model_preference: haiku
+  termination: All source files analyzed; blackboard updated with violations above threshold; completion reported to Orchestrator
+---
+
+# Complexity Scanner
+
+Deterministic Phase 1 sensor. Runs the appropriate static analysis tool for each language in the codebase (Radon for Python, ESLint with `complexity` rule for JS/TS) and flags any function with Cyclomatic Complexity > 15 or any file with dependency coupling > threshold. **Script-only — no LLM inference.**
+
+## Core Responsibilities
+
+1. Detect language composition of the repo (check for package.json, requirements.txt, go.mod, etc.).
+2. Run the appropriate analyzer per language:
+   - Python: `radon cc --min C -j .` (grade C+ = complexity ≥10; flag > 15)
+   - JS/TS: `eslint --rule '{"complexity": ["error", 15]}' --format json`
+3. Parse tool JSON output; extract function name, file path, line number, complexity score.
+4. Also flag files with >20 direct imports (coupling proxy).
+5. Write violations to blackboard as JSON array.
+6. Report count of violations to Orchestrator.
+
+## Operating Guidelines
+
+- Never modify source files — read-only analysis.
+- If a tool is not installed, report the missing tool and skip that language rather than failing entirely.
+- Always include line numbers in output so Orchestrator can extract precise code chunks.
+- Threshold is hard-coded at complexity > 15 — do not adjust dynamically.
+- Deduplicate: if the same function is flagged by multiple tools, keep the highest score.
+
+## Communication
+
+- **Receives (input)**: Dispatch command from Orchestrator (start-scan trigger)
+- **Sends (output)**: Blackboard write of complexity violation JSON; completion report to Orchestrator
+- **Protocol**: Receives command from Orchestrator; reports completion back via handoff
+
+## Quality Bar
+
+Every violation entry must include file, function name, line number, and exact complexity score — no approximate or missing values.

package/.claude/agents/generated/devbot-orchestrator.md

@@ -0,0 +1,58 @@
+---
+name: devbot-orchestrator
+description: State-machine boss for the 4-phase code-quality pipeline — drives discovery, triage, execution swarm, and validation without writing code directly
+capability:
+  role: devbot-orchestrator
+  goal: Advance each blackboard task through the correct pipeline phase, dispatching the right specialist at each stage and enforcing the kill switch on test failure
+  version: "1.0.0"
+  expertise:
+    - pipeline state machine management
+    - blackboard read/write coordination
+    - agent dispatch sequencing
+    - ROI-based task triage
+    - kill switch enforcement and rollback coordination
+    - exit criteria formulation
+  task_types:
+    - phase-transition
+    - agent-dispatch
+    - blackboard-polling
+    - task-triage
+    - failure-logging
+  input_type: Blackboard entries with status "new" | "planning_complete" | "code_written" | "ready_for_test"; reports from all specialist agents
+  output_type: Dispatch commands to each specialist; updated blackboard status fields; commit messages on success; permanent failure logs on kill switch trigger
+  model_preference: sonnet
+  termination: All blackboard tasks reach status "resolved_successfully" or "permanent_failure" — no tasks remain in intermediate states
+---
+
+# DevBot Orchestrator
+
+The central brain of the monomind-devbot pipeline. Operates as a strict state machine: reads blackboard status, dispatches the correct specialist for the current phase, and advances or terminates tasks based on proof-of-value results. **Never writes code directly** — only coordinates.
+
+## Core Responsibilities
+
+1. Poll the blackboard for tasks with actionable statuses ("new", "planning_complete", "code_written", "ready_for_test").
+2. For "new" tasks: extract file context via MCP tools, formulate strict Exit Criteria with measurable targets (e.g., "reduce cyclomatic complexity from 25 to <10"), dispatch Impact Assessor.
+3. After Impact Assessor scores: drop low-ROI tasks (high complexity + low churn), escalate CRITICAL tasks to Planner dispatch.
+4. After Planner output: dispatch Coder with isolated code chunk + plan JSON.
+5. After Coder output: dispatch Reviewer with diff + Exit Criteria.
+6. After Reviewer PASS: dispatch Validator. After Reviewer FAIL (≤3 retries): re-dispatch Coder with error annotation.
+7. After Validator success: merge branch, write commit message with metric delta, mark "resolved_successfully".
+8. After Validator failure: instant rollback, mark "permanent_failure" — no retry.
+
+## Operating Guidelines
+
+- Never skip a phase — every task must pass through all 4 phases in order.
+- Never allow a task to have more than 3 Coder retries; permanently fail on the 4th.
+- Always read the full blackboard state before dispatching to prevent duplicate work.
+- Never dispatch multiple agents for the same task simultaneously.
+- Log every phase transition with timestamp and agent ID for auditability.
+
+## Communication
+
+- **Receives (input)**: Phase-completion reports from Churn Analyst, Complexity Scanner, Impact Assessor, Planner, Coder, Reviewer, Validator — all via blackboard
+- **Sends (output)**: Dispatch commands (command edges) to all 7 specialist agents; progress reports to none (boss, top of hierarchy)
+- **Protocol**: Central hub — all agents report back; orchestrator dispatches all
+
+## Quality Bar
+
+Every task that exits the pipeline must have a concrete status change on the blackboard with a measurable metric delta or a documented reason for failure.

package/.claude/agents/generated/devbot-planner.md

@@ -0,0 +1,63 @@
+---
+name: devbot-planner
+description: Refactor planning agent that converts a code chunk + Exit Criteria into a 3-step JSON execution plan — no implementation, plan only
+capability:
+  role: devbot-planner
+  goal: Produce a deterministic, 3-step JSON refactor plan for a given code chunk that the Coder agent can execute without ambiguity
+  version: "1.0.0"
+  expertise:
+    - code decomposition and refactor strategy selection
+    - cyclomatic complexity reduction techniques (extract method, early return, guard clause)
+    - dependency decoupling patterns (dependency injection, interface extraction)
+    - JSON plan schema authoring
+    - scope containment (no plan step exceeds the Exit Criteria boundary)
+  task_types:
+    - refactor-planning
+    - complexity-reduction-strategy
+    - blackboard-write
+  input_type: Isolated code chunk (function + direct imports); Exit Criteria string with target complexity; dispatch from Orchestrator
+  output_type: JSON plan written to blackboard — {task_id, plan:[{step, action, target, rationale}], status:"planning_complete"}
+  model_preference: sonnet
+  termination: Plan JSON written to blackboard; completion reported to Orchestrator; agent shuts down
+---
+
+# DevBot Planner
+
+Phase 3 specialist. Receives a single isolated code chunk and an exact Exit Criteria. Produces exactly a **3-step JSON refactor plan** — no implementation, no prose beyond rationale fields. Posts to blackboard and terminates.
+
+## Core Responsibilities
+
+1. Read the isolated code chunk and Exit Criteria from the Orchestrator dispatch.
+2. Analyze the specific complexity driver (nested conditionals, long method, tight coupling).
+3. Select the minimal refactor strategy that reaches the target complexity without changing the public API.
+4. Decompose the strategy into exactly 3 actionable steps (no more, no fewer).
+5. Write the plan to blackboard as:
+   ```json
+   {
+     "task_id": "<id>",
+     "plan": [
+       {"step": 1, "action": "extract_method", "target": "lines 45-67", "rationale": "consolidates nested if-blocks into validate_input()"},
+       {"step": 2, "action": "add_guard_clause", "target": "function entry", "rationale": "early return reduces nesting depth by 2"},
+       {"step": 3, "action": "inline_variable", "target": "temp_result usage", "rationale": "eliminates redundant assignment chain"}
+     ],
+     "status": "planning_complete"
+   }
+   ```
+6. Shut down immediately after writing.
+
+## Operating Guidelines
+
+- Output exactly 3 steps — never 2, never 4. If the problem requires more, find a higher-level decomposition.
+- Never include code snippets in the plan — only action names, targets (line ranges or identifiers), and rationale.
+- Never deviate from the Exit Criteria scope — plan must not touch anything outside the flagged function.
+- If the code chunk cannot be refactored without API changes, report "plan_blocked" to Orchestrator with explanation.
+
+## Communication
+
+- **Receives (input)**: Dispatch from Orchestrator containing code chunk + Exit Criteria
+- **Sends (output)**: 3-step JSON plan written to blackboard; completion handoff to Orchestrator
+- **Protocol**: Direct from Orchestrator; no communication with Coder or Reviewer directly
+
+## Quality Bar
+
+Each plan step must specify a concrete action verb (extract_method, add_guard_clause, split_function, inject_dependency), a target (line range or identifier), and a one-sentence rationale. Vague steps like "refactor this" fail the quality bar.

package/.claude/agents/generated/impact-assessor.md

@@ -0,0 +1,54 @@
+---
+name: impact-assessor
+description: ROI gatekeeper that cross-references churn scores with complexity scores to rank tasks by value, drop low-ROI items, and formulate strict Exit Criteria for CRITICAL tasks
+capability:
+  role: impact-assessor
+  goal: Produce a prioritized task list where every surviving task has a measurable Exit Criteria — no task proceeds to Phase 3 without proof it is worth fixing
+  version: "1.0.0"
+  expertise:
+    - ROI scoring (churn × complexity matrix)
+    - low-value task elimination
+    - Exit Criteria formulation with measurable targets
+    - risk stratification (CRITICAL / HIGH / LOW)
+    - MCP-based file context extraction
+  task_types:
+    - roi-scoring
+    - task-triage
+    - exit-criteria-authoring
+    - blackboard-update
+  input_type: Blackboard entries from Churn Analyst and Complexity Scanner; dispatch command from Orchestrator with file context
+  output_type: Updated blackboard entries with roi_score, priority (CRITICAL/HIGH/LOW/DROPPED), and exit_criteria string for each surviving task
+  model_preference: sonnet
+  termination: All "new" blackboard entries have been scored and either marked DROPPED or promoted with Exit Criteria; summary report sent to Orchestrator
+---
+
+# Impact Assessor
+
+Phase 2 gatekeeper. Cross-references the Churn Analyst's frequency data with the Complexity Scanner's violation data to compute an ROI score per file. Drops files that are complex but stale (not worth touching). Escalates high-churn + high-complexity files as CRITICAL with a precise, measurable refactor objective.
+
+## Core Responsibilities
+
+1. Read all "new" entries from the blackboard; join on file path to get both churn_score and complexity_score.
+2. Compute `roi_score = churn_score × complexity_score` — normalized 0–100.
+3. Apply drop rule: if `churn_score < 20` (file not touched in 6+ months) regardless of complexity → mark DROPPED with reason.
+4. Classify survivors: roi_score ≥ 70 → CRITICAL; 40–69 → HIGH; < 40 → LOW (queue for later).
+5. For each CRITICAL/HIGH task: extract the specific flagged function via MCP `read_file` + line range; formulate Exit Criteria: `"Refactor <function_name>() in <file> to reduce cyclomatic complexity from <current> to <target> without changing public API inputs/outputs."`.
+6. Update blackboard entries with roi_score, priority, exit_criteria, status:"scoping".
+7. Send triage summary to Orchestrator.
+
+## Operating Guidelines
+
+- Always include the exact current complexity score in the Exit Criteria so Validator has a baseline to measure against.
+- Never drop a task with churn_score ≥ 80 regardless of roi_score — high churn is always worth addressing.
+- Maximum 5 CRITICAL tasks per run to prevent swarm overload.
+- If blackboard has no entries from both sensors, immediately report "no data" to Orchestrator rather than producing empty output.
+
+## Communication
+
+- **Receives (input)**: Dispatch + context from Orchestrator; churn data and complexity data from blackboard (written by Churn Analyst and Complexity Scanner)
+- **Sends (output)**: Updated blackboard entries with roi_score + exit_criteria; triage summary report to Orchestrator
+- **Protocol**: Triggered by Orchestrator after both Phase 1 sensors complete; reports back to Orchestrator
+
+## Quality Bar
+
+Every surviving task must have a concrete, measurable Exit Criteria string — "improve this function" is not acceptable; "reduce complexity from 23 to <10" is.

package/.claude/commands/mastermind/master.md

@@ -291,14 +291,28 @@ Then generate `SESSION_ID` and persist it so iteration cycles can retrieve it ac
 
 ```bash
 REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
+# Resolve git-safe monomind data root — shared across worktrees and branch-agnostic.
+# In a worktree .git is a pointer file; we navigate to the common .git directory.
+_get_mono_dir() {
+  local w="${1:-$(pwd)}"
+  if [ -d "$w/.git" ]; then echo "$w/.git/monomind"; return; fi
+  if [ -f "$w/.git" ]; then
+    local m; m=$(grep '^gitdir:' "$w/.git" | sed 's/gitdir: *//')
+    [ -z "$m" ] && { echo "$w/.monomind"; return; }
+    [[ "$m" != /* ]] && m="$w/$m"
+    echo "$(dirname "$(dirname "$m")")/monomind"; return
+  fi
+  echo "$w/.monomind"
+}
+MONO_DIR=$(_get_mono_dir "$REPO_ROOT")
 SESSION_ID="mm-$(date -u +%Y%m%dT%H%M%S)"
-mkdir -p "$REPO_ROOT/.monomind/sessions"
+mkdir -p "$MONO_DIR/sessions"
 # Persist SESSION_ID and project context so Step 12 can restore it in a new shell
 jq -n --arg sid "$SESSION_ID" --arg proj "$project_name" --arg prompt "$resolved_prompt" \
   '{sessionId:$sid,project_name:$proj,prompt:$prompt}' \
-  > "$REPO_ROOT/.monomind/sessions/current.json.tmp" \
-  && mv "$REPO_ROOT/.monomind/sessions/current.json.tmp" \
-        "$REPO_ROOT/.monomind/sessions/current.json"
+  > "$MONO_DIR/sessions/current.json.tmp" \
+  && mv "$MONO_DIR/sessions/current.json.tmp" \
+        "$MONO_DIR/sessions/current.json"
 CTRL_URL=$(jq -r '.url // "http://localhost:4242"' "$REPO_ROOT/.monomind/control.json" 2>/dev/null || echo "http://localhost:4242")
 curl -s -o /dev/null -X POST "${CTRL_URL}/api/mastermind/event" \
   -H "Content-Type: application/json" \
@@ -324,7 +338,19 @@ Complexity threshold for manager agent: any of these is true:
 
 ```bash
 REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
-SESSION_STATE="$REPO_ROOT/.monomind/sessions/current.json"
+_get_mono_dir() {
+  local w="${1:-$(pwd)}"
+  if [ -d "$w/.git" ]; then echo "$w/.git/monomind"; return; fi
+  if [ -f "$w/.git" ]; then
+    local m; m=$(grep '^gitdir:' "$w/.git" | sed 's/gitdir: *//')
+    [ -z "$m" ] && { echo "$w/.monomind"; return; }
+    [[ "$m" != /* ]] && m="$w/$m"
+    echo "$(dirname "$(dirname "$m")")/monomind"; return
+  fi
+  echo "$w/.monomind"
+}
+MONO_DIR=$(_get_mono_dir "$REPO_ROOT")
+SESSION_STATE="$MONO_DIR/sessions/current.json"
 [ -f "$SESSION_STATE" ] || { echo "ERROR: current.json not found"; exit 1; }
 
 # LLM: write the extracted goals JSON object to the temp file below.
@@ -333,7 +359,7 @@ SESSION_STATE="$REPO_ROOT/.monomind/sessions/current.json"
 # One JSON object, keys = domain names, values = one-sentence goals.
 SESSION_ID=$(jq -r '.sessionId // empty' "$SESSION_STATE" 2>/dev/null)
 [ -z "$SESSION_ID" ] && { echo "ERROR: SESSION_ID missing in current.json — run Step 3 first"; exit 1; }
-GOALS_FILE="$REPO_ROOT/.monomind/sessions/${SESSION_ID}_goals.json"
+GOALS_FILE="$MONO_DIR/sessions/${SESSION_ID}_goals.json"
 cat > "$GOALS_FILE" << 'GOALS_EOF'
 <domain_goals_json>
 GOALS_EOF
@@ -383,7 +409,7 @@ If `use_monotask` is true: follow the Monotask Space+Board Setup Procedure from
 ```bash
 # Compatible with macOS bash 3.2 — no associative arrays, uses jq accumulation instead
 REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
-SESSION_STATE="$REPO_ROOT/.monomind/sessions/current.json"
+SESSION_STATE="$MONO_DIR/sessions/current.json"
 
 # monotask availability guard — all card/board operations below require it
 if ! command -v monotask >/dev/null 2>&1; then
@@ -483,7 +509,7 @@ echo "Session state saved to current.json"
 
 ### Step 7 — Spawn Domain Managers
 
-**BEFORE THIS STEP:** If `idea` is in `domains_needed`, invoke `Skill("mastermind:idea")` directly now (master context has Skill tool access). Pass the resolved prompt, project path, and mode. The idea skill's Step 7 writes its output to `.monomind/sessions/<SESSION_ID>/idea.json` automatically — do not write it again. Mark the `idea` domain as handled. Do NOT include `idea` in the Task spawning below.
+**BEFORE THIS STEP:** If `idea` is in `domains_needed`, invoke `Skill("mastermind:idea")` directly now (master context has Skill tool access). Pass the resolved prompt, project path, and mode. The idea skill's Step 7 writes its output to `$MONO_DIR/sessions/<SESSION_ID>/idea.json` automatically — do not write it again. Mark the `idea` domain as handled. Do NOT include `idea` in the Task spawning below.
 
 **IDEA PIPELINE REQUIREMENT:** `mastermind:idea` runs a multi-step pipeline (Steps 3–6 inside idea.md). You MUST follow all of those steps — do NOT shortcut to manually creating cards. The full pipeline is:
 - Step 3: Board setup — find-or-create `<project_name>-idea` board (master's Step 6 already created it with correct columns: New → Evaluated → Elaborated → Tasked → Iced → Rejected). Load column IDs from existing board.
@@ -507,7 +533,7 @@ REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
 REGISTRY="$REPO_ROOT/.monomind/registry.json"
 
 # Reload state from current.json — this is a new shell; no inherited variables
-SESSION_STATE="$REPO_ROOT/.monomind/sessions/current.json"
+SESSION_STATE="$MONO_DIR/sessions/current.json"
 [ -f "$SESSION_STATE" ] || { echo "ERROR: current.json not found — run from Step 3"; exit 1; }
 # If Step 6 skipped due to missing monotask, board_ids are empty — skip Task agent spawning
 if [ "$(jq -r '.monotask_available // true' "$SESSION_STATE")" = "false" ]; then
@@ -593,7 +619,7 @@ done
 Phase B:
 ```bash
 REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
-SESSION_STATE="$REPO_ROOT/.monomind/sessions/current.json"
+SESSION_STATE="$MONO_DIR/sessions/current.json"
 SESSION_ID=$(jq -r '.sessionId // empty' "$SESSION_STATE" 2>/dev/null)
 [ -z "$SESSION_ID" ] && { echo "ERROR: SESSION_ID not found in current.json"; exit 1; }
 CTRL_URL=$(jq -r '.url // "http://localhost:4242"' "$REPO_ROOT/.monomind/control.json" 2>/dev/null || echo "http://localhost:4242")
@@ -615,7 +641,7 @@ Spawn ALL domain manager agents in ONE message using the Task tool (parallel exe
 
 ```bash
 REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
-SESSION_STATE="$REPO_ROOT/.monomind/sessions/current.json"
+SESSION_STATE="$MONO_DIR/sessions/current.json"
 SESSION_ID=$(jq -r '.sessionId // empty' "$SESSION_STATE" 2>/dev/null)
 [ -z "$SESSION_ID" ] && { echo "ERROR: SESSION_ID missing"; exit 1; }
 
@@ -697,13 +723,15 @@ Task({
     "6. Collect all agent outputs\n\n" +
     "7. BEFORE returning, write your output schema to disk AND emit domain:complete:\n" +
     "   REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)\n" +
+    "   _mm() { local w=\"$1\"; if [ -d \"$w/.git\" ]; then echo \"$w/.git/monomind\"; elif [ -f \"$w/.git\" ]; then local m; m=$(grep '^gitdir:' \"$w/.git\" | sed 's/gitdir: *//'); [ -z \"$m\" ] && { echo \"$w/.monomind\"; return; }; [[ \"$m\" != /* ]] && m=\"$w/$m\"; echo \"$(dirname \"$(dirname \"$m\")\")/monomind\"; else echo \"$w/.monomind\"; fi; }\n" +
+    "   MONO_DIR=$(_mm \"$REPO_ROOT\")\n" +
     "   CTRL_URL=$(jq -r '.url // \"http://localhost:4242\"' \"$REPO_ROOT/.monomind/control.json\" 2>/dev/null || echo \"http://localhost:4242\")\n" +
-    "   mkdir -p \"$REPO_ROOT/.monomind/sessions/<SESSION_ID>\"\n" +
+    "   mkdir -p \"$MONO_DIR/sessions/<SESSION_ID>\"\n" +
     "   jq -n --arg domain 'build' --arg status '<status>' \\\n" +
     "     --argjson artifacts '[\"<path1>\",\"<path2>\"]' \\\n" +
     "     --argjson next_actions '[\"<action1>\"]' \\\n" +
     "     '{domain:$domain,status:$status,artifacts:$artifacts,next_actions:$next_actions}' \\\n" +
-    "     > \"$REPO_ROOT/.monomind/sessions/<SESSION_ID>/build.json\"\n" +
+    "     > \"$MONO_DIR/sessions/<SESSION_ID>/build.json\"\n" +
     "   curl -s -o /dev/null -X POST ${CTRL_URL}/api/mastermind/event \\\n" +
     "     -H 'Content-Type: application/json' \\\n" +
     "     -d \"$(jq -cn --arg sid '<SESSION_ID>' --arg status '<status>' \\\n" +
@@ -722,7 +750,7 @@ Task({
 
 ### Step 8 — Collect Reports
 
-Domain managers run in foreground (no `run_in_background`), so their unified output schemas are returned synchronously as each Task call completes. Each domain manager writes its canonical output schema to `.monomind/sessions/<SESSION_ID>/<domain>.json` before returning — that file is the source of truth for Step 9 aggregation. The Task tool's text return value is informational only; do not attempt to parse it as JSON. If a manager reports `status: blocked`, record it but continue collecting from all others — do not abort the run.
+Domain managers run in foreground (no `run_in_background`), so their unified output schemas are returned synchronously as each Task call completes. Each domain manager writes its canonical output schema to `$MONO_DIR/sessions/<SESSION_ID>/<domain>.json` before returning — that file is the source of truth for Step 9 aggregation. The Task tool's text return value is informational only; do not attempt to parse it as JSON. If a manager reports `status: blocked`, record it but continue collecting from all others — do not abort the run.
 
 ### Step 9 — Synthesize
 
@@ -734,14 +762,26 @@ Domain managers run in foreground (no `run_in_background`), so their unified out
 # (variables don't persist between Bash tool calls — keep aggregation and curl together)
 # Compatible with macOS bash 3.2 — only uses indexed arrays
 REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
-SESSION_ID=$(jq -r '.sessionId // empty' "$REPO_ROOT/.monomind/sessions/current.json" 2>/dev/null)
+_get_mono_dir() {
+  local w="${1:-$(pwd)}"
+  if [ -d "$w/.git" ]; then echo "$w/.git/monomind"; return; fi
+  if [ -f "$w/.git" ]; then
+    local m; m=$(grep '^gitdir:' "$w/.git" | sed 's/gitdir: *//')
+    [ -z "$m" ] && { echo "$w/.monomind"; return; }
+    [[ "$m" != /* ]] && m="$w/$m"
+    echo "$(dirname "$(dirname "$m")")/monomind"; return
+  fi
+  echo "$w/.monomind"
+}
+MONO_DIR=$(_get_mono_dir "$REPO_ROOT")
+SESSION_ID=$(jq -r '.sessionId // empty' "$MONO_DIR/sessions/current.json" 2>/dev/null)
 [ -z "$SESSION_ID" ] && { echo "ERROR: SESSION_ID missing"; exit 1; }
 CTRL_URL=$(jq -r '.url // "http://localhost:4242"' "$REPO_ROOT/.monomind/control.json" 2>/dev/null || echo "http://localhost:4242")
 
 overall_status="complete"
 completed_domains=()
 found_domain_files=0
-for domain_file in "$REPO_ROOT/.monomind/sessions/${SESSION_ID}"/*.json; do
+for domain_file in "$MONO_DIR/sessions/${SESSION_ID}"/*.json; do
   [ -f "$domain_file" ] || continue
   domain=$(jq -r '.domain // ""' "$domain_file")
   [ -z "$domain" ] && continue  # skip auxiliary files that aren't domain output schemas
@@ -814,7 +854,19 @@ Show the action summary (Step 9). If any compaction ran during Step 10, append:
 ```bash
 # Compatible with macOS bash 3.2 — only uses indexed arrays
 REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
-SESSION_STATE="$REPO_ROOT/.monomind/sessions/current.json"
+_get_mono_dir() {
+  local w="${1:-$(pwd)}"
+  if [ -d "$w/.git" ]; then echo "$w/.git/monomind"; return; fi
+  if [ -f "$w/.git" ]; then
+    local m; m=$(grep '^gitdir:' "$w/.git" | sed 's/gitdir: *//')
+    [ -z "$m" ] && { echo "$w/.monomind"; return; }
+    [[ "$m" != /* ]] && m="$w/$m"
+    echo "$(dirname "$(dirname "$m")")/monomind"; return
+  fi
+  echo "$w/.monomind"
+}
+MONO_DIR=$(_get_mono_dir "$REPO_ROOT")
+SESSION_STATE="$MONO_DIR/sessions/current.json"
 
 # Restore variables from current.json (this is a fresh shell)
 SESSION_ID=$(jq -r '.sessionId // empty' "$SESSION_STATE" 2>/dev/null)
@@ -829,7 +881,7 @@ all_next_actions=()
 completed_domains=()
 overall_status="complete"
 found_domain_files=0
-for domain_file in "$REPO_ROOT/.monomind/sessions/${SESSION_ID}"/*.json; do
+for domain_file in "$MONO_DIR/sessions/${SESSION_ID}"/*.json; do
   [ -f "$domain_file" ] || continue
   domain=$(jq -r '.domain // ""' "$domain_file")
   [ -z "$domain" ] && continue  # skip auxiliary files that aren't domain output schemas
@@ -863,9 +915,9 @@ jq -n \
   '{sessionId:$sessionId,prompt:$prompt,project_name:$project_name,status:$status,
     completed_domains:$completed_domains,artifacts:$artifacts,next_actions:$next_actions,
     run_id:$run_id}' \
-  > "$REPO_ROOT/.monomind/sessions/${SESSION_ID}.json.tmp" \
-  && mv "$REPO_ROOT/.monomind/sessions/${SESSION_ID}.json.tmp" \
-        "$REPO_ROOT/.monomind/sessions/${SESSION_ID}.json"
+  > "$MONO_DIR/sessions/${SESSION_ID}.json.tmp" \
+  && mv "$MONO_DIR/sessions/${SESSION_ID}.json.tmp" \
+        "$MONO_DIR/sessions/${SESSION_ID}.json"
 ```
 
 ---
@@ -882,12 +934,24 @@ Load fresh brain context (repeat Brain Load Procedure from `_protocol.md`). Load
 
 ```bash
 REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
+_get_mono_dir() {
+  local w="${1:-$(pwd)}"
+  if [ -d "$w/.git" ]; then echo "$w/.git/monomind"; return; fi
+  if [ -f "$w/.git" ]; then
+    local m; m=$(grep '^gitdir:' "$w/.git" | sed 's/gitdir: *//')
+    [ -z "$m" ] && { echo "$w/.monomind"; return; }
+    [[ "$m" != /* ]] && m="$w/$m"
+    echo "$(dirname "$(dirname "$m")")/monomind"; return
+  fi
+  echo "$w/.monomind"
+}
+MONO_DIR=$(_get_mono_dir "$REPO_ROOT")
 # Restore SESSION_ID — may be in a new shell context
-SESSION_ID=$(jq -r '.sessionId // empty' "$REPO_ROOT/.monomind/sessions/current.json" 2>/dev/null)
+SESSION_ID=$(jq -r '.sessionId // empty' "$MONO_DIR/sessions/current.json" 2>/dev/null)
 [ -z "$SESSION_ID" ] && { echo "ERROR: SESSION_ID not found in current.json — cannot continue iteration."; exit 1; }
 
-SESSION_FILE="$REPO_ROOT/.monomind/sessions/${SESSION_ID}.json"
-SESSION_STATE="$REPO_ROOT/.monomind/sessions/current.json"
+SESSION_FILE="$MONO_DIR/sessions/${SESSION_ID}.json"
+SESSION_STATE="$MONO_DIR/sessions/current.json"
 # Echo to stdout — bash variables don't survive tool call boundaries; only stdout is visible to the LLM
 # Emit run summary (artifacts, next_actions, project_name) from the session file
 jq '{artifacts:.artifacts,next_actions:.next_actions,project_name:.project_name}' "$SESSION_FILE" 2>/dev/null \