monomind 2.7.12 → 2.7.14

package/packages/@monomind/cli/.claude/commands/mastermind/code-review.md

@@ -1,314 +0,0 @@
-<!-- "Monomind — Multi-agent iterative review loop: runs Code Reviewer, Security Engineer, and domain specialists in parallel, auto-fixes findings each iteration, and captures human-in-loop items to a dated file." -->
-
-**First — extract repeat flags:** Follow the REPEAT PREAMBLE from `mastermind-repeat/SKILL.md`. Extracts `--repeat`, `--tillend`, `--maxruns`, `--wait`, `--rep`, `--loop` from `$ARGUMENTS` before all other parsing. If `is_continuation = true`, skip the empty-arguments check below.
-
-Parse remaining `$ARGUMENTS` as `TOTAL_ITERATIONS` (integer, min 1, max 10).
-
-If `$ARGUMENTS` is empty, not a positive integer, or greater than 10, output this and STOP:
-
-> **Usage:** `/mastermind:code-review <iterations>`
->
-> Examples:
-> - `/mastermind:code-review 1` — single review pass
-> - `/mastermind:code-review 3` — three fix-and-re-review cycles
->
-> Runs parallel review agents each iteration, auto-fixes what can be fixed, and saves items requiring human judgment to `humaninloopreview-YYYY-MM-DD.md`.
-
-Do NOT proceed further if no valid number was provided.
-
----
-
-## Terminology
-
-- **Finding**: An issue reported by any review agent.
-- **Auto-fixable**: Claude can apply the fix without ambiguity and without changing intended behavior.
-- **Human-in-loop (HIL)**: Requires a product/design/architecture decision, a credential, a policy choice, or something Claude cannot safely assume. These are written to the HIL file and skipped.
-- **HIL file**: `humaninloopreview-<YYYY-MM-DD>.md` in the project root. Appended each loop; never overwritten.
-
----
-
-## Step 0: Setup
-
-Parse `$ARGUMENTS` as `TOTAL_ITERATIONS` (integer, min 1, max 10).
-
-Collect the following in parallel:
-
-1. **Git context**: Run the following to get recently changed files. Store result as `CHANGED_FILES`.
-   ```bash
-   CHANGED_FILES=$(git diff --name-only HEAD~1 HEAD 2>/dev/null)
-   [ -z "$CHANGED_FILES" ] && CHANGED_FILES=$(git ls-files -m 2>/dev/null)
-   [ -z "$CHANGED_FILES" ] && CHANGED_FILES=$(git diff --name-only HEAD~5 HEAD 2>/dev/null)
-   ```
-2. **Repo structure**: Run `git ls-files | head -80` to get a representative file list. Store as `FILE_LIST`.
-3. **Branch info**: Run `git log --oneline -5` to get recent commit context. Store as `RECENT_COMMITS`.
-4. **Stack detection**: Run `ls package.json pyproject.toml go.mod Cargo.toml 2>/dev/null; find . -maxdepth 3 \( -name "*.swift" -o -name "*.kt" \) | head -3` to detect language/framework. Store detected stacks as `STACK`.
-5. **HIL file path**: Compute `HIL_FILE=humaninloopreview-$(date +%Y-%m-%d).md` in the project root.
-
-Initialize tracking state:
-```
-ITERATION = 1
-ITERATIONS_RUN = 0       # how many iterations actually executed (for final report)
-ALL_FIXED = []           # auto-fixed items (across all iterations)
-ALL_HIL = []             # human-in-loop items (across all iterations)
-HIL_COUNT = 0            # global counter for HIL-N labels
-PENDING_FIXED = []       # staging: auto-fixed this batch, not yet verified
-ITERATION_FIXED_FILES = []  # file paths edited this iteration
-```
-
----
-
-## Step 1: Select Review Agents for This Stack
-
-Based on `STACK`, determine which specialist agents to run beyond the always-on core set.
-
-**Always run (every stack):**
-- `Code Reviewer` — correctness, maintainability, performance, naming, dead code
-- `Security Engineer` — injection, auth gaps, secrets exposure, CVE-prone patterns, OWASP Top 10
-- `Reality Checker` — evidence-based assessment: does the code actually do what it claims?
-
-**Run conditionally** — use `monograph_query` first to detect stack; fall back to find/grep if monograph returns 0 results:
-- `Accessibility Auditor` — `monograph_query({ query: "html jsx tsx component" })` or `find . -maxdepth 5 \( -name "*.html" -o -name "*.jsx" -o -name "*.tsx" \) -not -path "*/node_modules/*" | head -1 | grep -q .`
-- `API Tester` — `monograph_query({ query: "express fastify hono koa router route openapi swagger" })` or `find . -maxdepth 5 \( -name "*.route.*" -o -name "openapi.yml" -o -name "openapi.json" -o -name "swagger.*" \) -not -path "*/node_modules/*" | head -1 | grep -q . || grep -rqEl "express\(|fastify|hono|koa|router\." --include="*.ts" --include="*.js" . 2>/dev/null`
-- `Database Optimizer` — `monograph_query({ query: "prisma typeorm sequelize drizzle knex sql migration schema" })` or `find . -maxdepth 5 \( -name "*.sql" -o -name "*migration*" -o -name "*schema*" \) -not -path "*/node_modules/*" | head -1 | grep -q . || grep -rqEl "prisma|typeorm|sequelize|drizzle|knex" --include="*.ts" --include="*.js" . 2>/dev/null`
-- `SRE` — `find . -maxdepth 3 \( -name "Dockerfile" -o -name "docker-compose*" -o -name "*.yml" -path "*/.github/workflows/*" \) | head -1 | grep -q .`
-- `Mobile App Builder` — `find . -maxdepth 3 \( -name "*.swift" -o -name "*.kt" \) | head -1 | grep -q . || grep -q "react-native" package.json 2>/dev/null`
-
-Store the selected set as `ACTIVE_REVIEWERS`.
-
----
-
-## Loop: Run `TOTAL_ITERATIONS` times
-
-For each iteration, first reset per-iteration state:
-```
-PENDING_FIXED = []
-ITERATION_FIXED_FILES = []
-```
-
----
-
-### Step 2: Run All Reviewers in Parallel
-
-Spawn one agent per reviewer in `ACTIVE_REVIEWERS` using the `Task` tool — all in a **single message** so they run concurrently.
-
-Each agent receives:
-- `CHANGED_FILES`, `FILE_LIST`, `RECENT_COMMITS`, `STACK`
-- The list of findings already auto-fixed in prior iterations (so they don't re-report them)
-- The list of HIL items already deferred (same reason)
-- Their specific review focus (below)
-
-#### Agent Instructions by Role
-
-All agent prompts share this finding schema. `hil_reason` and `context` are only required when `auto_fixable: false`:
-```
-{
-  file, line,
-  severity: critical|high|medium|low,
-  category: "...",
-  description,
-  suggested_fix,
-  auto_fixable: true|false,
-  hil_reason?: "only if auto_fixable=false — why Claude cannot safely apply this",
-  context?: "only if auto_fixable=false — 2-4 sentences: what the code does, why this is a problem, what the risk is"
-}
-```
-
-**Code Reviewer prompt:**
-> Review the codebase for: logic errors, off-by-one bugs, null/undefined handling, dead code, overly complex functions (>50 lines or >3 nesting levels), naming inconsistencies, missing error propagation, and performance anti-patterns (N+1, blocking I/O, unnecessary allocations). Focus on `CHANGED_FILES` first, then related files. Return findings using the shared schema above.
-
-**Security Engineer prompt:**
-> Audit for: hardcoded secrets or API keys, SQL/command/path injection, missing input validation at system boundaries, insecure deserialization, broken auth/authz, sensitive data in logs, unpatched dependency versions with known CVEs, missing rate limiting on public endpoints, and CORS misconfigurations. Categories: injection|secrets|auth|deps|logging|config. Return findings using the shared schema above.
-
-**Reality Checker prompt:**
-> Check: does each function do what its name/docs claim? Are there missing test assertions? Are there commented-out code blocks, TODO/FIXME/HACK markers, or debug statements left in? Are there import cycles? Are env vars assumed to exist without validation? Categories: correctness|tests|debt|env. Return findings using the shared schema above.
-
-**Accessibility Auditor prompt (if applicable):**
-> Check: missing alt text, non-semantic HTML, keyboard-inaccessible interactive elements, insufficient color contrast (< 4.5:1 for text), missing ARIA labels, focus trap issues, and missing skip navigation. Category: a11y. Return findings using the shared schema above.
-
-**API Tester prompt (if applicable):**
-> Check: endpoints missing auth middleware, routes with no input validation, missing HTTP status codes on error paths, inconsistent response shapes, pagination not implemented where expected, and missing rate-limit headers. Category: api. Return findings using the shared schema above.
-
-**Database Optimizer prompt (if applicable):**
-> Check: missing indexes on foreign keys and frequently-queried columns, N+1 query patterns in ORM code, unparameterized queries, missing transactions around multi-step writes, and schema column type mismatches. Category: database. Return findings using the shared schema above.
-
-**SRE prompt (if applicable):**
-> Check: Docker images without pinned versions, CI jobs with no timeout, missing health check endpoints, hardcoded environment assumptions (localhost, fixed ports), missing retry logic on external calls, and secrets in CI config files. Categories: reliability|infra. Return findings using the shared schema above.
-
-**Mobile App Builder prompt (if applicable):**
-> Check: missing permission explanations, sensitive data stored in plain UserDefaults/SharedPreferences, missing loading/error states, hard-coded URLs, deprecated API usage, and missing offline/degraded-mode handling. Category: mobile. Return findings using the shared schema above.
-
----
-
-### Step 3: Merge and Deduplicate Findings
-
-Collect all agent outputs. As you collect each agent's findings, annotate each finding with `reporter: <agent role name>` (e.g., `"Code Reviewer"`, `"Security Engineer"`, `"Reality Checker"`). Merge into a single `ITERATION_FINDINGS` list. Deduplicate by `(file, category, description[:60])` — keep highest severity when duplicates exist. Do NOT deduplicate by line number, as applied fixes shift line numbers across iterations. Exclude anything already in `ALL_FIXED` or `ALL_HIL` by matching on `(file, description[:60])`.
-
-Sort by severity: critical → high → medium → low.
-
----
-
-### Step 4: Classify and Act
-
-For each finding in `ITERATION_FINDINGS`:
-
-**If `auto_fixable: true`:**
-- Apply the fix using `Edit` (or `Write` for new files). Add the file path to `ITERATION_FIXED_FILES` list. Add the finding to a staging list `PENDING_FIXED`.
-
-**If `auto_fixable: false` (HIL):**
-- Add to `ALL_HIL`. Do NOT attempt to fix.
-
-After processing all findings, if `PENDING_FIXED` is empty, skip verification and proceed to Step 5. Otherwise, run verification **once** for the whole batch. Run only commands appropriate for `STACK`:
-
-**Node.js / TypeScript:**
-```bash
-npm run --if-present lint 2>&1 | tail -5
-npm run --if-present typecheck 2>&1 | tail -5
-npm run --if-present test 2>&1 | tail -10
-```
-
-**Python** (if `pyproject.toml` or `*.py` detected):
-```bash
-ruff check . 2>&1 | tail -5
-python -m pytest --tb=short -q 2>&1 | tail -10
-```
-
-**Go** (if `go.mod` detected):
-```bash
-go vet ./... 2>&1 | tail -5
-go test ./... 2>&1 | tail -10
-```
-
-**Rust** (if `Cargo.toml` detected):
-```bash
-cargo check 2>&1 | tail -5
-cargo test 2>&1 | tail -10
-```
-- If all checks pass: move all `PENDING_FIXED` entries into `ALL_FIXED`.
-- If any check fails: run `git restore` on each file in `ITERATION_FIXED_FILES` to undo all changes, move all `PENDING_FIXED` entries to `ALL_HIL` with `hil_reason: "batch auto-fix caused verification failure — apply individually"`. Print the error output.
-
----
-
-### Step 5: Commit Fixes for This Iteration
-
-If `ALL_FIXED` gained any new entries this iteration:
-
-Stage only the files that were actually edited (tracked from `ITERATION_FIXED_FILES` collected in Step 4):
-```bash
-git add <space-separated list of ITERATION_FIXED_FILES paths>
-```
-
-Then commit with each fixed item on its own line in the body:
-```bash
-git commit -m "fix(review): iteration <ITERATION> — <count> findings fixed by mastermind:code-review
-
-<file>:<line> — <description>
-<file>:<line> — <description>
-
-Co-Authored-By: nokhodian <nokhodian@gmail.com>"
-```
-
----
-
-### Step 6: Write HIL Items to File
-
-If any new HIL items were added this iteration, **append** to `HIL_FILE`. For each new HIL item, increment `HIL_COUNT` by 1 and use it as the label number:
-
-```markdown
-## Review Iteration <ITERATION> — <YYYY-MM-DD HH:MM>
-
-<!-- One block per HIL finding; HIL_COUNT increments globally across all iterations -->
-### HIL-<HIL_COUNT>: <description> [`<severity>`]
-
-**File:** `<file>:<line>`
-**Category:** <category>
-**Reported by:** <agent name>
-
-**Context:**
-<context from agent finding, or derive from description if context field absent>
-
-**Suggested fix:**
-<suggested_fix from agent, verbatim>
-
-**Why human decision needed:**
-<hil_reason>
-
-**Your options:**
-- [ ] Apply the suggested fix as-is
-- [ ] Apply a modified fix (describe below)
-- [ ] Defer — not a priority right now
-- [ ] Reject — not applicable for this project
-
-**Your response (fill in and save):**
-> 
-
----
-```
-
-After writing, print:
-> `HIL_FILE` updated with <count> new items requiring human judgment.
-
----
-
-### Step 7: Iteration Summary
-
-Increment `ITERATIONS_RUN` by 1. Then print a table:
-
-```
-### Iteration <ITERATION> / <TOTAL_ITERATIONS>
-
-| Reviewer            | Findings | Auto-Fixed | HIL |
-|---------------------|----------|------------|-----|
-| Code Reviewer       | N        | N          | N   |
-| Security Engineer   | N        | N          | N   |
-| Reality Checker     | N        | N          | N   |
-| ...                 | ...      | ...        | ... |
-| **Total**           | **N**    | **N**      | **N**|
-
-Severity breakdown: X critical, Y high, Z medium, W low
-```
-
-If zero findings remain after dedup and exclusions, print:
-> No new findings. Review complete.
-> Break out of the loop early.
-
-Increment `ITERATION`. Continue to next iteration.
-
----
-
-## Step 8: Final Report
-
-After all iterations complete (or early exit), output:
-
-```markdown
-## mastermind:code-review — Complete
-
-**Iterations run:** <ITERATIONS_RUN> / <TOTAL_ITERATIONS>
-**Reviewers active:** <list>
-
-### Auto-Fixed (<N> total)
-| File | Line | Severity | Category | Description |
-|------|------|----------|----------|-------------|
-| ... | ... | ... | ... | ... |
-
-### Human-in-Loop (<N> items)
-Saved to: `humaninloopreview-<date>.md`
-
-| # | File | Severity | Category | Why HIL |
-|---|------|----------|----------|---------|
-| 1 | ... | ... | ... | ... |
-
-### How to resolve HIL items
-1. Open `humaninloopreview-<date>.md`
-2. For each item, fill in **Your response** and check the option box
-3. Apply your chosen fixes manually, or run `/mastermind:code-review 1` again after fixing to re-verify
-
-### Commits created
-<list of commit SHAs and messages from this session>
-```
-
-If `ALL_HIL` is empty, omit the HIL section and congratulate:
-> All findings were auto-fixed. No human decisions required.
-
-To repeat this command on a schedule, wrap it with `/mastermind:repeat` or use `--repeat N` / `--tillend` directly.
-
-**MANDATORY — invoke `Skill("mastermind-repeat")` now.** This is required regardless of how the skill above completed, regardless of whether you think the work is done, regardless of whether you plan to end your response. For `--repeat N`: the count is non-negotiable — all N runs must happen. For `--tillend`: only a verified empty round (confirmed by git diff) stops the loop. Do not end your response without invoking this skill.

package/packages/@monomind/cli/.claude/commands/mastermind/content.md

@@ -1,23 +0,0 @@
-<!-- Mastermind content domain — blog posts, threads, docs, newsletters. Default mode: confirm. -->
-
-**First — extract repeat flags:** Follow the REPEAT PREAMBLE from `mastermind-repeat/SKILL.md`. Extracts `--repeat`, `--tillend`, `--maxruns`, `--wait`, `--rep`, `--loop` from `$ARGUMENTS` before all other parsing. If `is_continuation = true`, skip the empty-prompt check and intake below.
-
-Parse `$ARGUMENTS` for:
-- `--auto` flag → mode = auto
-- `--confirm` flag → mode = confirm
-- `--project <name>` → project_name = <name>
-- Remaining text = prompt
-
-If prompt is empty: ask "What content would you like created?"
-
-Load brain context for the `content` domain (follow mastermind-protocol/SKILL.md Brain Load Procedure).
-
-Run intake if prompt is vague (follow mastermind-intake/SKILL.md — stop at Q3, domain is already known as `content`).
-
-Default mode for this command: **confirm** (unless `--auto` flag present or intake Q4 says auto).
-
-Invoke `Skill("mastermind-content")` passing: brain_context, prompt, project_name, board_id (create if needed), mode.
-
-After skill returns: follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `content`.
-
-Invoke `Skill("mastermind-repeat")` now to execute the REPEAT POSTAMBLE. This is a required tool call — do not skip it.

package/packages/@monomind/cli/.claude/commands/mastermind/createorg.md

@@ -1,143 +0,0 @@
-<!-- Define and save an autonomous agent organization (Org Runtime v2) — roles and hierarchy. Suggest or confirm roles, then persist the org config for `monomind org run`/`serve`. -->
-
-**If $ARGUMENTS is empty:** Output the following and wait.
-
----
-
-**MASTERMIND: CREATE ORG**
-
-An org is a named, persistent agent team, run by the Org Runtime v2 daemon — not a one-shot Mastermind run and not a Task-tool-spawned boss. Once created, every role in the config starts as its own live agent session the moment you run the org; roles message each other directly (no shared task board) and the org keeps running until stopped.
-
-Use orgs when the work is ongoing, not single-shot. A content team that ships 10 posts a month. A research squad that runs competitive scans weekly. A dev team with a permanent backlog.
-
-**What you provide:**
-- A goal — what should this org continuously accomplish?
-- Optional roles — or let Mastermind suggest them from the goal
-
-**Examples:**
-
-```
-/mastermind:createorg A content team that publishes 3 blog posts per week — writer, editor, SEO reviewer, publisher
-
-/mastermind:createorg --name research-pod Weekly competitor intelligence: researcher, analyst, summarizer
-
-/mastermind:createorg --auto An engineering team for ongoing feature development on my SaaS product
-```
-
-**Options:**
-`--name <slug>` — org identifier used with `monomind org run <name>` (derived from goal if omitted)
-`--roles <list>` — explicit role list (e.g. "boss, writer, reviewer, marketer")
-`--schedule <interval>` — daemon schedule for `monomind org serve` to pick up, e.g. `"30m"`, `"2h"`, `"1440m"` for daily (omit for a manual, one-shot org)
-`--auto` — skip confirmation, create immediately
-`--confirm` — always ask before saving (default)
-`--delete <name>` — delete a saved org and all associated data files (`monomind org delete <name> --yes`)
-`--list` — list all saved orgs with their status (`monomind org list`)
-
-Once created, start the org with `monomind org run <name>` (foreground, one-shot) or let `monomind org serve` pick it up if `--schedule` was set. Check status with `monomind org status <name>`; stop with `monomind org stop <name>`.
-
----
-
-**If $ARGUMENTS is non-empty:** Execute the flow below.
-
----
-
-Parse `$ARGUMENTS` for:
-- `--auto` flag → mode = auto (no confirmation prompt)
-- `--confirm` flag → mode = confirm
-- `--name <name>` → org_name = <name> (must match `^[a-z0-9][a-z0-9-]{0,63}$`; if omitted, derived from goal)
-- `--roles <desc>` → roles_desc = <desc> (explicit role list, e.g. "boss, writer, reviewer, marketer")
-- `--schedule <interval>` → schedule = <interval>, daemon format only: `"<N>s"`, `"<N>m"`, or `"<N>h"` (e.g. `"30m"`, `"2h"`) — this is passed straight into `parseSchedule()` in `orgrt/scheduler.ts`, whose regex `^(\d+)\s*(s|m|h)$` rejects anything else (e.g. `"every 30 minutes"`, `"daily"`) and silently leaves the org unscheduled
-- `--delete <name>` → delete_mode = true, delete_name = <name>
-- `--list` flag → list_mode = true
-- Remaining text = prompt (goal description)
-
-**If `--list` flag is set:**
-```bash
-# org list knows how to skip artifact side-car files (-state/-goals/…) and
-# shows role count, schedule, and runtime status per org
-npx -y monomind@latest org list || {
-  # fallback for environments without the CLI: config files only
-  orgs_dir=".monomind/orgs"
-  if [ ! -d "$orgs_dir" ] || [ -z "$(ls "$orgs_dir"/*.json 2>/dev/null)" ]; then
-    echo "No saved orgs. Run /mastermind:createorg <goal> to create one."
-  else
-    echo "Saved orgs:"
-    ls "$orgs_dir"/*.json | grep -vE -- '-(state|goals|threads|activity|approvals|members|secrets|budgets|routines|issues|projects|workspaces|worktrees|environments|plugins|adapters|join-requests|bootstrap|project-workspaces|approval-comments|skills)\.json$' \
-      | while IFS= read -r f; do
-          echo "  • $(basename "$f" .json) — $(jq -r '.goal // ""' "$f" 2>/dev/null | cut -c1-60)"
-        done
-  fi
-}
-```
-Stop after listing. Do not proceed to skill invocation.
-
-**If `--delete <name>` is set:**
-1. Confirm the org exists:
-   ```bash
-   [ -f ".monomind/orgs/${delete_name}.json" ] || { echo "Org '${delete_name}' not found."; exit 1; }
-   ```
-2. In confirm mode (default): ask "Delete org '${delete_name}' and all its data? This cannot be undone. Type 'yes' to confirm."
-   In auto mode: proceed without asking.
-3. Delete via the CLI (it refuses to delete a running org unless --force, and
-   removes every artifact side-car file); fall back to the dashboard server's
-   DELETE endpoint only if the CLI is unavailable:
-   ```bash
-   npx -y monomind@latest org delete "${delete_name}" --yes || {
-     REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
-     CTRL_URL=$(jq -r '.url // "http://localhost:4242"' "$REPO_ROOT/.monomind/control.json" 2>/dev/null || echo "http://localhost:4242")
-     result=$(curl -s -X DELETE -H "x-monomind-token: $(cat "${REPO_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}/.monomind/dashboard-token" 2>/dev/null || true)" "${CTRL_URL}/api/orgs/${delete_name}")
-     echo "$result" | jq -r 'if .ok then "Org '\'''"${delete_name}"'''\'' deleted." else "Error: " + (.error // "unknown") end'
-   }
-   ```
-4. Stop after deleting. Do not proceed to skill invocation.
-
-If neither `--auto` nor `--confirm` was provided, default: **mode = confirm**.
-
-If prompt is empty (and not list/delete mode): ask "Describe your org's goal and optionally list the roles you want (e.g. 'a content team with a boss, writer, reviewer, and marketer to produce 10 blog posts per month')."
-
-Load brain context for the `ops` domain (follow mastermind-protocol/SKILL.md Brain Load Procedure, namespace: `ops`).
-
-Generate a session ID as a real shell variable:
-```bash
-REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
-session_id="mm-$(date -u +%Y%m%dT%H%M%S)"
-CTRL_URL=$(jq -r '.url // "http://localhost:4242"' "$REPO_ROOT/.monomind/control.json" 2>/dev/null || echo "http://localhost:4242")
-```
-
-Emit `session:start` to dashboard:
-```bash
-curl -s -X POST "${CTRL_URL}/api/mastermind/event" -H "x-monomind-token: $(cat "${REPO_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}/.monomind/dashboard-token" 2>/dev/null || true)" \
-  -H "Content-Type: application/json" \
-  -d "$(jq -cn \
-    --arg session "$session_id" \
-    --arg prompt "$prompt" \
-    --arg mode "$mode" \
-    --arg proj "$REPO_ROOT" \
-    '{type:"session:start",session:$session,domain:"ops",prompt:$prompt,mode:$mode,project:$proj,ts:(now*1000|floor)}')" || true
-```
-
-Emit `domain:dispatch`:
-```bash
-curl -s -X POST "${CTRL_URL}/api/mastermind/event" -H "x-monomind-token: $(cat "${REPO_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}/.monomind/dashboard-token" 2>/dev/null || true)" \
-  -H "Content-Type: application/json" \
-  -d "$(jq -cn \
-    --arg session "$session_id" \
-    '{type:"domain:dispatch",session:$session,domain:"ops",cmd:"Designing and saving org definition",ts:(now*1000|floor)}')" || true
-```
-
-Invoke `Skill("mastermind-createorg")` passing: brain_context, prompt, org_name, roles_desc, schedule, mode, session_id: `$session_id`, caller: "command".
-
-After skill returns: note the status (`complete`, `partial`, or `blocked`). Emit `session:complete`:
-```bash
-curl -s -X POST "${CTRL_URL}/api/mastermind/event" -H "x-monomind-token: $(cat "${REPO_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}/.monomind/dashboard-token" 2>/dev/null || true)" \
-  -H "Content-Type: application/json" \
-  -d "$(jq -cn \
-    --arg session "$session_id" \
-    --arg status "<status>" \
-    '{type:"session:complete",session:$session,domain:"ops",status:$status,domains:["ops"],ts:(now*1000|floor)}')" || true
-```
-
-Follow mastermind-protocol/SKILL.md Brain Write Procedure for domain `ops`.
-
-
-Invoke `Skill("mastermind-repeat")` now to execute the REPEAT POSTAMBLE. This is a required tool call — do not skip it.