taskchef 5.5.1 → 5.6.0

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "taskchef",
-  "version": "5.5.1",
+  "version": "5.6.0",
   "description": "Dispatch work from a data-only workspace to visible Codex project tasks.",
   "author": {
     "name": "Favo Yang",

package/README.md

@@ -95,7 +95,7 @@ TaskChef replies with a link to the new Codex task. Open it to follow progress
 or give the executor more instructions. The dispatcher is ready for another
 request immediately.
 
-The plugin's focused local tools prepare and record delegations directly in the
+The plugin's focused MCP tools prepare and record delegations directly in the
 canonical workspace. They preserve TaskChef's lock and atomic-write guarantees
 without shell quoting, stdin handling, temporary record files, or a separate
 command-sandbox permission round trip.
@@ -205,8 +205,11 @@ The plugin has three skills:
 - `$taskchef-delegate` routes requests and creates executor tasks
 - `$taskchef-report` reads the task history and reports live executor state once
 
-The CLI underneath these skills manages workspace data. Run it once with `npx`
-if you do not want a global installation:
+Normal delegation uses the plugin's bundled MCP tools. The bootstrap and report
+skills continue to call the CLI for deterministic workspace administration,
+task-history reads, and later recovery. The same CLI is also available for
+direct inspection, benchmarking, and manual operations over the shared
+workspace logic. Run it once with `npx` if you do not want a global installation:
 
 ```sh
 npx taskchef help
@@ -218,9 +221,9 @@ For the shorter command used below, install it globally:
 npm install --global taskchef
 ```
 
-The npm package provides the data CLI. The Codex plugin provides the skills
-that create and inspect executor tasks. From a source checkout, use
-`node bin/taskchef.js`.
+The npm package provides the data CLI. The Codex plugin provides the skills and
+focused MCP tools used during delegation; native Codex tools still create and
+inspect executor tasks. From a source checkout, use `node bin/taskchef.js`.
 
 ```text
 taskchef help
@@ -234,7 +237,7 @@ taskchef project remove <name>
 taskchef dispatch prepare
 taskchef task record
 taskchef task resolve <task-id> --thread-id <thread-id>
-taskchef task show <task-id>
+taskchef task show <task-id-or-8-character-prefix>
 taskchef task list
 taskchef task summary
 ```
@@ -244,11 +247,14 @@ Workspace resolution is deterministic: `--workspace <path>`, then the
 current directory is never an implicit workspace. Data commands accept
 `--json` for machine-readable output. Run `taskchef help` for every option.
 
-`taskchef dispatch prepare --json` performs the read-only preparation used by
-the delegation skill in one process: it resolves the canonical workspace,
-loads and validates configured projects, and returns a generated task UUID,
-preparation timestamp, and exact correlation marker. `task record` accepts one
-JSON value only from closed, non-interactive standard input.
+`taskchef dispatch prepare --json` is the CLI equivalent of the MCP
+`prepare_dispatch` operation: it resolves the canonical workspace, loads and
+validates configured projects, and returns a generated task UUID, preparation
+timestamp, and exact correlation marker. Normal delegation calls the MCP tool;
+the CLI command remains useful for diagnostics and benchmarks. `task record`
+accepts one JSON value only from closed, non-interactive standard input and is
+intended for manual recovery or direct CLI use, not the skill's normal
+recording path.
 
 For repeatable live delegation measurements, run
 `npm run benchmark:e2e -- write`. It reads one non-interactive JSON value,
@@ -349,8 +355,11 @@ printf '%s\n' '{"id":"c0f010ff-84f2-4838-a69d-0ff1f5d721d7","project":"/workspac
   taskchef task record --json
 ```
 
-If a task has `threadId: null`, Codex can later find its exact marker and pass
-the verified durable ID to the CLI. Resolution is atomic and only permits the
+If a task has `threadId: null`, a later Codex workflow can find its exact
+marker and pass the verified durable ID through its prescribed interface. The
+delegate skill uses the MCP `resolve_task` tool during bounded post-creation
+recovery; the report skill and direct manual recovery use the equivalent CLI
+operation below. Both reach the same atomic logic, which permits only the
 one-way transition from null to one unique thread ID:
 
 ```sh
@@ -361,7 +370,7 @@ taskchef task resolve c0f010ff-84f2-4838-a69d-0ff1f5d721d7 \
 Inspect the task history without querying Codex tasks:
 
 ```sh
-taskchef task show t1
+taskchef task show c0f010ff
 taskchef task list
 taskchef task list --project payments
 taskchef task list --ascending
@@ -375,7 +384,10 @@ UUID-shaped IDs use their first eight-character section by default; pass
 with other empty table cells. Tasks are newest-first by default; pass
 `--ascending` to list them from oldest to newest. ID formatting does not alter
 the complete values in `--json` output, and the selected order applies to its
-`tasks` array.
+`tasks` array. `task show` accepts either the full task ID or the exact
+eight-character task ID printed by the default human-readable list. A short ID
+must identify exactly one recorded task; use `task list --full-id` when a short
+ID is missing or ambiguous.
 
 ```text
 TITLE           PROJECT   CREATED                   ID        THREAD ID

package/SPEC.md

@@ -296,7 +296,10 @@ it was not recorded.
 
 The CLI reads persisted history without contacting Codex:
 
-- `task show <id>` returns one entry.
+- `task show <id-or-8-character-prefix>` returns one entry. The short form is
+  the exact ID text printed by the default human-readable `task list` output
+  and succeeds only when it identifies exactly one recorded task. Missing,
+  ambiguous, malformed, and shorter prefixes fail without selecting a task.
 - `task list` returns entries newest-first by creation time, optionally filtered
   by historical project name or exact path. `--ascending` returns oldest-first.
   Human rows include task and thread ID columns, abbreviating UUID-shaped IDs

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "taskchef",
-  "version": "5.5.1",
+  "version": "5.6.0",
   "description": "A non-blocking interactive dispatcher for visible Codex tasks.",
   "license": "MIT",
   "author": "Favo Yang",

package/src/cli.js

@@ -12,10 +12,11 @@ import {
   importProjects,
   initializeWorkspace,
   listProjects,
+  listTasks,
   prepareDispatch,
-  readTask,
   recordTask,
   removeProject,
+  requireSafeId,
   resolveTask,
 } from "./workspace.js";
 
@@ -160,6 +161,39 @@ function displayId(value, fullId) {
   return uuidSection ? uuidSection[0] : value;
 }
 
+async function readTaskForShow(workspace, taskId) {
+  const id = requireSafeId(taskId, "taskId");
+  const tasks = await listTasks(workspace);
+  if (!/^[0-9a-fA-F]{8}$/.test(id)) {
+    const exact = tasks.find((task) => task.id === id);
+    if (exact) return exact;
+    if (id.length < 8) {
+      throw new Error(
+        `task ID prefix is too short: ${id}; use all 8 characters shown by taskchef task list`,
+      );
+    }
+    if (id.length === 8) {
+      throw new Error(
+        `malformed task ID prefix: ${id}; use the 8 hexadecimal characters shown by taskchef task list`,
+      );
+    }
+    throw new Error(`task not found: ${id}`);
+  }
+
+  const matches = tasks.filter((task) => displayId(task.id, false) === id);
+  if (matches.length === 0) {
+    throw new Error(
+      `task not found for ID prefix: ${id}; run taskchef task list --full-id to verify the task ID`,
+    );
+  }
+  if (matches.length > 1) {
+    throw new Error(
+      `task ID prefix is ambiguous: ${id}; run taskchef task list --full-id and pass the full task ID`,
+    );
+  }
+  return matches[0];
+}
+
 async function initialize(args) {
   validateCommandArgs(args, 2, {
     values: ["--workspace", "--codex-cli"],
@@ -314,7 +348,7 @@ async function taskResolve(args) {
 
 async function taskShow(args) {
   validateCommandArgs(args, 3, { values: ["--workspace"], switches: ["--json"] });
-  print(await readTask(workspaceRoot(args), args[2]), args);
+  print(await readTaskForShow(workspaceRoot(args), args[2]), args);
   return 0;
 }
 
@@ -367,11 +401,12 @@ Usage:
   taskchef dispatch prepare [--json] [--workspace <path>]
   taskchef task record [--json] [--workspace <path>]
   taskchef task resolve <task-id> --thread-id <thread-id> [--json] [--workspace <path>]
-  taskchef task show <task-id> [--json] [--workspace <path>]
+  taskchef task show <task-id-or-8-character-prefix> [--json] [--workspace <path>]
   taskchef task list [--project <name-or-path>] [--ascending] [--full-id] [--json] [--workspace <path>]
   taskchef task summary [--json] [--workspace <path>]
 
 Task record reads one JSON value from closed, non-interactive standard input.
+Task show accepts a full task ID or the exact 8-character ID printed by task list.
 Project import reads a JSON
 array from a file, or from standard input when the source is '-' or omitted.
 Workspace resolution precedence is --workspace, TASKCHEF_WORKSPACE, then