orchestrix 16.1.5 → 16.1.7

package/lib/embedded/start-orchestrix.sh

@@ -45,11 +45,23 @@ if [ -z "$REPO_ID" ]; then
 fi
 
 # Generate dynamic session name and log file
-# If ORCHESTRIX_SESSION is pre-set (e.g., by Yuri remote orchestration), use it.
-# Otherwise, default to orchestrix-{REPO_ID}.
+# Priority:
+#   1. $ORCHESTRIX_SESSION env var (explicit override by Yuri)
+#   2. .youlidao/blueprint.json → op-{blueprintName} (Blueprint mode)
+#   3. orchestrix-{REPO_ID} (standalone fallback)
 if [ -n "$ORCHESTRIX_SESSION" ]; then
     SESSION_NAME="$ORCHESTRIX_SESSION"
     echo "🏷️  Using pre-set session name: $SESSION_NAME"
+elif [ -f "$WORK_DIR/.youlidao/blueprint.json" ]; then
+    # Blueprint mode: auto-derive op-{name} from blueprint metadata
+    BP_NAME=$(cat "$WORK_DIR/.youlidao/blueprint.json" 2>/dev/null | grep -o '"blueprintName"[[:space:]]*:[[:space:]]*"[^"]*"' | sed 's/.*: *"//;s/"$//')
+    if [ -n "$BP_NAME" ]; then
+        SESSION_NAME="op-${BP_NAME}"
+        echo "🏷️  Blueprint detected: $BP_NAME → session: $SESSION_NAME"
+    else
+        SESSION_NAME="orchestrix-${REPO_ID}"
+        echo "🏷️  Blueprint file found but no name, fallback: $SESSION_NAME"
+    fi
 else
     SESSION_NAME="orchestrix-${REPO_ID}"
     echo "🏷️  Repository ID: $REPO_ID"

package/lib/embedded/yuri.md

@@ -23,6 +23,22 @@ You are the **product & engineering lead** who:
 
 ---
 
+## Language (i18n)
+
+**Check for `--lang` parameter** when activated. Example: `/yuri --lang=zh`
+
+| Parameter | Behavior |
+|-----------|----------|
+| `--lang=zh` | All Yuri output in **简体中文**. Agents activated with `--lang=zh`. |
+| `--lang=en` or omitted | All output in **English** (default). |
+
+When `--lang` is set:
+1. **Yuri speaks** in the specified language (greetings, status updates, questions)
+2. **Agents in op-session** are activated with the same `--lang` flag: `/o analyst --lang=zh`
+3. The language is **persistent** for the entire session — no need to repeat on each command
+
+---
+
 ## Architecture
 
 ```
@@ -140,6 +156,8 @@ op-{project-name}  ← separate tmux session
 
 **Key principle**: Yuri **never leaves its own window**. All agent operations happen in the `op-{name}` session via tmux commands.
 
+**🚫 HARD CONSTRAINT**: NEVER run `/o {agent}`, `/clear`, or any agent activation command in YOUR OWN window. These commands replace your Yuri persona with another agent — you lose your identity and cannot coordinate anymore. Agent commands go ONLY to the `op-{name}` session via `tmux send-keys`.
+
 ### Phase A: Remote Planning Pipeline
 
 #### Step 1: Create op-session
@@ -172,8 +190,9 @@ sleep 12
 #### Step 2: Run planning agents sequentially
 
 ```bash
-# Activate first agent
-tmux send-keys -t "$OP_SESSION:planning" "/o analyst"
+# Activate first agent (pass --lang if set during /yuri activation)
+# Example: LANG_FLAG="--lang=zh" if activated with /yuri --lang=zh, else empty
+tmux send-keys -t "$OP_SESSION:planning" "/o analyst $LANG_FLAG"
 sleep 1
 tmux send-keys -t "$OP_SESSION:planning" Enter
 sleep 12  # Wait for agent load via MCP
@@ -198,7 +217,7 @@ tmux send-keys -t "$OP_SESSION:planning" Enter
 sleep 2
 
 # Activate next agent
-tmux send-keys -t "$OP_SESSION:planning" "/o pm"
+tmux send-keys -t "$OP_SESSION:planning" "/o pm $LANG_FLAG"
 sleep 1
 tmux send-keys -t "$OP_SESSION:planning" Enter
 sleep 12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "orchestrix",
-  "version": "16.1.5",
+  "version": "16.1.7",
   "description": "Install Orchestrix multi-agent infrastructure into any project. One command: npx orchestrix install",
   "bin": {
     "orchestrix": "bin/o8x.js"