@jentrix/plugin-codex 0.3.1 → 0.3.3

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.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/plugins/jentrix/.codex-plugin/plugin.json +1 -1
  3. package/plugins/jentrix/skills/jentrix-align/SKILL.md +13 -7
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jentrix/plugin-codex",
3
- "version": "0.3.1",
3
+ "version": "0.3.3",
4
4
  "description": "The official Jentrix plugin for Codex: connected-session skills and trusted lifecycle hooks, materialized by the Jentrix CLI (jentrix plugin install codex).",
5
5
  "keywords": [
6
6
  "jentrix",
package/plugins/jentrix/.codex-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "jentrix",
3
- "version": "0.3.1",
3
+ "version": "0.3.3",
4
4
  "description": "Connect Codex tasks to Jentrix with trusted lifecycle hooks, exact-rollout telemetry recovery, typed artifacts, and operator-confirmed alignment.",
5
5
  "author": {
6
6
  "name": "Jentrix",
package/plugins/jentrix/skills/jentrix-align/SKILL.md CHANGED
@@ -66,13 +66,19 @@ wizard; a Project is an optional task label and is never part of it).
66
66
  ```
67
67
 
68
68
  One call returns the description, the links BOTH ways with their titles,
69
- the subtasks, the latest artifact of each type with its id, and the last
70
- five comments. Read it before you touch any code: a linked card is usually
71
- where the prior round's reasoning lives, and its artifacts are the context
72
- you would otherwise reconstruct from scratch. If it prints
73
- `no links · no artifacts · no comments`, the card has nothing to give and
74
- you stop looking — that single line is the answer, not an invitation to run
75
- `task get`, `task search` and `comment list` to confirm it.
69
+ the subtasks, the latest artifact of each type with its id, the last five
70
+ comments, and **Related evidence** — what OTHER work in this workspace
71
+ already said about this card (learnings, decisions, findings, reports;
72
+ at most five, each at 78 % similarity or more — byte for byte the block
73
+ the align output printed). Read it
74
+ before you touch any code: a linked card is usually where the prior
75
+ round's reasoning lives, its artifacts are the context you would otherwise
76
+ reconstruct from scratch, and a related learning is a mistake you do not
77
+ have to make twice — `jentrix artifact get --artifact-id <id>` reads one in
78
+ full. If it prints `no links · no artifacts · no comments · no related
79
+ evidence`, the card has nothing to give and you stop looking — that single
80
+ line is the answer, not an invitation to run `task get`, `task search` and
81
+ `comment list` to confirm it.
76
82
 
77
83
  Notes for you (the assistant):
78
84