orchestrix-yuri 4.8.2 → 4.8.3

package/lib/gateway/router.js

@@ -552,18 +552,35 @@ class Router {
       return { text: '❌ Usage: *change "description of the change"\n\nExample: *change "Add dark mode toggle to settings page"' };
     }
 
-    // Step 1: Ask Claude to assess scope
+    // Step 1: Ask Claude to assess scope — with conversation context + project state
     this.history.append(msg.chatId, 'user', msg.text);
     log.router(`Change request: "${description.slice(0, 80)}..." — assessing scope...`);
 
+    // Build context: recent conversation + project focus
+    const recentMsgs = this.history.getRecent(msg.chatId);
+    const recentContext = recentMsgs.slice(-6).map((m) => `${m.role}: ${m.text.slice(0, 200)}`).join('\n');
+
+    let projectContext = '';
+    try {
+      const focusPath = path.join(projectRoot, '.yuri', 'focus.yaml');
+      if (fs.existsSync(focusPath)) {
+        const focus = yaml.load(fs.readFileSync(focusPath, 'utf8')) || {};
+        projectContext = `Current phase: ${focus.phase || '?'}, step: ${focus.step || '?'}, pulse: ${focus.pulse || '?'}`;
+      }
+    } catch { /* ok */ }
+
     const scopePrompt = `You are assessing a change request for a software project.
 
-Change description: "${description}"
+${projectContext ? `Project state: ${projectContext}\n` : ''}${recentContext ? `Recent conversation:\n${recentContext}\n\n` : ''}Change description: "${description}"
+
+IMPORTANT: Consider the FULL conversation context, not just the description.
+If the user is approving/confirming a previously discussed plan that involves multiple components, stories, or a major redesign — that is medium or large, NOT small.
+"批准" / "ok" / "go ahead" in response to a multi-story plan = large scope.
 
-Based on the description, classify the scope as one of:
-- **small**: ≤5 files affected, no architectural changes, no new dependencies (e.g., UI tweak, bug fix, small feature)
-- **medium**: Cross-component change, needs PO routing and possibly architect review (e.g., new API endpoint, refactoring a module)
-- **large**: Cross-module/database/security change, needs full re-planning (e.g., auth system rewrite, new microservice)
+Classify the scope as one of:
+- **small**: Single-file fix, UI tweak, or isolated change (≤5 files, no architecture impact)
+- **medium**: Cross-component change, needs PO routing (new API endpoint, refactoring a module)
+- **large**: Cross-module change, multi-story plan, major redesign, needs full orchestration
 
 Reply with ONLY one word: small, medium, or large. Nothing else.`;
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "orchestrix-yuri",
-  "version": "4.8.2",
+  "version": "4.8.3",
   "description": "Yuri — Meta-Orchestrator for Orchestrix. Drive your entire project lifecycle with natural language.",
   "main": "lib/installer.js",
   "bin": {