@jentrix/plugin-claude 0.5.5 → 0.5.6

package/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "jentrix",
   "description": "Connect this Claude Code session to a Jentrix project: /jentrix-connect binds the current session (trusted lifecycle hooks supply the session id), /jentrix-align anchors it to a task with an accountable owner, /jentrix-plan, /jentrix-checkpoint, /jentrix-review, /jentrix-status and /jentrix-end wrap the same session operations. Business logic lives in the Jentrix CLI — removing this plugin leaves `jentrix session connect` as the universal fallback.",
-  "version": "0.5.5"
+  "version": "0.5.6"
 }

package/commands/jentrix-align.md

@@ -2,7 +2,7 @@
 description: Align this session to a Jentrix work item (task + accountable owner) with a server-confirmed snapshot
 allowed-tools: Bash(jentrix session:*), Bash(jentrix folder:*), Bash(jentrix task:*), Bash(jentrix column:*), Bash(jentrix tool:*)
 ---
-<!-- Source of truth: cli/plugins/claude. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/claude in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 Anchor THIS session's next work and telemetry to a task with an accountable
 owner (client-runtime v2 — alignment is a narrow flag-driven command, not a

package/commands/jentrix-checkpoint.md

@@ -2,7 +2,7 @@
 description: Write a distilled state-of-play for this session and push it as a typed Jentrix artifact
 allowed-tools: Bash(jentrix push:*), Bash(jentrix session:*), Bash(jentrix task:*), Bash(jentrix column:*)
 ---
-<!-- Source of truth: cli/plugins. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/claude in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 Write down what this session currently knows, and push it.
 

package/commands/jentrix-connect.md

@@ -2,7 +2,7 @@
 description: Connect this Claude Code session to Jentrix (session anchor + capture in the folder's workspace)
 allowed-tools: Bash(jentrix session:*), Bash(jentrix folder:*)
 ---
-<!-- Source of truth: cli/plugins/claude. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/claude in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 Run this exact command with the Bash tool and relay its output to the user:
 

package/commands/jentrix-end.md

@@ -2,7 +2,7 @@
 description: End the connected Jentrix session (pushes the final artifacts, verifies capture, stores the RUN_SUMMARY)
 allowed-tools: Bash(jentrix session:*), Bash(jentrix push:*), Bash(jentrix artifact:*), Bash(jentrix column:*), Bash(jentrix task:*), Bash(jentrix tool:*)
 ---
-<!-- Source of truth: cli/plugins. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/claude in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 End the connected Jentrix session honestly. For an ALIGNED session (the MVP
 pipeline), the typed artifacts ARE the record — push them before closing:

package/commands/jentrix-plan.md

@@ -2,7 +2,7 @@
 description: Turn the opening prompt into a goal and a small set of Jentrix tasks, confirmed by the operator before anything is created
 allowed-tools: Bash(jentrix task:*), Bash(jentrix column:*), Bash(jentrix board:*), Bash(jentrix session:*), Bash(jentrix push:*)
 ---
-<!-- Source of truth: cli/plugins. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/claude in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 Decompose the work the operator just asked for into a goal and a short task
 list, **confirm both before creating anything**, then create them.

package/commands/jentrix-review.md

@@ -2,7 +2,7 @@
 description: Review a Jentrix session's typed artifacts by category (input → plan → decision → output → issue → gap → learning → record), check the readiness contract, and post the verdict as a task comment
 allowed-tools: Bash(jentrix tool:*), Bash(jentrix artifact:*), Bash(jentrix session:*), Bash(jentrix comment:*)
 ---
-<!-- Source of truth: cli/plugins. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/claude in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 Run the category walk over one session's record (docs: Reviewing a session).
 Read-only until the final comment; never modify the tree, the board, or the

package/commands/jentrix-status.md

@@ -2,7 +2,7 @@
 description: Show the connected Jentrix session for this work (capture health included)
 allowed-tools: Bash(jentrix session:*)
 ---
-<!-- Source of truth: cli/plugins. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/claude in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 Run `jentrix session status` with the Bash tool (append the session id if the
 user gave one) and relay the output verbatim, including any capture-pending

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jentrix/plugin-claude",
-  "version": "0.5.5",
+  "version": "0.5.6",
   "description": "The official Jentrix plugin for Claude Code: connected-session commands and trusted lifecycle hooks, materialized by the Jentrix CLI (jentrix plugin install claude).",
   "keywords": [
     "jentrix",
@@ -9,14 +9,14 @@
     "sessions",
     "agents"
   ],
-  "homepage": "https://tm.jentrix.ai/docs/cli",
+  "homepage": "https://github.com/jentrix-au/jentrix",
   "bugs": {
-    "url": "https://github.com/jentrix-au/task-manager/issues"
+    "url": "https://github.com/jentrix-au/jentrix/issues"
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/jentrix-au/task-manager.git",
-    "directory": "cli/plugins/claude"
+    "url": "git+https://github.com/jentrix-au/jentrix.git",
+    "directory": "plugins/claude"
   },
   "license": "MIT",
   "author": "Jentrix",