@jentrix/plugin-claude 0.6.1 → 0.6.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,5 +1,5 @@
1
1
  {
2
2
  "name": "jentrix",
3
3
  "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.",
4
- "version": "0.6.1"
4
+ "version": "0.6.2"
5
5
  }
@@ -54,13 +54,18 @@ wizard; a Project is an optional task label and is never part of it).
54
54
  ```
55
55
 
56
56
  One call returns the description, the links BOTH ways with their titles,
57
- the subtasks, the latest artifact of each type with its id, and the last
58
- five comments. Read it before you touch any code: a linked card is usually
59
- where the prior round's reasoning lives, and its artifacts are the context
60
- you would otherwise reconstruct from scratch. If it prints
61
- `no links · no artifacts · no comments`, the card has nothing to give and
62
- you stop looking that single line is the answer, not an invitation to run
63
- `task get`, `task search` and `comment list` to confirm it.
57
+ the subtasks, the latest artifact of each type with its id, the last five
58
+ comments, and **Related evidence** what OTHER work in this workspace
59
+ already said about this card (learnings, decisions, findings, reports
60
+ ranked by similarity; the align output printed the same block). Read it
61
+ before you touch any code: a linked card is usually where the prior
62
+ round's reasoning lives, its artifacts are the context you would otherwise
63
+ reconstruct from scratch, and a related learning is a mistake you do not
64
+ have to make twice — `jentrix artifact get --artifact-id <id>` reads one in
65
+ full. If it prints `no links · no artifacts · no comments · no related
66
+ evidence`, the card has nothing to give and you stop looking — that single
67
+ line is the answer, not an invitation to run `task get`, `task search` and
68
+ `comment list` to confirm it.
64
69
 
65
70
  Notes for you (the assistant):
66
71
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jentrix/plugin-claude",
3
- "version": "0.6.1",
3
+ "version": "0.6.2",
4
4
  "description": "The official Jentrix plugin for Claude Code: connected-session commands and trusted lifecycle hooks, materialized by the Jentrix CLI (jentrix plugin install claude).",
5
5
  "keywords": [
6
6
  "jentrix",