@jentrix/cli 0.5.14 → 0.5.16

package/claude-plugin/.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 runs the MVP alignment wizard, /jentrix-status and /jentrix-end wrap the same session operations. Business logic lives in the Jentrix CLI — removing this plugin leaves `jentrix session attach` as the universal fallback.",
-  "version": "0.5.1"
+  "version": "0.5.2"
 }

package/claude-plugin/commands/jentrix-align.md

@@ -2,6 +2,7 @@
 description: Align this session to a Jentrix work layer (workspace → project → task → owner) with a server-confirmed alignment snapshot
 allowed-tools: Bash(jentrix align:*), Bash(jentrix session:*)
 ---
+<!-- Source of truth. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 Run the Jentrix MVP alignment wizard for THIS session. The question set is
 fixed — workspace, project, project name, work item, task title, owner,
@@ -20,6 +21,15 @@ and do NOT answer any question yourself.
 3. If `currentAlignment` is non-null: show it to the operator and ask —
    using the native choice UI (AskUserQuestion) — whether to keep it or
    re-align. Keep → relay the current snapshot and stop.
+   **Fast path.** If the payload's only `ask` question is `confirmation`
+   (project / work item / owner were pre-filled from this checkout's previous
+   alignment and the confirmation prompt says so — "continuing this
+   checkout's previous alignment …"), present that prompt VERBATIM through
+   the choice UI. Confirm ⇒ submit with the answered values exactly as the
+   payload shows them (`--project <id> --task <id>|--session-level --owner
+   <id>`). Re-answer ⇒ re-run `jentrix align --questions --json --fresh` and
+   continue with the full flow below, passing `--fresh` on the final submit
+   too.
 4. For each question whose `status` is `"ask"`, present its `choices`
    verbatim through the native choice UI (AskUserQuestion), preserving the
    labels. If the question carries a `notice`, relay it to the operator
@@ -28,12 +38,19 @@ and do NOT answer any question yourself.
    choice is the explicit free-text escape: when picked, let the operator
    type the id/slug. A question whose `status` is `"skipped"` was resolved
    by detection — tell the operator what was resolved (e.g. the workspace),
-   don't re-ask it.
-5. After the project answer, re-run
-   `jentrix align --questions --json --project <chosen>` to load the
-   work-item and owner choices, then continue asking. If the operator picked
-   "Create a new project from this repo", the NEXT question is
-   `project_name` (already in the payload, `kind: "freetext"`): relay its
+   don't re-ask it. When a question carries more choices than the native
+   picker can show (the work-item question can carry up to 15 tasks plus its
+   escapes), put the overflow choices — label AND id — in the prompt text and
+   say they are reachable through "Other…". Never silently drop a choice.
+5. Re-run `--questions --json` after every answer that unlocks the next
+   question, carrying the answers so far as flags. After the WORKSPACE
+   answer: `jentrix align --questions --json --workspace <chosen>` — it
+   narrows the project list to that workspace, and without it the project
+   question stays `pending` and the flow stalls. After the PROJECT answer:
+   `jentrix align --questions --json [--workspace <chosen>] --project <chosen>`
+   loads the work-item and owner choices, then continue asking. If the
+   operator picked "Create a new project from this repo", the NEXT question
+   is `project_name` (already in the payload, `kind: "freetext"`): relay its
    `prompt` verbatim and collect the name as free text FROM THE OPERATOR —
    never propose name options, never fill it in yourself. Then re-run
    `jentrix align --questions --json --new-project "<name>"` — the work-item

package/claude-plugin/commands/jentrix-checkpoint.md

@@ -2,6 +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:*)
 ---
+<!-- Source of truth. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 Write down what this session currently knows, and push it.
 

package/claude-plugin/commands/jentrix-connect.md

@@ -2,6 +2,7 @@
 description: Connect this Claude Code session to a Jentrix project (session anchor + capture)
 allowed-tools: Bash(jentrix session:*)
 ---
+<!-- Source of truth. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 Run this exact command with the Bash tool and relay its output to the user:
 

package/claude-plugin/commands/jentrix-end.md

@@ -2,6 +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. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 End the connected Jentrix session honestly. For an ALIGNED session (the MVP
 pipeline), the typed artifacts ARE the record — push them before closing:

package/claude-plugin/commands/jentrix-plan.md

@@ -2,6 +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. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 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/claude-plugin/commands/jentrix-review.md

@@ -2,6 +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. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 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/claude-plugin/commands/jentrix-status.md

@@ -2,6 +2,7 @@
 description: Show the connected Jentrix session for this work (capture health included)
 allowed-tools: Bash(jentrix session:*)
 ---
+<!-- Source of truth. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 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/codex-plugin/plugins/jentrix/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "jentrix",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Connect Codex tasks to Jentrix projects with trusted lifecycle hooks, alignment, checkpoints, and honest session capture.",
   "author": {
     "name": "Jentrix",

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

@@ -2,6 +2,7 @@
 name: stacks-align
 description: Align the current Codex task to a Jentrix workspace, project, work item, and owner with an operator-confirmed server snapshot.
 ---
+<!-- Source of truth. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 # Align this Codex task
 
@@ -9,11 +10,23 @@ description: Align the current Codex task to a Jentrix workspace, project, work
 2. Relay every failed or warning precondition before asking anything.
 3. If `currentAlignment` exists, ask whether to keep it or re-align. Keep means
    show the current snapshot and stop.
+   Fast path: if the payload's only `ask` question is `confirmation` (project /
+   work item / owner were pre-filled from this checkout's previous alignment and
+   the confirmation prompt says so), present that prompt verbatim. Confirm ⇒
+   submit with the answered values exactly as the payload shows them
+   (`--project <id> --task <id>|--session-level --owner <id>`). Re-answer ⇒
+   re-run `jentrix align --provider codex --questions --json --fresh` and
+   continue with the full flow below, passing `--fresh` on the final submit too.
 4. Present each `status:"ask"` question and its choices verbatim using Codex's
    structured input UI when available, otherwise ask in chat. Never answer for the
    operator. Preserve notices and the `Other…` free-text escape.
-5. Re-run `--questions --json` after project selection. Collect `project_name` and
-   `task_title` as free text from the operator; never propose permanent names.
+5. Re-run `--questions --json` after every answer that unlocks the next question,
+   carrying the answers so far: `--workspace <chosen>` after the workspace (it
+   narrows the project list — without it the project question stays `pending`),
+   then `--project <chosen>`. Collect `project_name` and `task_title` as free text
+   from the operator; never propose permanent names. When the choices outnumber
+   the front end's picker, name the overflow (label + id) in the prompt rather
+   than dropping it.
 6. Present the confirmation prompt and every disclosure verbatim.
 7. On confirmation, submit exactly once with `jentrix align --provider codex --json
    --yes` plus the confirmed project, task/session-level, owner, agent label, and

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

@@ -2,6 +2,7 @@
 name: stacks-checkpoint
 description: Distill verified session state into a typed Jentrix checkpoint that survives compaction or handoff.
 ---
+<!-- Source of truth. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 # Write a checkpoint
 

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

@@ -2,6 +2,7 @@
 name: stacks-connect
 description: Connect the current Codex task to a Jentrix project using trusted lifecycle identity and start the session capture host.
 ---
+<!-- Source of truth. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 # Connect this Codex task
 

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

@@ -2,6 +2,7 @@
 name: stacks-end
 description: End a connected Jentrix session after preserving approved outputs, parking completed work in review, and reporting capture honestly.
 ---
+<!-- Source of truth. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 # End the connected session
 

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

@@ -2,6 +2,7 @@
 name: stacks-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. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 # Plan confirmed work
 

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

@@ -2,6 +2,7 @@
 name: stacks-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. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 # Review a session's record
 

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

@@ -2,6 +2,7 @@
 name: stacks-status
 description: Show the connected Jentrix session, alignment, capture health, and honest telemetry availability for this Codex task.
 ---
+<!-- Source of truth. The cli/{claude,codex}-plugin copy is GENERATED by cli/scripts/build.mjs (rm + cp) on every build — edits made there are deleted. Edit this file. -->
 
 # Show session status