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

package/skills/room/SKILL.md

@@ -0,0 +1,381 @@
+---
+name: room
+description: View, launch, or navigate the Data Room
+license: BSL-1.1. See LICENSE for complete terms (Business Source License 1.1, Change Date 2030-04-16 to Apache License 2.0).
+help_jtbd: "Open your current room's view in this terminal."
+argument-hint: "[overview|<section>]"
+body_shape: C
+hitl_shape: "F.1"
+hitl_why: "Room navigation offers one next move from the current room."
+# Phase 267.3-07, ruled in 267.3-CLASSIFICATION.md (Row 11): first delivery at commands/room.md:121, the default overview's Semantic Tree, a predictable structural readout of what the navigator has already filed.
+interactive_first_reward: "--none (diagnostic surface)"
+body_shape_overview: B (Semantic Tree)
+body_shape_section: C (Room Card)
+serves_jtbd: ["audit-room"]
+teaching: "When you need to view or launch the active Data Room, /mos:room opens the room view with its current state. The default entry point for room navigation."
+ui_reference: skills/ui-system/SKILL.md
+allowed-tools: Read Write Bash Glob AskUserQuestion
+# --- Phase 172-16 CIRS R1 WIRE (Canon Part 11; navigator-directed 2026-06-23) ---
+connector:
+  connects_to_spine: true
+  sensor_triggers: []
+  reach_id: context_block
+  sub_mode: room-view
+  framework: null
+  posture: hold
+  hierarchy_rank: 15
+  filing: memory_event_only
+  plan_gated: false
+  web_scope: null
+  surface: F.1
+---
+
+<!-- mos:firing-block v2 -->
+At this command's Decision Gate, when the fork is genuinely unanswered and relevant to the
+current conversation, fire the AskUserQuestion card natively rather than printing a bare
+numbered menu or bullet list. Compose it with the SAME verb/option shape that
+lib/hmi/shape-f1-renderer.cjs (renderShapeF1) produces and that lib/hmi/selector-dispatcher.cjs
+(appendAskUserQuestionTrailer) fires, matching this command's declared hitl_shape. Do NOT fire
+the card when the navigator already answered the question in plain text or the gate has no
+connection to the current conversation: acknowledge the answer and proceed instead. Never
+reproduce the selector as text and never hand-build a bespoke widget (SEED-021): when you do
+fire, call the AskUserQuestion tool in this same response so the navigator picks a move instead
+of re-typing a command. Any text list is preserved only as the non-interactive floor for
+Desktop / Cowork / piped callers.
+<!-- /mos:firing-block -->
+
+# /mos:room
+
+You are Larry. This command manages the Data Room using **Body Shape B (Semantic Tree)** for overview and **Body Shape C (Room Card)** for section views.
+
+## UI Format
+
+- **overview subcommand:** Body Shape B -- Semantic Tree (folder tree with meaning symbols)
+- **[section] subcommand:** Body Shape C -- Room Card (wiki-style with graph relationships)
+- **Reference:** `skills/ui-system/SKILL.md`
+- All subcommands follow the 4-zone anatomy: Header Panel, Content Body, Intelligence Strip (conditional), Action Footer (NEVER omitted)
+
+Parse the user's input to determine which subcommand to execute. If no subcommand is given, default to **overview** (text-based).
+
+## Subcommand: view
+
+**Trigger:** `/mos:room view` or `/mos:room dashboard`
+
+### Step 1: Check for Room
+
+Run `bash "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/scripts/resolve-room"` to find the active room. If it exits non-zero (no room found), use the 3-line error format (per D-24):
+```
+x No Data Room found
+  Why: No room under ~/MindrianRooms/ or legacy room/ in workspace
+  Fix: /mos:new-project
+```
+
+STOP.
+
+### Step 2: Launch Dashboard
+
+Run the serve-dashboard script:
+
+```bash
+bash "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/scripts/serve-dashboard"
+```
+
+### Step 3: Confirm to User
+
+> "Data Room dashboard is running. Check your browser for the knowledge graph."
+>
+> "Use the chat box to ask about gaps, contradictions, or themes."
+>
+> "Come back here when done -- server stops automatically."
+
+## Subcommand: overview (default)
+
+**Trigger:** `/mos:room` (no subcommand) or `/mos:room overview`
+
+### Step 1: Check for Room
+
+Run `bash "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/scripts/resolve-room"` to find the active room path. If it exits non-zero (no room found), use the 3-line error format:
+```
+x No Data Room found
+  Why: No room under ~/MindrianRooms/ or legacy room/ in workspace
+  Fix: /mos:new-project
+```
+
+STOP.
+
+### Step 2: Read Room State
+
+Read `STATE.md` from the resolved room path for the computed overview. Also read each section's `ROOM.md` for identity and purpose.
+
+### Step 3: Render 4-Zone Output (Shape B: Semantic Tree)
+
+**Zone 1 -- Header Panel:**
+```
+-- [Room Name] -- ~/MindrianRooms/[name]/ -- [Venture Stage] --
+```
+
+Show the simplified `~/MindrianRooms/[name]/` path in the header. For legacy unmigrated rooms, show the actual relative path instead.
+
+**Zone 2 -- Content Body (Shape B: Semantic Tree):**
+
+Display sections as a meaningful tree. Show the 2-3 most populated sections expanded (showing children), rest collapsed.
+
+Symbols:
+- `▼` = expanded (has entries, showing children)
+- `▶` = collapsed, has content
+- `▷` = collapsed, empty
+- `├─` for non-last sibling, `└─` for last sibling
+- `✓` complete artifact, `•` draft artifact
+
+```
+  ▼ room/
+  ├─ ▼ problem-definition/          3 entries
+  │  ├─ ✓ domain-exploration.md     2026-03-20
+  │  ├─ • trend-analysis.md         2026-03-21
+  │  └─ • assumption-map.md         2026-03-22
+  ├─ ▶ market-analysis/             1 entry
+  ├─ ▷ solution-design/             empty
+  ├─ ▶ business-model/              2 entries
+  ├─ ▷ competitive-analysis/        empty
+  ├─ ▶ team-execution/              2 entries
+  ├─ ▷ legal-ip/                    empty
+  └─ ▷ financial-model/             empty
+```
+
+Entry count shown inline with section folders. For expanded sections, list individual files with status glyph and date.
+
+After the tree, show a summary line:
+```
+  [X] sections with content, [Y] empty.
+```
+
+Plus a brief Larry-voice observation about what's strong or missing.
+
+**Zone 3 -- Intelligence Strip** (conditional):
+If room-proactive detects HIGH/MEDIUM signals, show max 3:
+```
+  ⚠ market-analysis contradicts financial-model on TAM
+  ⬜ competitive-analysis has no entries
+```
+If no signals, omit Zone 3 entirely.
+
+**Zone 4 -- Action Footer (NEVER omit):**
+```
+  ▶ /mos:room problem-definition    Dive into your strongest section
+  ▷ /mos:status                     See progress bars
+  ▷ /mos:suggest-next               Get framework recommendations
+```
+
+## Subcommand: [section] (Room Card)
+
+**Trigger:** `/mos:room [section-name]` (e.g., `/mos:room problem-definition`)
+
+### Step 1: Validate Section
+
+Run `bash "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/scripts/resolve-room"` to find the active room. If no room found, use 3-line error format. If the section doesn't exist in the resolved room path, show:
+```
+x Section not found: [section-name]
+  Why: No room/[section-name]/ directory
+  Fix: /mos:room add [section-name]
+```
+
+### Step 2: Read Dual Context
+
+Read `room/[section]/ROOM.md` for identity and purpose.
+Read `room/[section]/MINTO.md` for reasoning pyramid (if exists).
+Read entries in the section directory.
+
+### Step 3: Render 4-Zone Output (Shape C: Room Card)
+
+**Zone 1 -- Header Panel:**
+```
+-- [Room Name] -- [section-name] -- [Venture Stage] --
+```
+
+**Zone 2 -- Content Body (Shape C: Room Card):**
+
+Wiki-style card for a single section:
+```
+  Governing Thought:
+  "[governing thought from MINTO.md, if available]"
+
+  Entries ([N]):
+  ├─ ✓ domain-exploration.md     2026-03-20  deep
+  ├─ • trend-analysis.md         2026-03-21  quick
+  └─ • assumption-map.md         2026-03-22  deep
+
+  Graph:
+  ├─ INFORMS  market-analysis (2 edges)
+  ├─ CONTRADICTS  financial-model (1 edge)
+  └─ CONVERGES  solution-design (1 edge)
+
+  MINTO Health: ✓  Governing thought + 3 arguments + evidence
+```
+
+Rules:
+- Governing thought from MINTO.md (quoted). If no MINTO.md, show "No governing thought defined yet."
+- Entries listed with status glyph (`✓` complete, `•` draft), filename, date, depth
+- Graph section shows LazyGraph edge types and counts. If no LazyGraph data, show "No graph connections yet."
+- MINTO health assessment: `✓` healthy, `•` partial, `--` missing
+
+If the section is empty, show starter questions from ROOM.md body:
+```
+  Status: Empty
+
+  Starter questions:
+  ├─ What specific problem are you solving, and for whom?
+  ├─ Why hasn't this been solved before?
+  └─ How painful is this problem -- would someone pay to fix it today?
+```
+
+**Zone 3 -- Intelligence Strip** (conditional):
+Floating signal badge if proactive intelligence exists for this section:
+```
+  ⚠ Contradicts financial-model on market size assumption
+  ⚡ "municipal water" theme converges with 2 other sections
+```
+
+**Zone 4 -- Action Footer (NEVER omit):**
+```
+  ▶ /mos:room market-analysis     Follow the INFORMS edge
+  ▷ /mos:open domain-exploration  Read the deepest entry
+  ▷ /mos:challenge-assumptions    Test your claims
+```
+
+Actions reference graph edges when possible.
+
+## Subcommand: add
+
+**Trigger:** `/mos:room add {name}` or `/mos:room add {parent}/{name}`
+
+### Step 1: Validate
+
+- Run `bash "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/scripts/resolve-room"` to find the active room. If no room found, use 3-line error format.
+- If the target directory already exists:
+  ```
+  x Room already exists: [path]
+    Why: room/[path]/ directory already present
+    Fix: /mos:room [path]
+  ```
+
+### Step 2: Create Room
+
+Create the directory and ROOM.md:
+
+```bash
+mkdir -p "room/{path}"
+```
+
+Write a ROOM.md with:
+- YAML frontmatter: section name, purpose (infer from the name), stage_relevance
+- Body: 1-2 sentence description, 2-3 starter questions relevant to the room name
+
+### Step 3: Confirm (Shape E mini-report)
+
+```
+  Action: room add
+  Created: room/[path]/
+
+  ▶ /mos:room [path]               View the new section
+  ▷ /mos:explore-domains           Start filling it
+```
+
+Larry adds a brief observation about the addition.
+
+## Subcommand: linkify
+
+**Trigger:** `/mos:room linkify` or `/mos:room linkify <room-name>`
+
+### Step 1: Check for Room
+
+Run `bash "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/scripts/resolve-room"` to find the active room. If it exits non-zero, use the 3-line error format:
+```
+x No Data Room found
+  Why: No room under ~/MindrianRooms/ or legacy room/ in workspace
+  Fix: /mos:new-project
+```
+
+STOP.
+
+### Step 2: Warn Before Mutation
+
+Linkify modifies room files IN PLACE -- no export, no copy. Show the warning:
+
+```
+  ! Linkify will inject wikilinks, branded footers, and content reformatting
+    into files in {room path} directly. This is not reversible via this command.
+
+    Continue? (y/N)
+```
+
+If user declines, abort with no changes.
+
+### Step 3: Run Linkify
+
+```bash
+node bin/mindrian-tools.cjs room linkify {room-name if provided}
+```
+
+The router forwards to scripts/vault-export-orchestrator.cjs with `--in-place`, which runs the same 7-script pipeline on the source room without the copy step. The orchestrator prints `[vault] >>>` progress lines. Let them stream through.
+
+### Step 4: Confirm (Shape E Mini Report)
+
+```
+  Action: room linkify (in-place)
+  Room:   {room path}
+  Files:  {N} markdown files touched
+  Added:  wikilinks, branded footers, Welcome doc, VAULT-RULES.md
+
+  Your room is now Obsidian-ready. Open it in Obsidian to see wikilinks and the graph view.
+
+  > /mos:vault                         Export to a separate vault folder instead
+  > /mos:room view                     Launch the live dashboard
+```
+
+Larry adds a brief observation about what changed. Example:
+- "Wikilinks injected across 14 team references and 9 section cross-links. Your room graph just gained structure."
+
+## Subcommand: export
+
+**Trigger:** `/mos:room export` or `/mos:room export --format standalone`
+
+### Step 1: Check for Room
+
+If no `room/` directory exists, use 3-line error format.
+
+### Step 2: Generate Export
+
+Run the export generation script:
+
+```bash
+node "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/scripts/generate-export.cjs" "./room"
+```
+
+This generates a self-contained HTML file at `room/exports/YYYY-MM-DD-{room-name}.html`.
+
+### Step 3: Confirm (Shape E mini-report)
+
+```
+  Action: export
+  Format: Standalone HTML (De Stijl Mondrian grid + 4 views)
+  Output: room/exports/{filename}.html
+  Sections: [X] with content, [Y] empty
+  Intelligence: [N] gaps, [M] convergence themes, [K] contradictions
+
+  Open in any browser -- no server needed. Share with investors, mentors, or team.
+
+  ▶ /mos:room view                    Launch the live dashboard
+  ▷ /mos:status                       Check overall progress
+```
+
+Larry adds a brief observation about the export quality (e.g., "Three empty sections will stand out to an investor -- consider filling them first.").
+
+## Voice Rules
+
+- Larry's voice throughout. Terse, structural, confident, action-oriented.
+- For overview: informative but concise. Trees and structure are the content.
+- For section view: let the data speak. Governing thought is the lead.
+- For add: confirm with a relevant observation, not just "done."
+- For export: frame it as preparation for a real audience.
+- **Banned phrases (per D-23):** "Great question!", "I'd be happy to help", "It's important to note", "Let me explain", sentences starting with "I"
+- NO EMOJI. Use only the 12 glyphs from the symbol vocabulary.

package/skills/room-passive/SKILL.md

@@ -0,0 +1,174 @@
+---
+name: room-passive
+description: >
+  Data Room awareness, filing intelligence, and passive monitoring. Active when
+  room/ exists -- gives Larry project structure context and filing guidance.
+license: BSL-1.1. See LICENSE for complete terms (Business Source License 1.1, Change Date 2030-04-16 to Apache License 2.0).
+# activation: "resolve_room:active"  <- INERT. Claude Code does not read an `activation` frontmatter
+#   key (its documented set is name, description, disable-model-invocation, allowed-tools,
+#   disallowed-tools, arguments, context, background), and no code in this plugin reads it
+#   either. Kept as a comment so the INTENT survives; it never gated anything. Pinned by
+#   tests/test-skill-frontmatter-inert-keys.cjs.
+paths:
+  - "**/STATE.md"
+  - "**/ROOM.md"
+  - "**/MindrianRooms/**"
+  - "**/.rooms/**"
+# --- Phase 172-06 CIRS R1 exclude (Canon Part 11) ---
+connector:
+  excluded: true
+  reason: "Ambient always-on infra. The passive room-listening skill runs every turn to capture insights; an always-on capture substrate with no discrete trigger."
+---
+
+# Room Passive -- Awareness + Filing Intelligence
+
+## Activation
+
+This skill activates when `scripts/resolve-room` finds any active room. The resolver checks (in order): central registry at `~/MindrianRooms/.rooms/registry.json`, directory scan under `~/MindrianRooms/`, workspace registry, and legacy `room/` fallback. If any strategy returns a path, this skill is active.
+
+The resolved room path (absolute) is the working room for all operations below.
+
+## Room Awareness
+
+Be aware of the active room's structure: reference specific sections, note empty sections as opportunities, use entry counts for completeness, read ROOM.md for section purpose. The room lives under `~/MindrianRooms/[name]/` (or legacy `room/` for unmigrated workspaces).
+
+## Room Structure
+
+8 DD-aligned sections: problem-definition, market-analysis, solution-design, business-model, competitive-analysis, team-execution, legal-ip, financial-model
+
+Plus: `team/` (members/mentors/advisors with ICM nested profiles), `meetings/` (YYYY-MM-DD-{name}/ archives)
+
+## ICM Layer 0 Mandate (MANDATORY)
+
+Every directory in the Data Room MUST have an identity file (ROOM.md). No exceptions.
+This is ICM Layer 0 -- it answers "Where am I? What belongs here? What does NOT belong here?"
+
+### The Rule
+When creating ANY new directory -- whether a room section, sub-room, team profile folder,
+meeting archive, opportunity bank, or any other folder -- ALWAYS create a ROOM.md inside it.
+
+### ROOM.md Template
+```markdown
+---
+icm_layer: 0
+section: {section-name or folder-type}
+parent: {parent-room-or-directory}
+---
+# {Folder Display Name}
+
+{One sentence: what this folder contains.}
+
+## What Belongs Here
+- {2-4 bullet points}
+
+## What Does NOT Belong Here
+- {2-3 redirects to correct locations}
+```
+
+### Enforcement
+- When filing an artifact to a section that lacks ROOM.md, create it FIRST
+- When creating a new sub-room, create ROOM.md for every section directory
+- When running /mos:room or room analysis, flag directories missing ROOM.md as ICM gaps
+- Scripts that create directories (create-speaker-profile, create-room, etc.) MUST generate ROOM.md
+- This applies to ALL rooms, ALL sub-rooms, ALL sections, ALL special folders -- no exceptions
+
+### Why This Matters
+Without Layer 0, Claude (on any surface -- CLI, Desktop, Cowork) cannot determine what belongs
+in a folder. This leads to misfiling, duplication, and lost context. ROOM.md is the folder's
+contract with every agent that touches it.
+
+## Filing Intelligence
+
+When methodology produces an artifact:
+1. Suggest correct room from methodology's default (see `${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/references/methodology/index.md`)
+2. Confirm before filing -- NEVER file silently
+3. Uncertain classification: analyze content and suggest best section
+4. Cross-room relevance: file to primary, mention secondary
+
+### Wikilink Injection on Filing (NATIVE-02)
+
+**Rule:** Whenever you write a new artifact into the active room (via any skill, command, or direct edit), the artifact MUST arrive with wikilinks already present. Do NOT leave wikilinking to a retroactive batch pass -- wikilinks are part of the artifact's birth, not a later cleanup.
+
+**How (preferred -- call the wrapper):**
+
+After writing a new file, immediately run:
+```bash
+node "${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?MindrianOS install root not found. Set MINDRIAN_OS_ROOT (see lib/core/active-plugin-root.cjs) or run from Claude Code.}}/scripts/wikilink-file.cjs" "$ROOM_DIR" "$NEW_FILE_PATH" \
+  [--filed-to-target="market-analysis/2026-04-09-tam.md"] \
+  [--meeting-slug="2026-04-09-align-strategy-session"]
+```
+
+The wrapper loads `lib/vault/room-scanner.cjs` + `lib/vault/wikilink-builder.cjs`, scans the room once, injects team-name wikilinks into the new file's body, and (if a meeting slug is given) appends a filed-to footer. Errors are logged to stderr but never abort filing -- backward compatibility is non-negotiable.
+
+**How (manual -- when running the wrapper is not feasible):**
+
+Inject wikilinks directly while writing the artifact:
+
+- **Team members:** First occurrence of each team member display name in the body -> `[[team/{category}/{slug}/PROFILE.md|{Display Name}]]`. Longer names beat prefixes (e.g., "Avital Leibovich" wins over "Avital"). Never self-link (the person's own PROFILE.md stays plain).
+- **Section references** in STATE.md / ROOM.md -> `[[{section}/ROOM.md|{section}]]`
+- **Filed-to stubs** (one stub per filed artifact under `meetings/{slug}/filed-to/`) -> include BOTH lines:
+  ```
+  -> Full artifact: [[{section}/{artifact-filename}.md]]
+  <- Source meeting: [[meetings/{slug}/summary.md|{Meeting Display Name}]]
+  ```
+- **Meeting display name** is the slug with the `YYYY-MM-DD-` prefix stripped and the remainder title-cased ("2026-04-09-align-strategy-session" -> "Align Strategy Session").
+
+**Graceful fallback (WIKI-06):** If the room has zero team profiles or zero meetings, skip that link type. Do not crash, do not invent targets.
+
+**Idempotence:** Never double-link. If `[[...|Name]]` already exists for a display name, don't add another occurrence of the same link. If a filed-to footer line already exists, do not duplicate it.
+
+**Canonical builder module:** See `lib/vault/wikilink-builder.cjs` -- it exports `buildTeamLinks`, `buildSectionLink`, `buildMeetingLink`, `buildFiledToFooter`, `injectFiledToFooter` as pure functions. The `scripts/wikilink-file.cjs` wrapper is the preferred filing-time entry point. Phase 76's retroactive `scripts/vault-wikilink-injector.cjs` remains available for whole-room sweeps.
+
+## Active Room Lock (Multi-Room)
+
+When `.rooms/registry.json` exists:
+- Resolve active room before ANY write
+- Target path MUST be inside active room
+- Block cross-room writes with error + fix (`/mos:rooms open [target]`)
+- Non-room writes always allowed
+- Admin commands room-agnostic
+
+Single-room mode (no registry): skip lock checks.
+
+## Provenance Metadata
+
+Every filed artifact MUST include frontmatter: methodology, created, depth, problem_type, venture_stage, room_section.
+
+## Meeting-Sourced Artifacts
+
+`source: transcript` artifacts carry extended metadata: speaker, speaker_role, meeting_date, segment_type, confidence, assumptions, perspective, cascade_sections.
+
+- Cross-linked to topic section AND speaker profile
+- Track assumption validity across sessions
+- Cascade awareness via `cascade_sections:` field
+
+For ad-hoc meeting mentions, suggest `/mos:file-meeting` for structured filing.
+
+## UDS Cross-Instance Listener Stubs (READY-03)
+
+<!-- UDS (Unified Data Sharing) is a future Anthropic feature for cross-instance state sharing.
+     When UDS ships, room-passive should listen for external room updates from other Claude instances
+     (e.g., a Cowork teammate files an artifact, and your Desktop session sees it).
+
+     Activation conditions:
+     1. Environment variable `tengu_harbor` is set to `true` (UDS feature gate)
+     2. OR file `room/.mindrian/uds-active` exists
+     3. AND room has multi-user configuration in room/.mindrian/uds-config.json
+
+     When active, room-passive should:
+     - Poll room/.mindrian/uds-inbox/ for incoming state diffs from other instances
+     - Apply diffs to local room state (new artifacts, updated STATE.md sections)
+     - Surface changes to user: "A teammate filed a new market analysis entry. Want to review?"
+     - Write acknowledgments to room/.mindrian/uds-outbox/ for sync confirmation
+
+     Until UDS ships, this is a no-op. The stubs exist so that:
+     - The room-passive skill already documents the integration surface
+     - When UDS activates via GrowthBook gate, only the transport layer needs implementation
+     - The skill instructions (what to do with incoming changes) are already defined
+-->
+
+When `tengu_harbor` env var is `true` or `room/.mindrian/uds-active` exists, check `room/.mindrian/uds-inbox/` for cross-instance updates on session start. Surface new entries to user before standard greeting. This is a future capability -- currently a no-op until UDS ships.
+
+## Wiki Dashboard Awareness
+
+When room has 2+ sections with content, mention wiki once per session after filing, analyzing, or first methodology output: "`/mos:wiki` for live wiki view." Sharing: `/mos:wiki --export` for static HTML bundle.