@jentrix/plugin-claude 0.6.2 → 0.6.3

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.6.2"
+  "version": "0.6.3"
 }

package/commands/jentrix-align.md

@@ -56,8 +56,9 @@ wizard; a Project is an optional task label and is never part of it).
    One call returns the description, the links BOTH ways with their titles,
    the subtasks, the latest artifact of each type with its id, the last five
    comments, and **Related evidence** — what OTHER work in this workspace
-   already said about this card (learnings, decisions, findings, reports
-   ranked by similarity; the align output printed the same block). Read it
+   already said about this card (learnings, decisions, findings, reports;
+   at most five, each at 78 % similarity or more — byte for byte the block
+   the align output printed). Read it
    before you touch any code: a linked card is usually where the prior
    round's reasoning lives, its artifacts are the context you would otherwise
    reconstruct from scratch, and a related learning is a mistake you do not

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jentrix/plugin-claude",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "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",