claude-nexus 0.30.0 → 0.31.0

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
     {
       "name": "claude-nexus",
       "description": "Claude Code plugin for nexus-core agent orchestration",
-      "version": "0.30.0",
+      "version": "0.31.0",
       "author": {
         "name": "kih"
       },

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-nexus",
-  "version": "0.30.0",
+  "version": "0.31.0",
   "description": "Claude Code plugin for nexus-core agent orchestration",
   "author": {
     "name": "kih"

package/README.en.md

@@ -61,12 +61,12 @@ Claude Code does not let a plugin auto-configure the user's `statusLine`, so reg
 {
   "statusLine": {
     "type": "command",
-    "command": "bunx claude-nexus-statusline"
+    "command": "bunx claude-nexus"
   }
 }
 ```
 
-`npx -y claude-nexus-statusline` works the same way. The first call downloads the package to the local cache; subsequent calls run from that cache.
+`npx -y claude-nexus` works the same way. The first call downloads the package to the local cache; subsequent calls run from that cache.
 
 ### Global install (fastest startup)
 
@@ -78,7 +78,7 @@ bun add -g claude-nexus    # or npm i -g claude-nexus
 {
   "statusLine": {
     "type": "command",
-    "command": "claude-nexus-statusline"
+    "command": "claude-nexus"
   }
 }
 ```

package/README.md

@@ -53,7 +53,7 @@ Claude Code 안에서 플러그인 마켓플레이스로 설치한다.
 
 플러그인은 2줄 statusline 스크립트를 함께 배포한다. 첫 줄은 `◆Nexus vX.Y.Z`·모델·프로젝트·git 브랜치(staged/unstaged), 둘째 줄은 컨텍스트 사용률과 5h/7d 사용 한도 게이지(리셋까지 남은 시간). Claude Pro·Max OAuth 세션에서만 5h/7d가 표시되며, 로컬의 여러 Claude 세션이 `~/.claude/.usage_cache`를 공유하므로 API 중복 호출 없이 경합이 방지된다.
 
-Claude Code는 플러그인이 사용자 `statusLine`을 자동 등록하는 걸 허용하지 않으므로, 별도 CLI로 배포된 `claude-nexus-statusline`을 본인의 `~/.claude/settings.json`에 등록한다.
+Claude Code는 플러그인이 사용자 `statusLine`을 자동 등록하는 걸 허용하지 않으므로, 별도 CLI로 배포된 `claude-nexus`를 본인의 `~/.claude/settings.json`에 등록한다.
 
 ### bunx 또는 npx (설치 불필요)
 
@@ -61,12 +61,12 @@ Claude Code는 플러그인이 사용자 `statusLine`을 자동 등록하는 걸
 {
   "statusLine": {
     "type": "command",
-    "command": "bunx claude-nexus-statusline"
+    "command": "bunx claude-nexus"
   }
 }
 ```
 
-`npx -y claude-nexus-statusline`도 동일하게 동작한다. 최초 호출 1회만 패키지를 로컬 캐시에 받고, 이후 호출은 캐시에서 즉시 실행된다.
+`npx -y claude-nexus`도 동일하게 동작한다. 최초 호출 1회만 패키지를 로컬 캐시에 받고, 이후 호출은 캐시에서 즉시 실행된다.
 
 ### 전역 설치 (가장 빠른 시작 시간)
 
@@ -78,7 +78,7 @@ bun add -g claude-nexus    # 또는 npm i -g claude-nexus
 {
   "statusLine": {
     "type": "command",
-    "command": "claude-nexus-statusline"
+    "command": "claude-nexus"
   }
 }
 ```

package/dist/mcp/server.js

@@ -20193,13 +20193,10 @@ var planUpdateTool = {
 var planDecideTool = {
   group: "plan",
   name: "nx_plan_decide",
-  description: "Record a decision for a plan issue",
+  description: "Record the final decision for a plan issue",
   inputSchema: {
     issue_id: numberType().describe("Issue ID to decide"),
-    decision: stringType().describe("Decision text"),
-    how_agents: arrayType(stringType()).optional().describe("Names of HOW agents that contributed analysis"),
-    how_summary: recordType(stringType(), stringType()).optional().describe("Summary of each agent's key input"),
-    how_agent_ids: recordType(stringType(), stringType()).optional().describe("Mapping from agent name to agent ID")
+    decision: stringType().describe("Decision text")
   }
 };
 var planResumeTool = {
@@ -20400,7 +20397,7 @@ var planToolBindings = [
   },
   {
     definition: planDecideTool,
-    handler: async ({ issue_id, decision, how_agents, how_summary, how_agent_ids }) => {
+    handler: async ({ issue_id, decision }) => {
       const pPath = planPath();
       let responsePayload = {};
       await updateJsonFileLocked(pPath, null, (raw) => {
@@ -20416,23 +20413,6 @@ var planToolBindings = [
         }
         issue2.status = "decided";
         issue2.decision = decision;
-        if (how_agents && how_agents.length > 0) {
-          const now = new Date().toISOString();
-          if (!issue2.analysis) {
-            issue2.analysis = [];
-          }
-          for (const agentName of how_agents) {
-            const entry = {
-              role: agentName,
-              summary: how_summary?.[agentName] ?? "",
-              recorded_at: now
-            };
-            if (how_agent_ids?.[agentName]) {
-              entry.agent_id = how_agent_ids[agentName];
-            }
-            issue2.analysis.push(entry);
-          }
-        }
         const allComplete = raw.issues.every((candidate) => candidate.status === "decided");
         const remaining = raw.issues.filter((candidate) => candidate.status !== "decided");
         responsePayload = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-nexus",
-  "version": "0.30.0",
+  "version": "0.31.0",
   "type": "module",
   "description": "Claude Code plugin for nexus-core agent orchestration",
   "author": "kih",
@@ -17,7 +17,7 @@
     "node": ">=20"
   },
   "bin": {
-    "claude-nexus-statusline": "./scripts/statusline.mjs"
+    "claude-nexus": "./scripts/statusline.mjs"
   },
   "scripts": {
     "build": "bun run sync && bun run build:bundle",
@@ -41,7 +41,7 @@
     "settings.json"
   ],
   "devDependencies": {
-    "@moreih29/nexus-core": "^0.18.2",
+    "@moreih29/nexus-core": "^0.19.0",
     "@types/bun": "^1.3.0",
     "@types/node": "^22.0.0",
     "typescript": "^5.6.0"

package/skills/nx-auto-plan/SKILL.md

@@ -96,7 +96,7 @@ Use `nx_plan_decide` to mark the issue as decided. The decision text MUST includ
 - The selected approach and its rationale
 - The rejected alternatives and their dismissal reasons
 
-If HOW subagents participated in the issue, bundle their contribution information so it can be referenced in future resumes and Step 7 task decomposition.
+`nx_plan_decide` records only the final decision text and decision state — it does **not** append to `analysis`. If HOW subagents participated, their analysis and resume-routing records must already have been written via `nx_plan_analysis_add` in Step 4, and Step 7 should reference those records directly.
 
 If the decision creates follow-up questions or derived issues, add them with `nx_plan_update` and move to Step 6. Do not ask the user for confirmation.
 

package/skills/nx-plan/SKILL.md

@@ -111,7 +111,7 @@ Issues must be processed one at a time. For each issue:
 
 ### Step 5: Record Decision
 
-When a decision is reached, use `nx_plan_decide` to mark the issue as decided. If HOW subagents participated in the issue, bundle their contribution information so it can be referenced in future resumes and Step 7 task decomposition.
+When a decision is reached, use `nx_plan_decide` to mark the issue as decided. `nx_plan_decide` records only the final decision text and decision state — it does **not** add to `analysis`. All HOW analysis and resume routing records must already be stored via `nx_plan_analysis_add` in Step 4.
 
 - Immediately after recording, check overall progress with `nx_plan_status` and announce the next issue in one line.
 - Check whether new follow-up questions have emerged, and if so, add follow-up issues with `nx_plan_update`.