taskchef 5.6.0 → 5.7.1

package/.codex-plugin/plugin.json

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

package/README.md

@@ -129,8 +129,9 @@ when it sent it, which project it selected, and which Codex task received the
 work.
 
 Every delegated instruction begins with a unique
-`<!-- taskchef_id=<UUID> -->` marker followed by a blank line. The valid HTML
-comment stays invisible in rendered Markdown.
+`<!-- taskchef_id=<UUID> -->` marker followed by a blank line, an
+executor-ownership paragraph, another blank line, and the assignment. The
+valid HTML comment stays invisible in rendered Markdown.
 If worktree creation does not return a thread ID immediately, TaskChef records
 the marked delegation as unresolved, then makes at most two exact-marker checks
 during a short bounded window. Candidate reads use one programmatic batch per
@@ -244,8 +245,9 @@ taskchef task summary
 
 Workspace resolution is deterministic: `--workspace <path>`, then the
 `TASKCHEF_WORKSPACE` environment variable, then `~/.agents/taskchef`. The
-current directory is never an implicit workspace. Data commands accept
-`--json` for machine-readable output. Run `taskchef help` for every option.
+current directory is never an implicit workspace. Data commands use concise
+human-readable output by default and accept `--json` for machine-readable
+output. Run `taskchef help` for every option.
 
 `taskchef dispatch prepare --json` is the CLI equivalent of the MCP
 `prepare_dispatch` operation: it resolves the canonical workspace, loads and
@@ -351,7 +353,7 @@ task lines remain readable without an eager rewrite of the append-only history.
 `project` value is the exact configured project path:
 
 ```sh
-printf '%s\n' '{"id":"c0f010ff-84f2-4838-a69d-0ff1f5d721d7","project":"/workspace/payments","title":"Add retry logs","instruction":"<!-- taskchef_id=c0f010ff-84f2-4838-a69d-0ff1f5d721d7 -->\n\nAdd structured logs for failed retries and test them.","threadId":"019f..."}' |
+printf '%s\n' '{"id":"c0f010ff-84f2-4838-a69d-0ff1f5d721d7","project":"/workspace/payments","title":"Add retry logs","instruction":"<!-- taskchef_id=c0f010ff-84f2-4838-a69d-0ff1f5d721d7 -->\n\nThis task owns the delegated assignment. Execute it in this task; do not re-dispatch it merely because it concerns TaskChef or a configured project. Explicit requests to delegate separate work remain valid.\n\nAdd structured logs for failed retries and test them.","threadId":"019f..."}' |
   taskchef task record --json
 ```
 
@@ -371,6 +373,7 @@ Inspect the task history without querying Codex tasks:
 
 ```sh
 taskchef task show c0f010ff
+taskchef task show c0f010ff --json
 taskchef task list
 taskchef task list --project payments
 taskchef task list --ascending
@@ -384,10 +387,32 @@ 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. `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.
+`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. Its default output labels the title, project name and path, creation
+time, full task and thread IDs, and instruction. A null thread ID appears as
+`-`, and multiline instructions retain their original line breaks and
+indentation. Pass `--json` to receive the unchanged complete task object.
+
+```text
+Title: Add retry logs
+Project: payments
+Project path: /workspace/payments
+Created: 2026-08-12T10:00:00.000Z
+Task ID: c0f010ff-84f2-4838-a69d-0ff1f5d721d7
+Thread ID: 019f9d46-f42c-7482-9707-3c107bf241ee
+Instruction:
+<!-- taskchef_id=c0f010ff-84f2-4838-a69d-0ff1f5d721d7 -->
+
+This task owns the delegated assignment. Execute it in this task; do not re-dispatch it merely because it concerns TaskChef or a configured project. Explicit requests to delegate separate work remain valid.
+
+Add structured logs for failed payment retries and test them.
+```
+
+The list remains a compact table:
 
 ```text
 TITLE           PROJECT   CREATED                   ID        THREAD ID

package/SPEC.md

@@ -13,18 +13,27 @@ not maintain a second lifecycle database.
 ## Core behavior
 
 1. The user submits a request in the dispatcher workspace or explicitly invokes
-   the delegation skill from another Codex project.
+   the delegation skill from another Codex project. Work merely concerning the
+   TaskChef source code does not implicitly invoke delegation outside the
+   dispatcher workspace.
 2. TaskChef separates only outcomes that can proceed independently.
 3. It selects each target using configured project metadata and validates the
    selected local path.
 4. It creates an independently openable Codex task in that project.
 5. It embeds a generated TaskChef UUID marker in the initial instruction before
-   creation. It appends one task entry as soon as creation returns, using
-   `threadId: null` while a provisional client ID is briefly resolved.
+   creation, followed by an executor-ownership sentence and the assignment. It
+   appends one task entry as soon as creation returns, using `threadId: null`
+   while a provisional client ID is briefly resolved.
 6. It returns without waiting for executor work to complete.
 7. When requested, TaskChef can read task entries, query the relevant Codex
    tasks once, and present a live report without persisting the fetched state.
 
+A task created by TaskChef owns its delegated initial assignment. It executes
+that assignment in the current task and does not re-dispatch it merely because
+the subject is TaskChef or another configured project. The task may still use
+TaskChef when the initial assignment explicitly requests delegation of separate
+work or when the user later explicitly requests a new delegation.
+
 Several active executors may target the same project.
 
 ## Workspace layout
@@ -134,7 +143,7 @@ schedules, task status, results, host information, or the workspace path.
 `tasks.jsonl` contains one compact JSON object per line, in append order:
 
 ```json
-{"schemaVersion":2,"id":"c0f010ff-84f2-4838-a69d-0ff1f5d721d7","project":{"name":"payments-api","path":"/workspace/payments-api","isGitRepository":true,"githubRepos":["https://github.com/example/payments-api","https://github.com/example/payments-sdk"],"description":"Owns payment authorization, capture, refunds, and provider integrations."},"title":"Add payment retry logs","instruction":"<!-- taskchef_id=c0f010ff-84f2-4838-a69d-0ff1f5d721d7 -->\n\nAdd structured logs for failed payment retries and test them.","threadId":"019f9d46-f42c-7482-9707-3c107bf241ee","createdAt":"2026-08-08T10:00:00.000Z"}
+{"schemaVersion":2,"id":"c0f010ff-84f2-4838-a69d-0ff1f5d721d7","project":{"name":"payments-api","path":"/workspace/payments-api","isGitRepository":true,"githubRepos":["https://github.com/example/payments-api","https://github.com/example/payments-sdk"],"description":"Owns payment authorization, capture, refunds, and provider integrations."},"title":"Add payment retry logs","instruction":"<!-- taskchef_id=c0f010ff-84f2-4838-a69d-0ff1f5d721d7 -->\n\nThis task owns the delegated assignment. Execute it in this task; do not re-dispatch it merely because it concerns TaskChef or a configured project. Explicit requests to delegate separate work remain valid.\n\nAdd structured logs for failed payment retries and test them.","threadId":"019f9d46-f42c-7482-9707-3c107bf241ee","createdAt":"2026-08-08T10:00:00.000Z"}
 ```
 
 - `schemaVersion` identifies the task entry format.
@@ -142,8 +151,8 @@ schedules, task status, results, host information, or the workspace path.
 - `project` is the complete configured project snapshot used for routing.
 - `title` is a short task name.
 - `instruction` is the complete executor instruction, including its first-line
-  `<!-- taskchef_id=<full UUID> -->` correlation marker and the blank line that
-  follows it.
+  `<!-- taskchef_id=<full UUID> -->` correlation marker, executor-ownership
+  paragraph, and assignment body.
 - `threadId` identifies the created Codex task, or is `null` when creation was
   accepted but bounded marker resolution did not find one durable task ID.
 - `createdAt` is the dispatch time as an ISO 8601 timestamp.
@@ -188,7 +197,8 @@ For each assignment, `$taskchef-delegate`:
    the already-loaded native projects
 3. prefixes the instruction with the prepared exact
    `<!-- taskchef_id=<UUID> -->` marker as the first line, followed by a blank
-   line
+   line, the executor-ownership sentence, another blank line, and the
+   assignment body
 4. creates a real Codex task at the exact configured path
 5. appends a task entry immediately through the structured `record_task` tool
    when creation returns a durable thread ID; it never opens a shell, parses
@@ -296,10 +306,15 @@ it was not recorded.
 
 The CLI reads persisted history without contacting Codex:
 
-- `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 show <id-or-8-character-prefix>` returns one entry. By default it emits
+  labeled human-readable lines for title, project name and path, creation time,
+  full task ID, thread ID, and instruction. A null thread ID renders as `-`.
+  The instruction starts on the line after `Instruction:` and retains its
+  stored line breaks and indentation. `--json` returns the unchanged complete
+  task object. 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, shorter, and
+  wrong-case 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/docs/delegation-design.md

@@ -130,6 +130,8 @@ The exact executor instruction becomes:
 ```text
 <!-- taskchef_id=c0f010ff-84f2-4838-a69d-0ff1f5d721d7 -->
 
+This task owns the delegated assignment. Execute it in this task; do not re-dispatch it merely because it concerns TaskChef or a configured project. Explicit requests to delegate separate work remain valid.
+
 Return exactly the integers 1 through 10, one per line.
 Do not modify files.
 ```
@@ -184,7 +186,7 @@ with `threadId: null`:
   "id": "c0f010ff-84f2-4838-a69d-0ff1f5d721d7",
   "project": "/projects/t2",
   "title": "Count from 1 to 10",
-  "instruction": "<!-- taskchef_id=c0f010ff-84f2-4838-a69d-0ff1f5d721d7 -->\n\nReturn exactly the integers 1 through 10, one per line.\nDo not modify files.",
+  "instruction": "<!-- taskchef_id=c0f010ff-84f2-4838-a69d-0ff1f5d721d7 -->\n\nThis task owns the delegated assignment. Execute it in this task; do not re-dispatch it merely because it concerns TaskChef or a configured project. Explicit requests to delegate separate work remain valid.\n\nReturn exactly the integers 1 through 10, one per line.\nDo not modify files.",
   "threadId": null
 }
 ```
@@ -197,7 +199,7 @@ A later candidate read might contain this structured delegated input:
     "content": [
       {
         "codexDelegation": {
-          "input": "<!-- taskchef_id=c0f010ff-84f2-4838-a69d-0ff1f5d721d7 -->\n\nReturn exactly the integers 1 through 10, one per line.\nDo not modify files."
+          "input": "<!-- taskchef_id=c0f010ff-84f2-4838-a69d-0ff1f5d721d7 -->\n\nThis task owns the delegated assignment. Execute it in this task; do not re-dispatch it merely because it concerns TaskChef or a configured project. Explicit requests to delegate separate work remain valid.\n\nReturn exactly the integers 1 through 10, one per line.\nDo not modify files."
         }
       }
     ]

package/index.js

@@ -28,6 +28,7 @@ export {
 } from "./src/github.js";
 
 export {
+  EXECUTOR_OWNERSHIP_PARAGRAPH,
   THREAD_RESOLUTION_CHECKPOINTS_MS,
   THREAD_RESOLUTION_CLOCK_SKEW_MS,
   THREAD_RESOLUTION_RECENT_LIMIT,

package/package.json

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

package/skills/taskchef-delegate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: taskchef-delegate
-description: "Dispatch actionable requests through the per-user TaskChef workspace into independently openable Codex project tasks. Use for ordinary work requests in the TaskChef project, explicit delegation from any project, or splitting independent work across projects. Preserve unresolved delegations for later marker-based recovery, and never use subagents, hooks, schedules, daemons, or executor-completion waiting."
+description: "Dispatch actionable requests through the per-user TaskChef workspace into independently openable Codex project tasks. Use automatically for actionable work received in the canonical TaskChef dispatcher workspace. From any other project, use only when the user explicitly asks to delegate or split separate work into Codex tasks; TaskChef-related subject matter alone is not delegation intent. Preserve unresolved delegations for later marker-based recovery, and never use subagents, hooks, schedules, daemons, or executor-completion waiting."
 ---
 
 # TaskChef Delegate
@@ -8,6 +8,17 @@ description: "Dispatch actionable requests through the per-user TaskChef workspa
 Create real Codex tasks through the canonical per-user TaskChef data workspace
 and return immediately.
 
+## Invocation boundary
+
+A task whose initial structured `codexDelegation.input` starts with an exact
+`<!-- taskchef_id=<full UUID> -->` marker already owns that delegated
+assignment. Execute the assignment in the current task. Do not re-dispatch it
+merely because it concerns TaskChef or a configured project.
+
+This does not prevent the task from using TaskChef later. Use this skill
+normally when the initial assignment explicitly asks to delegate separate
+work, or when the user later explicitly requests a new delegation.
+
 Use the bundled TaskChef `prepare_dispatch`, `record_task`, and `resolve_task`
 tools for deterministic workspace and task-record operations. Call them
 directly; never probe for them or fall back to shell CLI writes. If a required
@@ -57,7 +68,12 @@ explicitly requested benchmark artifact.
    tool.
    Prefix the complete executor instruction with
    exactly `<!-- taskchef_id=<full UUID> -->` as the first line, followed by a
-   blank line and the instruction body. Preserve this
+   blank line, this executor-role paragraph, another blank line, and the
+   instruction body. Add the paragraph as one line in the created input:
+
+   > This task owns the delegated assignment. Execute it in this task; do not re-dispatch it merely because it concerns TaskChef or a configured project. Explicit requests to delegate separate work remain valid.
+
+   Preserve this
    marked instruction for recording, and note the creation time. The exact
    random marker is the sole correlation proof.
 6. Create one real Codex task using the exact configured project, a local

package/src/cli.js

@@ -161,6 +161,19 @@ function displayId(value, fullId) {
   return uuidSection ? uuidSection[0] : value;
 }
 
+function taskDetails(task) {
+  return [
+    `Title: ${task.title}`,
+    `Project: ${task.project.name}`,
+    `Project path: ${task.project.path}`,
+    `Created: ${task.createdAt}`,
+    `Task ID: ${task.id}`,
+    `Thread ID: ${task.threadId ?? "-"}`,
+    "Instruction:",
+    task.instruction,
+  ].join("\n");
+}
+
 async function readTaskForShow(workspace, taskId) {
   const id = requireSafeId(taskId, "taskId");
   const tasks = await listTasks(workspace);
@@ -348,7 +361,7 @@ async function taskResolve(args) {
 
 async function taskShow(args) {
   validateCommandArgs(args, 3, { values: ["--workspace"], switches: ["--json"] });
-  print(await readTaskForShow(workspaceRoot(args), args[2]), args);
+  print(await readTaskForShow(workspaceRoot(args), args[2]), args, taskDetails);
   return 0;
 }
 
@@ -407,6 +420,7 @@ Usage:
 
 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.
+Task show prints human-readable details by default; --json prints the complete task object.
 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

package/src/delegation.js

@@ -4,6 +4,7 @@ export const THREAD_RESOLUTION_CHECKPOINTS_MS = Object.freeze([10_000, 30_000]);
 export const THREAD_RESOLUTION_TIMEOUT_MS = 30_000;
 export const THREAD_RESOLUTION_RECENT_LIMIT = 50;
 export const THREAD_RESOLUTION_CLOCK_SKEW_MS = 5_000;
+export const EXECUTOR_OWNERSHIP_PARAGRAPH = "This task owns the delegated assignment. Execute it in this task; do not re-dispatch it merely because it concerns TaskChef or a configured project. Explicit requests to delegate separate work remain valid.";
 
 const UUID_SOURCE = "[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}";
 const UUID_PATTERN = new RegExp(`^${UUID_SOURCE}$`);
@@ -93,7 +94,7 @@ export function prepareDelegation(instruction, { taskId = randomUUID() } = {}) {
   const id = requireUuid(taskId);
   return {
     id,
-    instruction: `${taskChefMarker(id)}\n\n${instruction}`,
+    instruction: `${taskChefMarker(id)}\n\n${EXECUTOR_OWNERSHIP_PARAGRAPH}\n\n${instruction}`,
   };
 }