@mindrian_os/cli 2.0.0-beta.29 → 2.0.0-beta.31

package/references/brain/room-hierarchy-schema.md

@@ -0,0 +1,218 @@
+# Room Hierarchy Graph Schema
+
+Schema for Room/RoomGroup hierarchy in both KuzuDB (local) and Neo4j Brain (remote).
+Added in Phase 59.2. Additive-only -- filesystem + registry.json remain operational truth.
+
+## Node Types
+
+### Room
+Represents a registered Data Room (venture workspace).
+
+| Property | Type | Source | Notes |
+|----------|------|--------|-------|
+| name | STRING (PK) | registry.json key | Room slug, e.g. "acme-robotics" |
+| venture_name | STRING | registry.json | Human-readable name |
+| venture_stage | STRING | registry.json | Pre-Opportunity, Discovery, Validation, Design, Investment |
+| domain | STRING | registry.json or inferred | Domain keywords |
+| status | STRING | registry.json | active, parked, archived |
+| created | STRING | registry.json | ISO 8601 timestamp |
+| path | STRING | registry.json | Relative path from ROOMS_HOME |
+
+**Present in:** KuzuDB + Brain
+
+### RoomGroup
+Represents a grouping directory (clients/, internal/, etc.).
+
+| Property | Type | Source | Notes |
+|----------|------|--------|-------|
+| name | STRING (PK) | Directory name | Group slug, e.g. "clients" |
+| icm_layer | STRING | Always "group" | ICM classification |
+| rationale | STRING | CLAUDE.md first line | Why this group exists |
+| path | STRING | Relative from ROOMS_HOME | Directory path |
+
+**Present in:** KuzuDB + Brain
+
+### RoomRoot (Brain only)
+Singleton node representing ~/MindrianRooms/ itself.
+
+| Property | Type | Notes |
+|----------|------|-------|
+| name | STRING (PK) | Always "MindrianRooms" |
+| created | DATETIME | First sync timestamp |
+| path | STRING | Always "~/MindrianRooms/" |
+
+### VentureStage
+Five-stage taxonomy (already exists in Brain, seeded in KuzuDB).
+
+| Property | Type | Notes |
+|----------|------|-------|
+| name | STRING (PK) | Pre-Opportunity, Discovery, Validation, Design, Investment |
+
+**Present in:** KuzuDB + Brain (pre-existing in Brain)
+
+## Relationship Types
+
+### CONTAINS
+Physical hierarchy edges.
+
+| From | To | Scope | Notes |
+|------|----|-------|-------|
+| RoomRoot | RoomGroup | Brain | Root contains groups |
+| RoomRoot | Room | Brain | Root contains ungrouped rooms |
+| RoomGroup | Room | Both | Group contains rooms |
+| RoomGroup | RoomGroup | KuzuDB | Nested groups (future) |
+
+### AT_STAGE
+Connects Room to its current VentureStage.
+
+| From | To | Scope | Notes |
+|------|----|-------|-------|
+| Room | VentureStage | Both | One edge per room, deleted and recreated on stage change |
+
+### USES_FRAMEWORK (Brain only)
+Connects Room to Framework nodes based on methodology commands run in that room.
+
+| From | To | Properties | Notes |
+|------|----|------------|-------|
+| Room | Framework | first_used (datetime), usage_count (int) | Created from room/.analytics.json |
+
+Source: `track-analytics` records command usage per room. `sync-rooms-brain` maps commands to Framework node names.
+
+### SHARES_THEME (Brain only)
+Cross-room content similarity detected from problem-definition keywords.
+
+| From | To | Properties | Notes |
+|------|----|------------|-------|
+| Room | Room | shared_terms (string), term_count (int), detected (datetime) | Bidirectional conceptually, stored as directed edge |
+
+Detection: reads first 5 files from each room's `problem-definition/` directory, extracts domain keywords (5+ chars), requires 10+ shared keywords for edge creation.
+
+### HAS_SECTION (Brain only)
+Wires Room to DataRoomSection nodes (13 existing orphans in Brain).
+
+| From | To | Notes |
+|------|----|-------|
+| Room | DataRoomSection | Created only when section directory exists in room filesystem |
+
+Standard sections: Problem Definition, Market Analysis, Solution Design, Business Model, Competitive Analysis, Team & Execution, Legal & IP, Financial Model, Opportunity Bank, Funding, Product, Decisions, Beta Testing.
+
+### GROUPED_BY_USER (Brain only, future)
+Created by /mos:organize move when user confirms a grouping.
+
+| From | To | Properties |
+|------|----|------------|
+| Room | RoomGroup | timestamp (datetime), rationale (string) |
+
+### SEPARATED_BY_USER (Brain only, future)
+Created by /mos:organize when user rejects a grouping.
+
+| From | To | Properties |
+|------|----|------------|
+| Room | Room | timestamp (datetime), reason (string) |
+
+## KuzuDB DDL
+
+Location: `$ROOMS_HOME/.rooms/.room-graph/`
+
+```sql
+-- Node tables
+CREATE NODE TABLE IF NOT EXISTS Room(
+  name STRING PRIMARY KEY,
+  venture_name STRING,
+  venture_stage STRING,
+  domain STRING,
+  status STRING,
+  created STRING,
+  path STRING
+);
+
+CREATE NODE TABLE IF NOT EXISTS RoomGroup(
+  name STRING PRIMARY KEY,
+  icm_layer STRING,
+  rationale STRING,
+  path STRING
+);
+
+CREATE NODE TABLE IF NOT EXISTS VentureStage(
+  name STRING PRIMARY KEY
+);
+
+-- Relationship tables
+CREATE REL TABLE IF NOT EXISTS CONTAINS(FROM RoomGroup TO Room);
+CREATE REL TABLE IF NOT EXISTS GROUP_CONTAINS(FROM RoomGroup TO RoomGroup);
+CREATE REL TABLE IF NOT EXISTS AT_STAGE(FROM Room TO VentureStage);
+```
+
+## Cypher Patterns for /mos:organize
+
+### Get room hierarchy tree
+```cypher
+MATCH (root:RoomRoot {name: 'MindrianRooms'})
+OPTIONAL MATCH (root)-[:CONTAINS]->(g:RoomGroup)-[:CONTAINS]->(r:Room)
+OPTIONAL MATCH (root)-[:CONTAINS]->(ungrouped:Room)
+WHERE NOT (ungrouped)<-[:CONTAINS]-(:RoomGroup)
+RETURN g.name AS group_name,
+       collect(DISTINCT r.name) AS grouped_rooms,
+       collect(DISTINCT ungrouped.name) AS ungrouped_rooms
+```
+
+### Find rooms sharing frameworks
+```cypher
+MATCH (r1:Room)-[:USES_FRAMEWORK]->(f:Framework)<-[:USES_FRAMEWORK]-(r2:Room)
+WHERE r1.name <> r2.name
+RETURN r1.name, r2.name, collect(f.name) AS shared_frameworks
+```
+
+### Find rooms at the same venture stage
+```cypher
+MATCH (r:Room)-[:AT_STAGE]->(s:VentureStage)
+RETURN s.name AS stage, collect(r.name) AS rooms
+```
+
+### Find rooms with shared themes
+```cypher
+MATCH (r1:Room)-[e:SHARES_THEME]->(r2:Room)
+RETURN r1.name, r2.name, e.shared_terms, e.term_count
+ORDER BY e.term_count DESC
+```
+
+### Find orphaned rooms (not in any group)
+```cypher
+MATCH (r:Room)
+WHERE NOT (:RoomGroup)-[:CONTAINS]->(r)
+RETURN r.name, r.venture_stage, r.status
+```
+
+### Get room's full context (all edges)
+```cypher
+MATCH (r:Room {name: $room_name})
+OPTIONAL MATCH (r)-[:AT_STAGE]->(s:VentureStage)
+OPTIONAL MATCH (r)-[:USES_FRAMEWORK]->(f:Framework)
+OPTIONAL MATCH (r)-[:HAS_SECTION]->(sec:DataRoomSection)
+OPTIONAL MATCH (r)-[:SHARES_THEME]-(other:Room)
+RETURN r.name, s.name AS stage,
+       collect(DISTINCT f.name) AS frameworks,
+       collect(DISTINCT sec.name) AS sections,
+       collect(DISTINCT other.name) AS theme_neighbors
+```
+
+## Sync Scripts
+
+| Script | Target | Trigger | Frequency |
+|--------|--------|---------|-----------|
+| `scripts/sync-rooms-graph` | KuzuDB local | session-start, room-registry create/archive | Every session + on room changes |
+| `scripts/sync-rooms-brain` | Neo4j Brain | session-start (when Brain available) | Best-effort, per session |
+
+Both scripts are idempotent and fire-and-forget. Failure degrades gracefully:
+- Brain unavailable -> KuzuDB only
+- KuzuDB unavailable -> filesystem only (Tier 0)
+- Both unavailable -> everything still works from registry.json
+
+## Additive-Only Rule (D-15 through D-18)
+
+1. Graph NEVER writes to filesystem or registry.json
+2. Graph NEVER blocks any operation on failure
+3. All graph operations are fire-and-forget (async, best-effort)
+4. Graph data can be regenerated from filesystem at any time (no exclusive state)
+
+The graph layer adds intelligence. It never owns truth.

package/references/brain/schema.md

@@ -0,0 +1,86 @@
+# Brain Schema Reference
+
+Neo4j Aura graph -- 21K+ nodes, 65K+ relationships. Larry's teaching intelligence.
+
+## How Brain Connects
+
+**CLI:** `brain-client.cjs` calls the Brain HTTP API directly using `MINDRIAN_BRAIN_KEY` from `.env` or `~/.mindrian.env`. No MCP config needed. Functions: `brain.query(cypher)`, `brain.search(text)`, `brain.schema()`.
+
+**Desktop/Cowork:** Add Brain as an MCP server in `claude_desktop_config.json` or Cowork settings. Server name: `mindrian-brain`. Tools become:
+- `mcp__mindrian-brain__brain_query` -- execute Cypher queries
+- `mcp__mindrian-brain__brain_write` -- write operations (admin only)
+- `mcp__mindrian-brain__brain_schema` -- introspect schema
+- `mcp__mindrian-brain__brain_search` -- semantic search via Pinecone
+
+Note: Brain is NOT configured in the plugin's `.mcp.json` (that file is for the local mindrian-os stdio server only). Brain config lives in user settings because it requires a per-user API key.
+
+## Node Types
+
+| Label | ~Count | Key Properties | Purpose |
+|-------|--------|----------------|---------|
+| Framework | 275+ | name, description, category, difficulty | Innovation methodology frameworks |
+| Phase | varies | name, order, description, framework_id | Ordered steps within a framework |
+| Concept | varies | name, description | Abstract innovation concepts |
+| ProblemType | 4 | name (Un-Defined, Ill-Defined, Well-Defined, Wicked) | Problem classification |
+| Book | 59 | title, author, isbn | Analyzed source books |
+| Tool | 59 | name, description, pws_mapping | Innovation tools with PWS mappings |
+| Course | varies | name, code, semester | Curriculum courses |
+| Example | 80+ | project_name, grade, grade_numeric, rubric_scores, feedback_patterns, percentile, example_type | Graded student work AND worked examples attached to frameworks/methods |
+| Method | 94 | name, description | Alternative methods a framework offers (e.g. Three Approaches -> Brute Force / Targeted / Eureka) |
+| Stage | 74 | name, order, consciousness_level | Ordered stages within a framework (e.g. Wallas creativity stages) |
+| Insight | 13 | name, description | Teaching insights a framework/method reveals |
+| Question | 8 | name, question_type | Beautiful-question / diagnostic prompts attached to a level or framework |
+| PyramidLevel | 5 | name, level_order | Ackoff DIKW levels (Data/Information/Knowledge/Understanding/Wisdom) |
+
+## Relationships
+
+| Relationship | From -> To | Properties | Why It Matters |
+|--------------|-----------|------------|----------------|
+| FEEDS_INTO | Framework -> Framework | confidence, transform_description | Framework chaining rules |
+| TRANSFORMS_OUTPUT_TO | Framework -> Framework | transform_type, description | How output becomes input |
+| CO_OCCURS | Framework -> Framework | frequency, context | Natural framework pairings |
+| ADDRESSES_PROBLEM_TYPE | Framework -> ProblemType | effectiveness | Framework-to-problem mapping |
+| HAS_PHASE | Framework -> Phase | order | Phase progressions |
+| PREREQUISITE | Framework -> Framework | strength | What must come first |
+| APPLIED_IN | Framework -> Example | section, quality_score | Real usage with grades |
+| REFERENCES | Book -> Framework | chapter, relevance | Source material links |
+| HAS_EXAMPLE | Framework/Method -> Example | example_type | Worked examples attached directly to a framework or method (OODA, Usher, Ackoff, Wallas, the Three Approaches). Larry reaches for this to illustrate a concept on demand. |
+| HAS_METHOD | Framework -> Method | -- | A framework offers these alternative methods (Three Approaches -> Brute Force / Targeted Development / Eureka; Ackoff -> Camera Test). Use to surface method choices within a framework. |
+| REVEALS | Framework/Method -> Insight | -- | The teaching insight a framework or method exposes. Use when Larry explains *why* a framework matters, not just how. |
+| CONTRASTS_WITH | Framework -> Theory/Framework | -- | A rejected or rival theory (Usher -> Transcendentalist / Mechanistic). Use to teach by contrast. |
+| DIRECTS | PyramidLevel -> PyramidLevel | -- | Downward direction in the Ackoff pyramid (Wisdom directs what Data to collect). Use to teach top-down DIKW reasoning. |
+
+## Grading Calibration Data
+
+Example nodes provide calibration for grading:
+- `rubric_scores`: {vision, problem_definition, feasibility, market, completeness}
+- `grade` / `grade_numeric`: letter (A-F) and numeric (0-100)
+- `feedback_patterns`: common tags (Vision-to-Execution Gap, Framework Vomit, etc.)
+- `percentile`: ranking within cohort
+
+Grading Agent compares user's room state against this distribution for calibrated assessment.
+
+## .mcp.json Template
+
+```json
+{
+  "mcpServers": {
+    "neo4j-brain": {
+      "command": "npx",
+      "args": ["-y", "@neo4j/mcp-neo4j"],
+      "env": {
+        "NEO4J_URI": "{uri}",
+        "NEO4J_USER": "{user}",
+        "NEO4J_PASSWORD": "{password}"
+      }
+    },
+    "pinecone-brain": {
+      "command": "npx",
+      "args": ["-y", "@anthropic/pinecone-mcp"],
+      "env": {
+        "PINECONE_API_KEY": "{key}"
+      }
+    }
+  }
+}
+```

package/references/capability-radar/capabilities-index.md

@@ -0,0 +1,269 @@
+# Claude Capabilities Index for MindrianOS
+
+Last updated: 2026-08-27 (Phase 265 correction pass). `data/capability-ledger.json` is now
+the machine-readable source of record for tracked Claude Code capabilities; this file is
+curated human prose over it, not a duplicate of its rows.
+
+This reference is curated. Run `/mos:radar --fetch` to check the Claude Code changelog for
+recent additions - Step 3b of `commands/radar.md` writes the ledger first, this file gets
+updated by hand when a ledger row is promoted to curated prose. `SEED-003-claude-code-2-1-x-
+capability-adoption.md` is superseded by Phase 265; see the ledger for current tracking.
+
+---
+
+## models
+
+### Opus 5 (current top-tier model)
+- **What:** The current top-tier model. `lib/core/model-profiles.cjs` maps agent types to the
+  bare alias `opus`, `sonnet`, or `haiku` - the alias resolves at the host to whatever model
+  is currently the top of that family, so a new model generation needs no config change here.
+  The `/effort` slider's maximum-reasoning xhigh tier (introduced alongside Opus 4.7, Claude
+  Code 2.1.111) is still available and still overkill for most plans, but worth it for
+  load-bearing migration phases.
+- **MindrianOS relevance:** No config key naming a fixed executor model exists anywhere in this
+  repo (that claim in an earlier version of this doc was wrong). The two real model-config
+  surfaces are
+  `lib/core/model-profiles.cjs` (agent types -> bare aliases) and `.planning/config.json`
+  (GSD only), both alias-based.
+- **Status:** available
+- **Since:** current generation; historical predecessor was Opus 4.7 (Claude Code 2.1.111)
+
+### Opus (extended context, historical baseline: Opus 4.6)
+- **What:** Extended thinking, adaptive reasoning, 128K max output tokens, 1M context window.
+  Opus 4.6 was the generation that first shipped this combination; the `opus` alias now
+  resolves to the current top-tier generation automatically, so this entry documents the
+  capability's history rather than asserting Opus 4.6 is current.
+- **MindrianOS relevance:** Methodology sessions can go deeper with full reference loading viable. Complex pipelines (Discovery, Thesis) can hold complete Room state in context without compression.
+- **Status:** capability persists across generations via alias resolution
+- **Since:** 2026 Q1 (Opus 4.6 introduced it)
+
+### Sonnet (balanced default, historical baseline: Sonnet 4.6)
+- **What:** Balanced speed and intelligence. 200K default context, extendable to 1M. Sonnet 4.6
+  was the generation current when this entry was first written; the `sonnet` alias resolves to
+  the current generation automatically, so this entry documents the capability's history rather
+  than asserting Sonnet 4.6 is current.
+- **MindrianOS relevance:** Default model for most users. Context compression and selective reference loading are critical. Room intelligence pipeline must stay within budget.
+- **Status:** capability persists across generations via alias resolution
+- **Since:** 2026 Q1 (Sonnet 4.6 introduced it)
+
+### Haiku 4.5
+- **What:** Fast, cost-efficient model for background and lightweight tasks
+- **MindrianOS relevance:** Potential for non-blocking Room analysis, quick classification tasks, and high-volume insight filing where speed matters more than depth.
+- **Status:** available
+- **Since:** 2025 Q4
+
+---
+
+## code
+
+### Statusline API
+- **What:** Real-time display of context window usage, model info, and cost data in the CLI status bar
+- **MindrianOS relevance:** Powers the context-monitor bridge. Lets users see how much context their Room and methodology sessions consume in real time.
+- **Status:** available
+- **Since:** 2025 Q4
+
+### Hooks (SessionStart, Stop, PostToolUse)
+- **What:** Event-driven plugin behavior triggered at session lifecycle points and after tool usage
+- **MindrianOS relevance:** Core of the intelligence pipeline. SessionStart loads Room state and proactive findings. PostToolUse triggers passive insight filing. SessionStop handles cleanup.
+- **Status:** available
+- **Since:** 2025 Q3
+
+### Hooks Can Invoke MCP Tools Natively (`type: "mcp_tool"`)
+- **What:** Hook entries can declare `type: "mcp_tool"` and call any registered MCP tool directly, without spawning a Node child process
+- **MindrianOS relevance:** Removes the `lib/core/brain-client.cjs` proxy layer. Eliminates a class of "hook timed out at 2000ms" failures. Direct moat deepening per the MWP mandate. Tracked as adoption candidate A2 in SEED-003.
+- **Status:** available
+- **Since:** Claude Code 2.1.118
+
+### PostToolUse `updatedToolOutput` (Tool-Output Rewrite)
+- **What:** PostToolUse hooks can rewrite a tool's output via `hookSpecificOutput.updatedToolOutput` before the model sees it
+- **MindrianOS relevance:** Structural enforcement of Canon Part 8. Sanitize Brain MCP responses to redact accidental user-data echo at runtime. Closes the gap noted in CANON-PHASE-MAP.md (Part 8 row, "PR gate pending"). Tracked as adoption candidate A3 in SEED-003.
+- **Status:** available
+- **Since:** Claude Code 2.1.121
+
+### `/usage` (replaces `/cost` + `/stats`)
+- **What:** Unified usage/cost reporting command; replaces the two prior commands
+- **MindrianOS relevance:** Statusline `📊` token-budget glyph (Phase 106-02) should track the new command's output schema. Single-line update.
+- **Status:** available
+- **Since:** Claude Code 2.1.118
+
+### `/skills` Type-to-Filter
+- **What:** Skills picker now has a type-to-filter search box
+- **MindrianOS relevance:** Improves discoverability of MindrianOS's 30+ skills. No code change required on the plugin side.
+- **Status:** available
+- **Since:** Claude Code 2.1.121
+
+### `/ultrareview` Built-in
+- **What:** Built-in parallel code-review command (also available as non-interactive `claude ultrareview [target]`)
+- **MindrianOS relevance:** May overlap with MindrianOS's own `/ultrareview`. Verify; if Anthropic's built-in is sufficient, delegate to it and remove the MindrianOS duplication.
+- **Status:** available
+- **Since:** Claude Code 2.1.111
+
+### `${CLAUDE_EFFORT}` in Skills
+- **What:** Skills can read `${CLAUDE_EFFORT}` to calibrate verbosity/depth based on the user's current `/effort` setting
+- **MindrianOS relevance:** Larry skills (larry-personality, larry-extended) can match teaching depth to user effort. xhigh effort = deeper Feynman decomposition; low effort = terse navigation.
+- **Status:** available
+- **Since:** Claude Code 2.1.120
+
+### `claude project purge`
+- **What:** Subcommand to delete all Claude Code state at a path with `--dry-run`, `-y`, `-i`, `--all` flags
+- **MindrianOS relevance:** Clean-slate command for testers when an install goes sideways. Mention in tester onboarding docs.
+- **Status:** available
+- **Since:** Claude Code 2.1.126
+
+### Background Tasks (run_in_background)
+- **What:** Async command execution that runs without blocking the main conversation
+- **MindrianOS relevance:** Potential for non-blocking Room analysis, export generation, and Brain queries that don't interrupt the user's flow.
+- **Status:** available
+- **Since:** 2025 Q4
+
+### Max Output Tokens (128K for Opus)
+- **What:** Opus can generate up to 128K tokens in a single response
+- **MindrianOS relevance:** Export and document generation quality. Full thesis documents, comprehensive Room exports, and detailed grading reports can be generated in one pass.
+- **Status:** available
+- **Since:** 2026 Q1
+
+---
+
+## desktop_cowork
+
+### Cowork
+- **What:** Multi-user persistent agents with shared 00_Context/ state directory
+- **MindrianOS relevance:** Team venture collaboration. Multiple users can work on the same venture with shared Room state, concurrent methodology sessions, and unified Data Room.
+- **Status:** available
+- **Since:** 2025 Q4
+
+### Desktop
+- **What:** Conversational interface with MCP server support and visual interaction
+- **MindrianOS relevance:** Larry personality shines here. Users interact naturally without commands. MCP Brain connection works seamlessly. One of the three surfaces MindrianOS must support.
+- **Status:** available
+- **Since:** 2025 Q3
+
+### Agent Teams
+- **What:** Experimental multi-agent coordination for complex tasks
+- **MindrianOS relevance:** Potential for specialized agent collaboration. Research Agent + Investor Agent could run adversarial analysis in parallel. Pipeline stages could delegate to focused agents.
+- **Status:** experimental
+- **Since:** 2026 Q1
+
+### Fork Mode Defaults (`CLAUDE_CODE_FORK_SUBAGENT`)
+- **What:** Fork mode runs subagents concurrently. As of Claude Code 2.1.232, fork mode is ON
+  BY DEFAULT in every interactive session. The `CLAUDE_CODE_FORK_SUBAGENT` environment variable
+  still exists, but its polarity inverted: it is now the opt-OUT, not an opt-in. `=0` turns fork
+  mode off in every kind of session; `=1` turns fork mode on in non-interactive mode and the
+  Agent SDK only. A reader who sets `=1` in an interactive session today is not opting into
+  anything - fork mode is already on for them. Source: code.claude.com/docs/en/sub-agents.
+- **MindrianOS relevance:** Substrate for Canon Part 2 Engine 2 (BONO Orchestration) - spawning
+  hat-instantiated team members in parallel. Superseded SEED-003 A4; see
+  `data/capability-ledger.json` (capability `run_in_background-removal-fork-mode-default-on`)
+  and Phase 265 (capability-radar-absorption-routing) for the corrected destination mapping.
+- **Status:** available (default on, interactive sessions; opt-out via `=0`)
+- **Since:** Claude Code 2.1.232 (the polarity inversion); the variable itself existed since 2.1.117
+
+### Agent Frontmatter `mcpServers` Declaration
+- **What:** Individual agent files can declare required MCP servers in frontmatter; loaded for main-thread sessions via `--agent`
+- **MindrianOS relevance:** Per-agent Brain MCP scoping. `mos-research` can require Brain without polluting global config; `mos-investor` (synthesis hat) can opt out. See `data/capability-ledger.json` and Phase 265 for current tracking; SEED-003 is superseded.
+- **Status:** available
+- **Since:** Claude Code 2.1.117
+
+### Push Notification Tool for Remote Control
+- **What:** Built-in tool for asynchronously notifying the user (push notification surface)
+- **MindrianOS relevance:** Larry can ping the user when Brain finishes an enrichment cycle, when a proactive scan finds a contradiction, or when a long-running methodology completes. Today these only surface if the user is actively in the session.
+- **Status:** available
+- **Since:** Claude Code 2.1.110
+
+### `/focus` View
+- **What:** Toggleable focus view in the TUI
+- **MindrianOS relevance:** Aligns with Canon's focus-node concept (Phase 109 D-01). Statusline `🎯` glyph should coordinate with `/focus` state - when user is in focus view, render the focus node prominently.
+- **Status:** available
+- **Since:** Claude Code 2.1.110
+
+---
+
+## plugins_mcp
+
+### Plugin Marketplace
+- **What:** Git-based plugin distribution with auto-updates and version management
+- **MindrianOS relevance:** Primary distribution channel. Users install MindrianOS with one command. Auto-updates keep methodology content current.
+- **Status:** available
+- **Since:** 2025 Q4
+
+### `--plugin-dir` Accepts `.zip` Archives
+- **What:** `claude --plugin-dir <path>` now accepts a `.zip` archive in addition to a directory
+- **MindrianOS relevance:** Beta-tester distribution side-channel. Today: marketplace tag is the only sanctioned path; beta gating requires marketplace.json to advertise the version. Zip channel decouples - hand a tester a single `.zip` without touching marketplace state. Tracked as adoption candidate A5 in SEED-003.
+- **Status:** available
+- **Since:** Claude Code 2.1.128
+
+### `claude plugin validate` (Expanded Manifest)
+- **What:** Plugin validation command accepts a wider set of manifest fields
+- **MindrianOS relevance:** `plugin.json` can declare more metadata that the marketplace honors. Audit current manifest against new accepted fields when planning v1.13.0.
+- **Status:** available
+- **Since:** Claude Code 2.1.120
+
+### Plugin Dependency Auto-Resolution
+- **What:** Plugin dependencies are auto-resolved from configured marketplaces
+- **MindrianOS relevance:** Simplifies coupling between MindrianOS and Brain MCP if Brain ever ships as a separate marketplace plugin (currently bundled).
+- **Status:** available
+- **Since:** Claude Code 2.1.117
+
+### MCP Tool Search
+- **What:** Auto-discovers available MCP tools at 10% context threshold
+- **MindrianOS relevance:** Brain MCP discovery. When Brain is connected, Claude automatically finds Neo4j query tools without explicit configuration.
+- **Status:** available
+- **Since:** 2025 Q4
+
+### MCP `alwaysLoad` Server Config
+- **What:** `alwaysLoad: true` in `.mcp.json` skips tool-search deferral and surfaces server tools from turn 1
+- **MindrianOS relevance:** **Eliminates Brain MCP cold-start window.** Today Larry's first session response is "Brain-blind" until the 10% discovery threshold fires. With `alwaysLoad`, Mode A (Full Loop) per Canon Part 3 starts at turn 1. Single biggest leverage adoption per SEED-003 A1.
+- **Status:** available
+- **Since:** Claude Code 2.1.121
+
+### MCP Auto-Retry on Transient Startup Errors
+- **What:** MCP servers auto-retry transient startup errors up to 3 times
+- **MindrianOS relevance:** Brain MCP reliability improvement. Reduces "Brain unavailable" Tier 0 fallbacks caused by network blips during boot.
+- **Status:** available
+- **Since:** Claude Code 2.1.121
+
+### Concurrent MCP Server Connections (Default)
+- **What:** Multiple MCP servers connect concurrently at startup instead of serially
+- **MindrianOS relevance:** Faster session start when MindrianOS users have Brain + other MCP servers configured (Notion, Gmail, etc.). Net positive for plugin UX.
+- **Status:** available
+- **Since:** Claude Code 2.1.117
+
+### `/mcp` Tool Count + Zero-Tool Flagging
+- **What:** `/mcp` command shows the tool count for connected servers and flags servers that connected with 0 tools
+- **MindrianOS relevance:** Direct diagnostic for Brain MCP failure modes. When a tester says "Brain isn't responding," step 1 becomes `/mcp` - if Brain shows 0 tools, the failure mode is now visible. Candidate for `/mos:doctor --brain` integration.
+- **Status:** available
+- **Since:** Claude Code 2.1.128
+
+### Plugin Hooks
+- **What:** SessionStart, SessionStop, and PostToolUse events available to plugins
+- **MindrianOS relevance:** Intelligence pipeline foundation. Every hook fires plugin scripts that maintain Room state, file insights, and surface proactive findings.
+- **Status:** available
+- **Since:** 2025 Q3
+
+### Statusline in Plugins
+- **What:** Plugins can declare custom statusline scripts for persistent display
+- **MindrianOS relevance:** Context-monitor displays real-time Room health and context budget consumption directly in the CLI status bar.
+- **Status:** available
+- **Since:** 2025 Q4
+
+---
+
+## visualization
+
+### Mermaid Rendering
+- **What:** Built-in Mermaid diagram support for flowcharts, graphs, and sequences
+- **MindrianOS relevance:** Data Room relationship visualization. Knowledge graphs, pipeline flows, and venture stage maps rendered inline.
+- **Status:** available
+- **Since:** 2025 Q3
+
+### SVG Generation
+- **What:** Direct SVG output for vector graphics
+- **MindrianOS relevance:** De Stijl visual assets. Room dashboard graphics, profile documents, and export visuals use SVG for clean rendering.
+- **Status:** available
+- **Since:** 2025 Q3
+
+### HTML Artifact Rendering
+- **What:** Browser-based rich output via localhost serving
+- **MindrianOS relevance:** Data Room dashboard. The De Stijl-styled interactive viewer with knowledge graph, chat panel, and methodology output display.
+- **Status:** available
+- **Since:** 2025 Q4