@jentrix/plugin-codex 0.2.8 → 0.2.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jentrix/plugin-codex",
-  "version": "0.2.8",
+  "version": "0.2.9",
   "description": "The official Jentrix plugin for Codex: connected-session skills and trusted lifecycle hooks, materialized by the Jentrix CLI (jentrix plugin install codex).",
   "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/codex"
+    "url": "git+https://github.com/jentrix-au/jentrix.git",
+    "directory": "plugins/codex"
   },
   "license": "MIT",
   "author": "Jentrix",

package/plugins/jentrix/.codex-plugin/plugin.json

@@ -1,15 +1,20 @@
 {
   "name": "jentrix",
-  "version": "0.2.8",
+  "version": "0.2.9",
   "description": "Connect Codex tasks to Jentrix with trusted lifecycle hooks, exact-rollout telemetry recovery, typed artifacts, and operator-confirmed alignment.",
   "author": {
     "name": "Jentrix",
     "url": "https://github.com/jentrix-au"
   },
   "homepage": "https://tm.jentrix.ai/docs",
-  "repository": "https://github.com/jentrix-au/task-manager",
+  "repository": "https://github.com/jentrix-au/jentrix",
   "license": "MIT",
-  "keywords": ["jentrix", "sessions", "task-management", "agents"],
+  "keywords": [
+    "jentrix",
+    "sessions",
+    "task-management",
+    "agents"
+  ],
   "skills": "./skills/",
   "interface": {
     "displayName": "Jentrix",
@@ -17,7 +22,10 @@
     "longDescription": "Align a Codex task to a Jentrix project and task, preserve typed artifacts and checkpoints, capture supported lifecycle evidence through trusted hooks, and recover provider-reported usage from the exact task rollout when hooks are unavailable.",
     "developerName": "Jentrix",
     "category": "Productivity",
-    "capabilities": ["Interactive", "Write"],
+    "capabilities": [
+      "Interactive",
+      "Write"
+    ],
     "defaultPrompt": [
       "Connect this Codex task to my Jentrix project.",
       "Align this work and create a confirmed task plan."

package/plugins/jentrix/skills/jentrix-align/SKILL.md

@@ -2,7 +2,7 @@
 name: jentrix-align
 description: Align the current Codex task to a Jentrix work item (task + accountable owner) with a server-confirmed snapshot.
 ---
-<!-- Source of truth: cli/plugins/codex. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/codex in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 # Align this Codex task
 
@@ -24,7 +24,12 @@ wizard is retired, and a Project is an optional task label, never part of it.
    line rather than summarizing it away.
 4. `FOLDER_NOT_ALIGNED` means the checkout has no workspace binding: run
    `jentrix folder align`, then retry. Never invent a workspace or task id.
-5. Settings ride a same-task re-align without fragmenting attribution:
+5. Move the aligned task to the board's working column when you start work on
+   it: read the real columns (`jentrix column list --board <boardId> --json`) and
+   move with `jentrix task move --task <taskId> --to-column-id <columnId>`.
+   `$jentrix-end` moves it to In review when the work is genuinely finished — the
+   terminal move is the operator's Accept, never yours.
+6. Settings ride a same-task re-align without fragmenting attribution:
    `--owner`, `--agent`, `--agent-emoji`, `--budget|--no-budget`,
    `--capture|--no-capture`, `--skeleton|--no-skeleton`. Pass only what the
    operator asked for. Project labels are separate:

package/plugins/jentrix/skills/jentrix-checkpoint/SKILL.md

@@ -2,7 +2,7 @@
 name: jentrix-checkpoint
 description: Distill verified session state into a typed Jentrix checkpoint that survives compaction or handoff.
 ---
-<!-- Source of truth: cli/plugins. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/codex in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 # Write a checkpoint
 

package/plugins/jentrix/skills/jentrix-connect/SKILL.md

@@ -2,7 +2,7 @@
 name: jentrix-connect
 description: Connect the current Codex task to Jentrix (session anchor + capture in the folder's workspace).
 ---
-<!-- Source of truth: cli/plugins/codex. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/codex in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 # Connect this Codex task
 

package/plugins/jentrix/skills/jentrix-end/SKILL.md

@@ -2,15 +2,18 @@
 name: jentrix-end
 description: End a connected Jentrix session after preserving approved outputs, parking completed work in review, and reporting capture honestly.
 ---
-<!-- Source of truth: cli/plugins. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/codex in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 # End the connected session
 
 1. For an aligned session, offer to push a concise final `report`, any unrecorded
-   `decision --basis <artifact-id|url>` or `learning`, and a useful `diff`. Run the
-   **gap sweep**: every promised-but-undone item becomes a `jentrix push gap` (title
-   states the claim), and anything found broken becomes `jentrix push issue`. Never
-   invent content or record material the operator declined.
+   `decision --basis <artifact-id|url>` or `learning`. Run the **gap sweep**: every
+   promised-but-undone item becomes a `jentrix push gap` (title states the claim),
+   and anything found broken becomes `jentrix push issue`. Never invent content or
+   record material the operator declined. Do NOT push a diff by hand: when HEAD
+   moved, `jentrix session end` generates the real `git log --patch` for the
+   session's range itself and pushes it as the attested DIFF (evidence check E1) —
+   a model-authored diff would be a second, unattested copy.
 2. **Batched mint confirmations**: list this session's gap/issue/findings artifacts
    not yet minted and ask the operator once which should become cards; for each
    accepted one run `jentrix artifact mint-issue --artifact <id> --from-task <id>`
@@ -18,8 +21,11 @@ description: End a connected Jentrix session after preserving approved outputs,
    (`mint-<artifactId>`); a declined mint leaves the artifact untouched.
 3. If work is genuinely complete, read the board's real columns and move the task to
    **In review**. Never self-accept it into Done.
-4. Run `jentrix session end <session-id>` and relay all output, including the exact
-   telemetry line and any capture gap.
+4. Run `jentrix session end` and relay all output, including the exact telemetry
+   line and any capture gap. With no id it closes THIS task's aligned session (the
+   same resolution `jentrix session status` shows); pass an id only when the
+   operator names a different session. When several sessions are bound to the
+   checkout the CLI refuses and lists them — ask the operator which one, never pick.
 5. Report provider-reported Codex token receipts when the hook supplied a rollout
    path. If none were observed, keep token fields null; never report estimates.
 6. A final-response artifact exists only when a prior `Stop` hook observed assistant

package/plugins/jentrix/skills/jentrix-plan/SKILL.md

@@ -2,7 +2,7 @@
 name: jentrix-plan
 description: Turn the opening request into an operator-approved goal and small Jentrix task set, then store the prompt and goal as typed artifacts.
 ---
-<!-- Source of truth: cli/plugins. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/codex in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 # Plan confirmed work
 
@@ -13,9 +13,13 @@ description: Turn the opening request into an operator-approved goal and small J
    is already one unit of work, create no extra tasks.
 4. Ask the operator to approve or replace the goal and every title. Their wording is
    authoritative; never silently clean it up.
-5. Create only approved tasks with stable idempotency keys, record the goal on the
-   aligned task, push the opening prompt verbatim as a `prompt` artifact, and push
-   the approved goal as a `goal` artifact.
+5. Create only approved tasks with stable idempotency keys and record the goal on
+   the aligned task. Then push the typed inputs — the provenance the RUN_SUMMARY's
+   Intent cites: the opening prompt VERBATIM with
+   `jentrix push prompt --title "Opening prompt"` (never a paraphrase), the
+   approved goal with `jentrix push goal --title "Goal"`, and, when a PRD exists
+   for this work, `jentrix push prd --title "<PRD title>"` with the PRD body on
+   stdin.
 6. Report created ids/keys and move only the task being started into the board's
    actual working column.
 

package/plugins/jentrix/skills/jentrix-review/SKILL.md

@@ -2,7 +2,7 @@
 name: jentrix-review
 description: Review a Jentrix session's typed artifacts by category, verify the readiness contract, and post the verdict as a comment on the aligned task.
 ---
-<!-- Source of truth: cli/plugins. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/codex in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 # Review a session's record
 

package/plugins/jentrix/skills/jentrix-status/SKILL.md

@@ -2,7 +2,7 @@
 name: jentrix-status
 description: Show the connected Jentrix session, alignment, capture health, and honest telemetry availability for this Codex task.
 ---
-<!-- Source of truth: cli/plugins. Shipped verbatim in the npm package. -->
+<!-- Source of truth: plugins/codex in jentrix-au/jentrix. Shipped verbatim in the npm package. -->
 
 # Show session status