@mindrian_os/cli 1.13.0-beta.10 → 1.13.0-beta.44

package/commands/rooms.md

@@ -1,598 +0,0 @@
----
-name: rooms
-description: List, switch, or archive project rooms
-argument-hint: [list|switch|archive|park]
-body_shape: B (Semantic Tree)
-serves_jtbd: ["audit-room"]
-ui_reference: skills/ui-system/SKILL.md
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
----
-
-# /mos:rooms
-
-You are Larry. This command manages multiple project rooms using **Body Shape B (Semantic Tree)** per the UI Ruling System.
-
-## UI Format
-
-- **Body Shape:** B (Semantic Tree) for all subcommands
-- **Reference:** `skills/ui-system/SKILL.md`
-- All subcommands follow the 4-zone anatomy: Header Panel, Content Body, Intelligence Strip (conditional), Action Footer (NEVER omitted)
-- **Symbols:** Only the 12 approved glyphs. No emoji. No em-dashes.
-
-## Routing
-
-Parse user input to determine which subcommand to execute. If no subcommand is given, default to `list`.
-
-Subcommands: `list`, `new`, `open`, `close`, `archive`, `where`, `git-setup`, `git-status`
-
-**Natural language mapping (Desktop/Cowork):**
-- "which room am I in?" / "where am I?" -> `where`
-- "switch to fintech" / "open fintech" -> `open fintech-startup`
-- "show my rooms" / "list rooms" -> `list`
-- "create a new room" / "new room" -> `new`
-- "park this room" / "close room" -> `close`
-- "archive the old project" -> `archive`
-- "set up git for this room" / "add git" -> `git-setup`
-- "git status" / "is git configured?" -> `git-status`
-
----
-
-## Subcommand: list
-
-**Trigger:** `/mos:rooms` or `/mos:rooms list`
-
-### Step 1: Get Room Data
-
-Determine `ROOMS_HOME` (`$MINDRIAN_ROOMS_HOME` or `~/MindrianRooms`).
-
-Run `bash scripts/room-registry list` to get JSON array of rooms. The registry lives at `$ROOMS_HOME/.rooms/registry.json`.
-
-If the command fails (no registry exists), check for legacy `room/` directory:
-
-- If `room/` exists: Tell the user they have a single-room workspace. Suggest adopting it:
-  > "You have an existing room/ project. Run `/mos:rooms new` to create additional rooms -- I'll offer to adopt your existing project into the registry first."
-
-  Then STOP.
-
-- If no room at all: Tell the user they have no rooms yet. Suggest:
-  > "No rooms found. Your rooms will live at ~/MindrianRooms/. Run `/mos:rooms new` or `/mos:new-project` to get started."
-
-  Then STOP.
-
-### Step 2: Render Room List
-
-For each room in the JSON array, count .md files in the room directory (excluding STATE.md, ROOM.md, USER.md) to get the entry count.
-
-Render using Body Shape B (Semantic Tree):
-
-```
--- MindrianOS -- Rooms -- ~/MindrianRooms/ -------------------------
-
-  |- [filled-square] acme-robotics          active [git]  Pre-Opportunity   8 entries
-  |- [triangle-right] fintech-startup        parked        Discovery         14 entries
-  |- [hollow-triangle] biotech-venture        archived      Validation        22 entries
-
-  Active: acme-robotics (switched 2 hours ago)
-  Path: ~/MindrianRooms/acme-robotics/
-
-  [triangle-right] /mos:rooms open fintech-startup   Switch to parked room
-  [hollow-triangle] /mos:rooms new                    Create a new room
-  [hollow-triangle] /mos:rooms where                  Quick sanity check
-```
-
-Show `[git]` after the room status if `git_enabled` is `"true"` in the registry entry for that room.
-
-Symbol key:
-- `■` (filled square) = active room
-- `▶` (filled triangle) = parked room
-- `▷` (hollow triangle) = archived room
-
-Compute "switched X ago" from the active room's `last_opened` timestamp relative to now.
-
-### Step 3: Action Footer (Zone 4)
-
-Suggest 2-3 grounded next steps:
-- If parked rooms exist: `/mos:rooms open <name>` to switch to a parked room
-- Always: `/mos:rooms new` to create a new room
-- Always: `/mos:rooms where` for quick sanity check
-
----
-
-## Subcommand: new
-
-**Trigger:** `/mos:rooms new <name>`
-
-### Step 1: Validate Name
-
-The name must be a valid directory slug: lowercase, alphanumeric, hyphens only.
-
-If the user provides a human-readable name like "Acme Robotics":
-- Slugify to `acme-robotics`
-- Store the original as `venture_name`
-
-If no name provided, ask: "What should I call this room?"
-
-### Step 2: Resolve ROOMS_HOME and Check State
-
-Determine the central rooms location:
-
-```bash
-ROOMS_HOME="${MINDRIAN_ROOMS_HOME:-$HOME/MindrianRooms}"
-```
-
-If `$ROOMS_HOME/.rooms/registry.json` does NOT exist AND legacy `room/` directory exists in the workspace:
-
-Ask the user:
-> "You have an existing room/ project. Want me to adopt it into ~/MindrianRooms/ so you can have multiple rooms?"
-
-If user says yes:
-- Run `bash scripts/resolve-room $PWD --adopt` to create registry with existing room
-- Then proceed to Step 3
-
-If user says no: Proceed without adoption (the old room/ still works via legacy fallback).
-
-### Step 2.5: ICM Layer 0/1 Auto-Generation
-
-Before creating the room, ensure ICM files exist at `$ROOMS_HOME`:
-
-```bash
-PLUGIN_ROOT="$(dirname "$(dirname "$(readlink -f "$0")")")"
-if [ ! -f "$ROOMS_HOME/CLAUDE.md" ]; then
-  cp "$PLUGIN_ROOT/templates/icm/CLAUDE.md" "$ROOMS_HOME/CLAUDE.md"
-fi
-if [ ! -f "$ROOMS_HOME/INDEX.md" ]; then
-  cp "$PLUGIN_ROOT/templates/icm/INDEX.md" "$ROOMS_HOME/INDEX.md"
-fi
-```
-
-### Step 3: Create Room Directory
-
-Create directory at `~/MindrianRooms/<slug>/` (under ROOMS_HOME) with the 8 standard sections:
-
-```
-~/MindrianRooms/<slug>/
-  problem-definition/
-    ROOM.md
-  market-analysis/
-    ROOM.md
-  solution-design/
-    ROOM.md
-  business-model/
-    ROOM.md
-  competitive-analysis/
-    ROOM.md
-  team-execution/
-    ROOM.md
-  legal-ip/
-    ROOM.md
-  financial-model/
-    ROOM.md
-  team/
-```
-
-Each ROOM.md gets minimal frontmatter:
-
-```yaml
----
-section: {section-name}
-purpose: {one-line purpose from section definitions}
----
-```
-
-Use the section definitions from `/mos:new-project` Step 4 for purpose and methodology defaults.
-
-**Important:** `/mos:rooms new` creates the room STRUCTURE only. No deep exploration conversation happens here - that is what `/mos:new-project` does afterward. This keeps room creation fast.
-
-### Step 4: Register Room
-
-Run:
-```bash
-bash scripts/room-registry create <slug> "<slug>" "<venture_name>" "Pre-Opportunity"
-```
-
-The registry create command automatically sets the new room as active and parks the previous one.
-
-**Update INDEX.md:** After registration, refresh the routing index:
-
-```bash
-bash scripts/update-icm-index "$ROOMS_HOME"
-```
-
-### Step 5: Compute State
-
-Run:
-```bash
-bash scripts/compute-state "$ROOMS_HOME/<slug>" > "$ROOMS_HOME/<slug>/STATE.md"
-```
-
-### Step 6: Report Success
-
-Show success with Zone 1 header displaying the new room name:
-
-```
--- MindrianOS -- <venture_name> --------------------------------------
-
-  Room created: ~/MindrianRooms/<slug>/
-  Status: active
-  Venture stage: Pre-Opportunity
-  Sections: 8
-
-  [triangle-right] /mos:new-project     Start the deep exploration conversation
-  [hollow-triangle] /mos:rooms list      See all your rooms
-```
-
----
-
-## Subcommand: open
-
-**Trigger:** `/mos:rooms open <name>`
-
-### Step 1: Validate Room Exists
-
-Run `bash scripts/room-registry read <name>` to check if the room is in the registry.
-
-If not found, show 3-line error:
-```
-x Room not found: <name>
-  Why: No room named "<name>" in .rooms/registry.json
-  Fix: /mos:rooms list
-```
-
-Then STOP.
-
-### Step 2: Check Room Status
-
-Read the room's status from the registry entry.
-
-If status is `archived`, warn the user:
-> "This room is archived. Opening it will set its status to active. Continue?"
-
-Wait for confirmation before proceeding. If user declines, STOP.
-
-### Step 3: Switch Active Room
-
-Run:
-```bash
-bash scripts/room-registry set-active <name>
-```
-
-This parks the previous active room and sets the new one as active.
-
-### Step 4: Report Success
-
-Show Zone 1 header with the switched room name:
-
-```
--- MindrianOS -- <venture_name> --------------------------------------
-
-  Switched to: <name>
-  Status: active
-  Venture: <venture_name>
-  Stage: <venture_stage>
-
-  [triangle-right] /mos:status           Check room health
-  [triangle-right] /mos:room             View Data Room
-  [hollow-triangle] /mos:rooms where      Confirm active room
-```
-
----
-
-## Subcommand: close
-
-**Trigger:** `/mos:rooms close`
-
-### Step 1: Get Active Room
-
-Run `bash scripts/room-registry get-active` to get the current active room name.
-
-If no active room (empty result), show error:
-```
-x No active room to close
-  Why: No room is currently set as active in the registry
-  Fix: /mos:rooms list
-```
-
-Then STOP.
-
-### Step 2: Park the Room
-
-Run:
-```bash
-bash scripts/room-registry update <active-name> status parked
-```
-
-### Step 3: Clear Active Field
-
-Clear the active field in the registry by running:
-```bash
-ROOMS_HOME="${MINDRIAN_ROOMS_HOME:-$HOME/MindrianRooms}"
-python3 -c "
-import json
-with open('$ROOMS_HOME/.rooms/registry.json', 'r') as f:
-    reg = json.load(f)
-reg['active'] = ''
-with open('$ROOMS_HOME/.rooms/registry.json', 'w') as f:
-    json.dump(reg, f, indent=2)
-"
-```
-
-**Update INDEX.md:** After parking, refresh the routing index:
-
-```bash
-bash scripts/update-icm-index "$ROOMS_HOME"
-```
-
-### Step 4: Report Success
-
-```
--- MindrianOS -- No Active Room --------------------------------------
-
-  Room <name> is now parked. No active room.
-
-  [triangle-right] /mos:rooms list              See all rooms
-  [triangle-right] /mos:rooms open <name>       Reopen this room
-```
-
----
-
-## Subcommand: archive
-
-**Trigger:** `/mos:rooms archive <name>`
-
-### Step 1: Validate Room Exists
-
-Run `bash scripts/room-registry read <name>` to check if the room is in the registry.
-
-If not found, show 3-line error:
-```
-x Room not found: <name>
-  Why: No room named "<name>" in .rooms/registry.json
-  Fix: /mos:rooms list
-```
-
-Then STOP.
-
-### Step 2: Check if Active
-
-Read the room's status. If the room is currently active, warn the user:
-> "This is your active room. Archiving it will leave you with no active room. Continue?"
-
-Wait for confirmation. If user declines, STOP.
-
-### Step 3: Archive the Room
-
-Run:
-```bash
-bash scripts/room-registry archive <name>
-```
-
-This sets the room status to `archived`. If the room was active, it also clears the active field.
-
-**Update INDEX.md:** After archiving, refresh the routing index:
-
-```bash
-bash scripts/update-icm-index "${MINDRIAN_ROOMS_HOME:-$HOME/MindrianRooms}"
-```
-
-### Step 4: Report Success
-
-```
--- MindrianOS -- Rooms -----------------------------------------------
-
-  Room <name> is now archived.
-
-  [triangle-right] /mos:rooms list              See all rooms
-  [triangle-right] /mos:rooms open <other>      Switch to another room
-```
-
-If other non-archived rooms exist, suggest opening one by name.
-
----
-
-## Subcommand: where
-
-**Trigger:** `/mos:rooms where`
-
-### Step 1: Get Active Room
-
-Run `bash scripts/room-registry get-active` to get the current active room name.
-
-If no active room (empty result):
-> "No active room. Run `/mos:rooms list` to see available rooms."
-
-Then STOP.
-
-### Step 2: Read Room Details
-
-Run `bash scripts/room-registry read <active-name>` to get the full registry entry.
-
-### Step 3: Display Location
-
-```
--- MindrianOS -- <venture_name> --------------------------------------
-
-  Active room: <name>
-  Path: ~/MindrianRooms/<name>/
-  Venture: <venture_name>
-  Stage: <venture_stage>
-  Last opened: <timestamp>
-
-  [triangle-right] /mos:status           Check room health
-  [triangle-right] /mos:rooms open       Switch rooms
-  [hollow-triangle] /mos:rooms list       See all rooms
-```
-
-Display the path as `~/MindrianRooms/<name>/` (abbreviated with ~). For legacy rooms that haven't migrated, show the actual path (e.g., `./room/`).
-
----
-
-## Subcommand: git-setup
-
-**Trigger:** `/mos:rooms git-setup [name]`
-
-If no name provided, use the currently active room (get via `bash scripts/room-registry get-active`).
-
-### Step 1: Validate Room
-
-Run `bash scripts/room-registry read <name>` to verify room exists.
-
-If not found, show 3-line error and STOP.
-
-### Step 2: Check Current Git State
-
-Run `bash scripts/git-ops status <room_path>` to check if git is already configured.
-
-If already enabled:
-> "Git is already set up for this room."
-> Show current status (remote URL, auto_push setting, LFS status).
-> Offer to change settings: "Want to change auto-push mode? Current: <setting>."
-
-If user wants to change auto_push:
-```bash
-bash scripts/room-registry git-config <name> true "<existing_remote>" "<new_setting>"
-```
-
-Then STOP.
-
-### Step 3: Initialize Git
-
-```bash
-bash scripts/git-ops init <room_path>
-bash scripts/git-ops lfs-setup <room_path>
-```
-
-### Step 4: Offer GitHub Remote
-
-Check gh CLI:
-```bash
-gh --version 2>/dev/null
-```
-
-If gh available, check auth:
-```bash
-gh auth status 2>/dev/null
-```
-
-If gh available AND authenticated:
-> "Want me to create a GitHub repo for this room? (Private by default)"
-
-If user accepts:
-```bash
-gh repo create <name> --private --source=<room_path> --push
-```
-
-Capture remote URL.
-
-If gh NOT available:
-> "GitHub CLI not installed. Setting up local git only. Install `gh` later to add a remote: https://cli.github.com/"
-
-If gh available but NOT authenticated:
-> "GitHub CLI found but not logged in. Run `gh auth login`, then try again. Setting up local git only for now."
-
-### Step 5: First Commit
-
-```bash
-git -C <room_path> add -A
-git -C <room_path> commit -m "room: initialize <venture_name> Data Room"
-```
-
-IMPORTANT: Use `git -C <room_path>` instead of `cd + git`. This keeps all git operations consistent with the scripts/git-ops pattern (no bare `cd` side effects, handles spaces in paths).
-
-If remote configured:
-```bash
-bash scripts/git-ops push <room_path>
-```
-
-### Step 6: Update Registry
-
-```bash
-bash scripts/room-registry git-config <name> true "<remote_url_or_empty>" "off"
-```
-
-### Step 7: Report Success
-
-```
--- MindrianOS -- Git Setup Complete ------------------------------------
-
-  Room: <name>
-  Git: initialized
-  Remote: <url or "local only">
-  Auto-push: off (opt-in with --auto-push auto)
-  LFS: <enabled/not available>
-
-  [triangle-right] /mos:rooms git-setup <name> --auto-push auto   Enable auto-push
-  [triangle-right] /mos:rooms git-status                          Check git state
-  [hollow-triangle] /mos:rooms list                                See all rooms
-```
-
-### Auto-push Flag
-
-If the user passes `--auto-push <mode>` (where mode is auto, manual, or off), set that mode instead of the default "off":
-```bash
-bash scripts/room-registry git-config <name> true "<remote>" "<mode>"
-```
-
-**CRITICAL:** If ANY git operation fails, print a brief note and STOP gracefully. Git failure must NEVER leave the room in a broken state. Example:
-
-> "Git setup had an issue. Your room still works fine. Try again or check `gh auth status`."
-
----
-
-## Subcommand: git-status
-
-**Trigger:** `/mos:rooms git-status [name]`
-
-If no name provided, use the currently active room.
-
-### Step 1: Get Status
-
-Run `bash scripts/git-ops status <room_path>`
-
-### Step 2: Render
-
-If git not enabled:
-```
--- MindrianOS -- <name> ------------------------------------------------
-
-  Git: not configured
-
-  [triangle-right] /mos:rooms git-setup <name>   Set up git for this room
-```
-
-If git enabled:
-```
--- MindrianOS -- <name> ------------------------------------------------
-
-  Git: enabled
-  Remote: <url or "none (local only)">
-  Auto-push: <auto|manual|off>
-  LFS: <installed|not available>
-  Uncommitted changes: <N files>
-
-  [triangle-right] /mos:rooms git-setup <name> --auto-push auto   Change auto-push
-  [hollow-triangle] /mos:rooms list                                See all rooms
-```
-
----
-
-## Cross-Surface Notes (Tri-Polar Rule)
-
-| Surface | Behavior |
-|---------|----------|
-| **CLI** | Full subcommand syntax as documented above. Scripts run directly. |
-| **Desktop** | Larry interprets natural language and maps to subcommands. See natural language mapping at top. |
-| **Cowork** | Same registry, same commands. Cowork agents share the room context via 00_Context/. When switching rooms, mention that Cowork state follows the active room. |
-
-## Error Format
-
-Always use the 3-line error pattern:
-
-```
-x What happened
-  Why: reason
-  Fix: /mos:command
-```

package/commands/root-cause.md

@@ -1,34 +0,0 @@
----
-name: root-cause
-description: Trace root cause via 5-Whys, Fishbone, Fault Tree
-serves_jtbd: ["find-problem"]
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
----
-
-# /mos:root-cause
-
-You are Larry. This command guides the user through Root Cause Analysis.
-
-## Setup
-
-1. Read `references/methodology/root-cause.md` for framework details
-2. Read `references/personality/voice-dna.md` for Larry's voice
-3. Read `room/STATE.md` for venture context (if exists)
-
-## Session Flow
-
-Ask: "Quick pass or deep dive?"
-
-Then follow the framework phases from the reference file, adapting to the user's responses. You are NOT following a rigid script -- the phases are a guide. If the user provides rich context, skip ahead. If they need more exploration, slow down.
-
-## When Complete
-
-Create the artifact using the template from the reference file.
-Ask: "File this to problem-definition?" before writing.
-
-If the conversation reveals a connection to another methodology, suggest it:
-"The root cause you found connects to [methodology]. Want to explore that next?"

package/commands/rs-experts.md

@@ -1,79 +0,0 @@
----
-name: rs-experts
-description: Resolve the expert network for a topic via Aura Cypher MATCH
-body_shape: D (Comparison Matrix)
-serves_jtbd: ["find-bottleneck", "connect-domains"]
-ui_reference: skills/ui-system/SKILL.md
-allowed-tools:
-  - Bash
-  - Read
-  - mcp__mindrian-brain__read_neo4j_cypher
----
-
-# /mos:rs-experts
-
-You are Larry. This command resolves the expert network for a topic from the local Aura instance (Tier 1). Authors and institutions accumulate in Aura via `rs-fetcher-experts` (Phase 89.2-05) and `rs-expert-mapper.mapAuthorsToAura` (Phase 89.3-04) during prior `/mos:rs-fetch` runs. The query is a parameterized Cypher MATCH on `AUTHORED_BY` and `AFFILIATED_WITH` edges. Tier 0 (Aura unreachable) returns a graceful "Aura not connected" guidance message.
-
-**Synopsis:**
-
-    /mos:rs-experts <topic>
-    /mos:rs-experts <topic> --json
-    /mos:rs-experts <topic> --limit 20
-
-## What it does
-
-1. Validates `<topic>` against Canon Part 8 (`auditQueryString` on the bound parameter; throws `ExternalEgressViolation` if forbidden bytes appear).
-2. Detects Aura availability via `brainClient.isAvailable()` plus the Aura driver / `NEO4J_URI` env var checks.
-3. Tier 1 path: runs the Cypher MATCH `(a:Author)-[:AUTHORED_BY]->(p:Paper) WHERE p.topic = $topic OPTIONAL MATCH (a)-[:AFFILIATED_WITH]->(i:Institution) RETURN a, collect(DISTINCT i) AS institutions LIMIT $limit` with parameterized `$topic` + `$limit`. Returns ranked author list with institution affiliations.
-4. Tier 0 path: emits the 3-line guidance error pointing to `/mos:rs-fetch` to populate the local mirror first.
-5. Emits Phase Gate-style transcript (CLI) or JSON (`--json`).
-
-## UI Format
-
-- **Body Shape:** D (Comparison Matrix) -- ranked authors with institutions
-- **Reference:** `skills/ui-system/SKILL.md`
-- **Zone 1:** Header Panel -- topic + author count
-- **Zone 2:** Content Body -- ranked table: Rank / Author / Institution / Papers / Score
-- **Zone 3:** Intelligence Strip -- top institution cluster signals
-- **Zone 4:** Action Footer -- next-step verbs (`/mos:persona` may be warranted; `/mos:rs-fetch` for fresh papers)
-
-## Three-surface notes
-
-- **CLI:** Phase Gate-style transcript with the ranked table.
-- **Desktop MCP:** structured JSON via `--json`; the MCP wrapper renders Larry's narration with top 3 authors as conversational mentions.
-- **Cowork:** honors `MINDRIAN_ROOM`; multi-user rooms see the same shared expert list filed in `00_Context/`.
-
-## Canon References
-
-- **Canon Part 7 (Reuse Before Build):** consumes existing `brain-client.cjs` Aura session. Zero forks.
-- **Canon Part 8 (Graph Boundary):** topic is parameterized as `$topic` (NO string concatenation). Audited via `auditQueryString` BEFORE binding. The Aura is a LOCAL Brain mirror per Canon Part 8; this command does NOT query the remote Brain methodology graph.
-
-## Examples
-
-    /mos:rs-experts "quantum brain imaging"
-    /mos:rs-experts "fintech KYC" --json
-    /mos:rs-experts "carbon capture" --limit 50
-
-## Error patterns
-
-3-line error format:
-
-    x Aura not connected
-      Why: brainClient.isAvailable() returned false; expert network requires Aura
-      Fix: /mos:rs-fetch <topic> first to populate the local SQLite mirror, then retry
-
-    x No experts found for topic
-      Why: zero rows matched topic <topic> in Aura
-      Fix: /mos:rs-fetch <topic>
-
-    x Canon Part 8 audit failed
-      Why: forbidden bytes in topic argument (ExternalEgressViolation)
-      Fix: rephrase the topic without user-content placeholders
-
-## Voice
-
-Larry direct:
-
-> "Mapped <N> experts across <M> institutions. Leading: <top institution>. /mos:persona may be warranted to build the engagement strategy."
-
-> "Aura not connected. Run /mos:rs-fetch first to populate the mirror, then I can resolve the expert network."