claude-nexus 0.31.1 → 0.31.2

package/.claude-plugin/marketplace.json

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

package/.claude-plugin/plugin.json

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

package/agents/lead.md

@@ -262,7 +262,7 @@ For questions that can be answered briefly, answer directly without structure.
 
 ### Subagent ID Recording Practice
 
-Every time a subagent is spawned, record its id (either returned by the harness spawn tool or the `name` the Lead assigned) through one of the paths below. Without this, `nx_plan_resume` / `nx_task_resume` will have no resume candidates to return.
+Every time a subagent is spawned, record the agent id returned by the harness spawn tool through one of the paths below. Do not substitute a human-readable assigned name; names are for active-session messaging only and are not a safe resume identifier for completed sessions. Without this, `nx_plan_resume` / `nx_task_resume` will have no resume candidates to return.
 
 - HOW participation → pass `agent_id` to `nx_plan_analysis_add(issue_id, role, agent_id=<id>, summary)` (Step 4 of nx-plan / nx-auto-plan skill).
 - Task execution → store via `nx_task_update(id, owner={role, agent_id=<id>, resume_tier=<ephemeral|bounded|persistent>})` (Step 2 of nx-run skill).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-nexus",
-  "version": "0.31.1",
+  "version": "0.31.2",
   "type": "module",
   "description": "Claude Code plugin for nexus-core agent orchestration",
   "author": "kih",
@@ -40,7 +40,7 @@
     "settings.json"
   ],
   "devDependencies": {
-    "@moreih29/nexus-core": "^0.19.0",
+    "@moreih29/nexus-core": "^0.19.1",
     "@types/bun": "^1.3.0",
     "@types/node": "^22.0.0",
     "typescript": "^5.6.0"

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

@@ -72,7 +72,7 @@ Issues must be processed one at a time. For each issue:
 2. If needed, spawn HOW subagents for independent analysis.
    - If reusing context from a prior HOW session for the same role is advantageous, check resume routing information with `nx_plan_resume` first.
    - If resumable, continue with the existing session; otherwise, spawn fresh.
-3. When HOW results return, record them on the issue with `nx_plan_analysis_add(issue_id, role, agent_id=<id from spawn>, summary)`. The `agent_id` is the value `nx_plan_resume` will return on a future resume request for the same role, so always pass it.
+3. When HOW results return, record them on the issue with `nx_plan_analysis_add(issue_id, role, agent_id=<id from spawn>, summary)`. The `agent_id` is the value `nx_plan_resume` will return on a future resume request for the same role, so always pass the agent id obtained from the spawn tool response. Do not substitute a human-readable assigned name; names are only for messaging a currently running subagent and are not a safe resume identifier for a completed session.
 4. **Lead internal deliberation**: enumerate candidate options, compare pros/cons and trade-offs, and select the most reasonable one. Do not output comparison tables or option presentations.
 5. Proceed immediately to Step 5 to record the decision.
 

package/skills/nx-plan/SKILL.md

@@ -73,7 +73,7 @@ Issues must be processed one at a time. For each issue:
 2. If needed, spawn HOW subagents for independent analysis.
    - If reusing context from a prior HOW session for the same role is advantageous, check resume routing information with `nx_plan_resume` first.
    - If resumable, continue with the existing session; otherwise, spawn fresh.
-3. When HOW results return, record them on the issue with `nx_plan_analysis_add(issue_id, role, agent_id=<id from spawn>, summary)`. The `agent_id` is the value `nx_plan_resume` will return on a future resume request for the same role, so always pass the id obtained from the spawn tool response (or the name the Lead assigned). This record feeds both future resume paths and Step 7 task decomposition.
+3. When HOW results return, record them on the issue with `nx_plan_analysis_add(issue_id, role, agent_id=<id from spawn>, summary)`. The `agent_id` is the value `nx_plan_resume` will return on a future resume request for the same role, so always pass the agent id obtained from the spawn tool response. Do not substitute a human-readable assigned name; names are only for messaging a currently running subagent and are not a safe resume identifier for a completed session. This record feeds both future resume paths and Step 7 task decomposition.
 4. After synthesis, present a comparison table and recommendation.
 5. Receive the user's response and record the decision.