taskchef 7.4.0 → 7.6.0

package/.codex-plugin/plugin.json

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

package/README.md

@@ -3,11 +3,11 @@
 TaskChef is a local dispatch desk for Codex. Give one dispatcher a request and
 it records each independently useful outcome, creates a normal Codex task in
 the right project, and returns immediately. The executor task is where live
-work, approvals, and follow-ups happen; TaskChef keeps the latest compact
-snapshot for navigation and reporting.
+work, approvals, and follow-ups happen; TaskChef keeps every semantic result
+while projecting the latest one for compact navigation and reporting.
 
 ```text
-request -> recorded TaskChef task -> Codex executor -> current state + last result
+request -> recorded TaskChef task -> Codex executor -> current state + result history
 ```
 
 ## Which document should I read?
@@ -49,7 +49,7 @@ The canonical workspace is `~/.agents/taskchef`. TaskChef owns only:
 ```text
 AGENTS.md       managed dispatcher instructions plus user additions
 taskchef.json   schema-2 configured projects and routing metadata
-tasks.jsonl     one schema-4/5 snapshot per task (new writes use schema 5)
+tasks.jsonl     one task snapshot per line (schema 6; schema 4/5 migration supported)
 ```
 
 List or change routing targets conversationally:
@@ -119,10 +119,12 @@ when a turn starts and one semantic outcome before that same turn ends:
 - `failed`: the executor or creation attempt ended unsuccessfully.
 
 A native approval prompt is live Codex state, not `needs_input`.
-TaskChef stores the current reported execution state and separately preserves
-the last concise semantic result. A follow-up therefore appears as `working`
-immediately without erasing the previous outcome. TaskChef does not store the
-transcript or a lifecycle event log.
+TaskChef stores the current reported execution state and appends every concise
+semantic result to `results`. A follow-up therefore appears as `working`
+immediately without erasing any prior outcome. The final entry is exposed as a
+derived `lastResult` compatibility alias; it is not persisted independently and
+is planned for removal in the next major version after callers move to
+`results.at(-1)`. TaskChef does not store transcripts or non-semantic events.
 
 Delegated tasks created by earlier TaskChef versions remain compatible: their
 inline executor protocol still parses, self-links, and may use the deprecated
@@ -172,7 +174,13 @@ taskchef dashboard --port 3211
 ```
 
 The loopback dashboard watches `tasks.jsonl`, groups current states, and opens
-linked Codex tasks. It does not mutate TaskChef data and prints its local URL.
+linked Codex tasks. List snapshots and SSE events carry only the latest-result
+projection; opening task details fetches the full newest-first result history.
+Task and result times are relative through 29 days (with minute detail for the
+first six hours), then use a locale-aware calendar date. Each time is a keyboard-
+accessible toggle for its full locale-aware date and time, and one shared
+30-second timer keeps relative labels current without reloading the page.
+It does not mutate TaskChef data and prints its local URL.
 When a compatible foreground dashboard already owns port 3210,
 `ensure_dashboard` reuses it but does not take ownership. If an unknown,
 different-workspace, or stale-version process owns the port, TaskChef reports a
@@ -183,6 +191,8 @@ The health endpoint contains only a fixed service marker, health schema,
 TaskChef version, dashboard-server version, and canonical workspace. It exposes
 no task data, credentials, environment variables, process control, or secrets.
 
+![Task detail result history](docs/images/result-history-dashboard.jpg)
+
 ## Common recovery
 
 Check the managed workspace:
@@ -190,20 +200,27 @@ Check the managed workspace:
 ```sh
 taskchef doctor
 taskchef workspace init
+taskchef workspace migrate
 taskchef doctor
 ```
 
-`doctor` is read-only. `workspace init` creates missing current-schema files
-and refreshes managed instructions; it does not migrate unsupported
-configuration or task records.
+`doctor` is read-only. `workspace init` creates missing files and refreshes
+managed instructions. `workspace migrate` explicitly upgrades supported schema
+4/5 task lines to schema 6 under the workspace lock. It validates the complete
+source and converted log before writing, creates an exclusive `tasks.jsonl.pre-v6-*.bak`
+backup, atomically replaces the log, validates the result, and becomes an
+idempotent no-op after migration. If replacement fails, the original remains
+or the reported backup can be restored; unsupported or invalid input is rejected
+before a backup or rewrite.
 
 If a new record has no thread ID, the executor is link-pending. Reopen that
 executor so its first action can retry `link_task`. Do not guess an identity
 or edit `tasks.jsonl`. If native task creation failed, the record is retained
 as `failed` with null thread and turn IDs.
 
-If an unsupported workspace must be retained, keep it as a backup and create a
-new current workspace. TaskChef provides no conversion or merge command.
+Schemas other than 4, 5, and 6 remain unsupported. Retain such a workspace
+unchanged and create a current workspace; the migration command deliberately
+does not guess how to convert unknown formats.
 
 ## Boundaries
 

package/assets/codex.svg

@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path fill="currentColor" d="M3 1.5h10A1.5 1.5 0 0 1 14.5 3v10a1.5 1.5 0 0 1-1.5 1.5H3A1.5 1.5 0 0 1 1.5 13V3A1.5 1.5 0 0 1 3 1.5Zm0 1a.5.5 0 0 0-.5.5v10a.5.5 0 0 0 .5.5h10a.5.5 0 0 0 .5-.5V3a.5.5 0 0 0-.5-.5H3Zm1.15 3.1.7-.7L7.95 8l-3.1 3.1-.7-.7L6.55 8l-2.4-2.4ZM8 10h4v1H8v-1Z"/>
+</svg>

package/docs/spec.md

@@ -23,7 +23,8 @@ is dated research, not contract.
 | **Self-linking** | The executor's one-way registration of its own canonical Codex UUIDv7 from `CODEX_THREAD_ID`. |
 | **Link-pending** | A working task whose `threadId` is null and `updatedBy` is `dispatcher`. |
 | **Current execution state** | The latest reported executor turn and its `working`, `needs_input`, `completed`, or `failed` status. |
-| **Last semantic result** | The most recent `completed`, `needs_input`, or `failed` outcome, preserved separately while a newer turn is working. |
+| **Result history** | The ordered collection of every accepted `completed`, `needs_input`, or `failed` per-turn outcome. |
+| **Last semantic result** | The final result-history entry, exposed through the derived `lastResult` compatibility alias. |
 | **Current turn ID** | The canonical Codex UUIDv7 returned by an exact native read of the linked executor for the turn being reported. |
 | **Dashboard** | The loopback, read-only UI derived from validated workspace snapshots and bounded native actions. |
 | **Skill** | One packaged agent procedure: `taskchef-bootstrap`, `taskchef-delegate`, `taskchef-executor`, or `taskchef-report`. |
@@ -67,10 +68,10 @@ Names and paths MUST be unique. Git projects MUST be exact Git roots.
 Repository URLs MUST canonicalize to `https://github.com/<owner>/<repository>`
 and be case-insensitively deduplicated.
 
-`tasks.jsonl` MUST contain zero or more newline-terminated schema-4 or schema-5
-records, one per line. Schema 4 is read compatibility for the previously
-released format; every new record and state mutation MUST write schema 5.
-Other schemas or unsupported fields MUST be rejected without conversion.
+`tasks.jsonl` MUST contain zero or more newline-terminated schema-4, schema-5,
+or schema-6 records, one per line. Schemas 4 and 5 are supported migration/read
+formats; every new record and state mutation MUST write schema 6. Other schemas
+or unsupported fields MUST be rejected without conversion.
 Reads and writes MUST reject symlinked managed files. Mutations
 MUST hold the shared workspace lock and replace state atomically; read-only
 operations MUST NOT require write permission.
@@ -81,7 +82,7 @@ Every record MUST contain exactly these fields:
 
 | Field | Contract |
 | --- | --- |
-| `schemaVersion` | Integer `5`; schema-4 records remain readable until their next mutation. |
+| `schemaVersion` | Integer `6`; schema-4/5 records remain readable until explicit migration or their next mutation. |
 | `id` | Unique safe TaskChef ID; delegation uses a lowercase full UUID. |
 | `project` | Immutable configured-project snapshot. |
 | `title` | Non-empty display title. |
@@ -93,7 +94,13 @@ Every record MUST contain exactly these fields:
 | `turnId` | Null before turn reporting; otherwise the current reported turn. Linked MCP journeys use a canonical Codex UUIDv7. |
 | `updatedAt` | ISO 8601 timestamp not earlier than `createdAt` or the prior `updatedAt`; clock rollback cannot backdate a transition. |
 | `updatedBy` | `dispatcher` or `mcp`. |
-| `lastResult` | Null before a semantic result; otherwise `{status, summary, turnId, updatedAt}` preserving the latest semantic result. |
+| `results` | Ordered oldest-first array of `{status, summary, turnId, updatedAt}` semantic results, with unique turn IDs and nondecreasing timestamps. |
+
+Returned Task objects MUST additionally expose `lastResult` as null for an empty
+history or the final `results` entry. `lastResult` MUST be derived and MUST NOT
+be persisted in schema 6. It is a compatibility alias for schema-4/5, CLI,
+MCP, reporting-skill, and dashboard-list callers, with removal planned for the
+next major version after callers migrate to `results.at(-1)`.
 
 Task IDs and non-null thread identities MUST be unique. The immutable intent
 fields MUST NOT change after recording.
@@ -231,7 +238,8 @@ new preparation values, though it writes no state.
 
 **Structured output:** `{ task: Task }`.
 
-The returned task has schema 5, `working`, null summary/turn/thread/lastResult,
+The returned task has schema 6, `working`, null summary/turn/thread/lastResult,
+an empty `results` array,
 `updatedBy: dispatcher`, and equal creation/update timestamps. Duplicate IDs,
 unknown projects, malformed markers, and invalid input fail. Repeating a
 successful call is not idempotent; it fails as a duplicate.
@@ -260,7 +268,7 @@ marker, or ineligible state fails.
 ### `report_state`
 
 **Caller:** executor, or dispatcher only for native creation failure.
-**Mutation:** replaces the current state atomically and preserves `lastResult`.
+**Mutation:** replaces the current state atomically and preserves `results`.
 
 **Input:**
 
@@ -279,8 +287,10 @@ the current turn and last semantic result. A semantic state MUST match the
 current working turn. Repeating an identical state is idempotent; conflicting
 or older state fails. A null-identity record accepts only a fresh executor
 creation `failed` state with both IDs null. Success sets the current state and
-preserves the semantic state in `lastResult`; starting newer work does not erase
-that result.
+appends a semantic result to `results`; starting newer work preserves the entire
+collection. An identical retry for any settled turn returns success without an
+append. A different result for a settled turn, a stale turn, or a semantic
+result that does not match the active working turn MUST fail.
 
 **Annotations:** `readOnlyHint: false`, `destructiveHint: true`,
 `openWorldHint: false`.
@@ -289,10 +299,10 @@ that result.
 
 `report_result` retains the prior semantic-only input shape and statuses as a
 temporary compatibility alias. It implicitly accepts a fresh supplied turn and
-stores its semantic result, including for supported schema-4 records and
+stores its semantic result, including for supported schema-4/5 records and
 low-level opaque direct records. It does not accept `working`. New executor
-instructions MUST use `report_state`. Successful mutation upgrades schema 4 to
-schema 5; unsupported schemas remain rejected.
+instructions MUST use `report_state`. Successful mutation upgrades schema 4/5
+to schema 6; unsupported schemas remain rejected.
 
 ## Reporting and dashboard
 
@@ -302,6 +312,7 @@ state overrides cache. An inactive task does not prove completion. Focused
 reports MAY read a selected task once when metadata is newer or evidence is
 uncertain. Reports MUST NOT poll or classify assistant prose.
 
+Task lists, summaries, and broad reports MUST use the final result by default.
 The dashboard MUST bind only to loopback, validate the current workspace
 snapshot, and avoid sessions or shared client state. `GET /api/health` MUST
 return only the bounded service identity, health schema, exact TaskChef and
@@ -313,6 +324,21 @@ startup safely. Direct thread navigation
 MUST require a canonical Codex UUIDv7. Otherwise it MAY open the revalidated
 configured project. Project paths from task history MUST be matched against
 current configuration before use.
+Snapshot and SSE list payloads MUST omit full `results` history and include the
+derived latest-result projection. The bounded per-task detail endpoint MAY
+return the full validated task so the dialog can render history newest first.
+
+## Task-log migration
+
+`workspace migrate` MUST explicitly convert every supported schema-4/5 record
+under the shared lock. A legacy `lastResult`, or a schema-4 current semantic
+state, becomes zero or one initial `results` entry. Migration MUST validate the
+complete source and complete schema-6 candidate before changing the task log,
+create and read back an exclusive recovery backup, atomically replace the log,
+and validate the installed result. A fully schema-6 log MUST be an idempotent
+no-op without another backup. Invalid/unsupported input MUST remain untouched;
+failures after backup creation MUST report the backup path and MUST never
+partially rewrite individual lines.
 
 ## Concurrency and trust
 

package/docs/workflows.md

@@ -18,7 +18,7 @@ research.
 | `src/delegation.js` | UUID marker, concise executor-skill invocation shape, and creation-failure handling. |
 | `src/workspace.js` | Current schemas, validation, locking, atomic JSONL writes, linking, and result freshness. |
 | `src/cli.js` | Administration, inspection, diagnostics, and dashboard startup. |
-| `src/dashboard.js` | Versioned health identity, validated snapshots, SSE fan-out, and bounded open actions. |
+| `src/dashboard.js` | Versioned health identity, validated compact snapshots, SSE fan-out, on-demand details, and bounded open actions. |
 | `src/dashboard-manager.js` | Concurrent singleton ensure, exact listener reuse, conflicts, and owned shutdown. |
 
 The MCP process resolves `TASKCHEF_WORKSPACE` once and never accepts a model
@@ -89,7 +89,7 @@ sequenceDiagram
   D->>D: Choose one configured and native project
   D->>M: record_task(id, project, title, instruction, null)
   M->>W: recordTask()
-  W->>W: Lock, validate, append schema-5 snapshot
+  W->>W: Lock, validate, append schema-6 snapshot
   W-->>M: working link-pending task
   M-->>D: task
   D->>C: Create executor with marked instruction
@@ -116,8 +116,8 @@ semantic callbacks.
 ## State reporting
 
 The executor obtains the turn identity from an exact native read of its own
-linked task. `report_state` records live turn state while preserving the last
-semantic result separately.
+linked task. `report_state` records live turn state while preserving the ordered
+semantic result history.
 
 ```mermaid
 sequenceDiagram
@@ -130,13 +130,13 @@ sequenceDiagram
   C-->>E: Current turn ID
   E->>M: report_state(..., working, null)
   M->>W: reportTaskState()
-  W->>W: Store current turn and preserve lastResult
+  W->>W: Store current turn and preserve results
   E->>E: Work, finish, or reach semantic decision
   E->>M: report_state(..., semantic status, summary)
   M->>W: reportTaskState()
   W->>W: Lock and validate identity and freshness
   alt Same current working turn
-    W->>W: Store semantic state and lastResult
+    W->>W: Append semantic result and derive lastResult
     W-->>M: Updated task
     M-->>E: Recorded result
   else Same turn and same result
@@ -173,9 +173,9 @@ sequenceDiagram
   C-->>E: turnB
   E->>M: report_state(..., turnB, working, null)
   M->>W: reportTaskState()
-  W->>W: Require turnB greater and preserve result A
-  W-->>M: working snapshot plus lastResult A
-  M-->>E: working snapshot plus lastResult A
+  W->>W: Require turnB greater and preserve results
+  W-->>M: working snapshot plus history A
+  M-->>E: working snapshot plus history A
   E->>M: report_state(..., turnB, completed, summaryB)
   M->>W: reportTaskState()
   W-->>M: completed snapshot plus result B
@@ -263,7 +263,9 @@ sequenceDiagram
   F-->>D: Filesystem change
   D->>F: Bounded read from one descriptor
   D->>D: Validate current schema and sort
-  D-->>B: SSE snapshot
+  D-->>B: Compact SSE snapshot without results
+  B->>D: GET task detail on demand
+  D-->>B: Full validated history
   B->>D: Open task action
   alt Canonical Codex UUIDv7
     D->>C: Direct thread navigation
@@ -273,10 +275,25 @@ sequenceDiagram
   end
 ```
 
-The dashboard binds to `127.0.0.1`, has no shared session state, limits
-request bodies, and checks origin/authority for stateful local actions. Its
-bounded identity endpoint contains no task data or secrets. Historical project
-paths are untrusted until matched against current configuration.
+The dashboard binds to `127.0.0.1`, has no shared session state, limits task
+count, file size, result count, and display fields, and checks origin/authority
+for stateful local actions. Its bounded identity endpoint contains no task data
+or secrets. The monitor already validates the complete log, but
+snapshot/SSE list projections omit `results` so repeated updates do not resend
+unnecessary history. A read-only per-task endpoint returns full history only
+when the dialog opens. Historical project paths are untrusted until matched
+against current configuration.
+
+## Schema 4/5 migration
+
+`taskchef workspace migrate` acquires the same workspace lock as lifecycle
+writers, validates the complete legacy log, converts each schema-4/5 latest
+result into zero or one initial schema-6 `results` entry, then validates the
+complete candidate. Before replacement it writes and reads back an exclusive
+`tasks.jsonl.pre-v6-*.bak` file. The task log is replaced atomically and
+validated again. A second run sees only schema 6 and returns unchanged without
+another backup. Unsupported or malformed input fails before backup/rewrite;
+after a later filesystem failure, the reported backup is the recovery source.
 
 ## Concurrency and trust boundaries
 
@@ -291,6 +308,7 @@ summary is cryptographically authenticated; this is a local single-user trust
 model. Managed files, instructions, project snapshots, MCP inputs, and dashboard
 requests are validated at every action boundary.
 
-Configuration schema 2 and task schemas 4 and 5 are accepted. Schema 4 is
-read-only compatibility until a lifecycle mutation upgrades that record to
-schema 5. Other schemas are rejected without rewrite.
+Configuration schema 2 and task schemas 4, 5, and 6 are accepted. Schemas 4/5
+are read/migration compatibility until an explicit migration or lifecycle
+mutation upgrades each record to schema 6. Schema 6 persists `results` only and
+derives `lastResult` for compatibility. Other schemas are rejected without rewrite.

package/index.js

@@ -10,6 +10,7 @@ export {
   initializeWorkspace,
   linkTask,
   listProjects,
+  migrateTaskLog,
   prepareDispatch,
   readConfig,
   listTasks,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "taskchef",
-  "version": "7.4.0",
+  "version": "7.6.0",
   "description": "A non-blocking interactive dispatcher for visible Codex tasks.",
   "license": "MIT",
   "author": "Favo Yang",
@@ -26,6 +26,7 @@
     "docs/spec.md",
     "docs/workflows.md",
     "docs/firstmate-taskchef-comparison.md",
+    "docs/images/result-history-dashboard.jpg",
     "index.js",
     "mcp",
     "scripts/benchmark-dispatch-prepare.js",

package/skills/taskchef-report/SKILL.md

@@ -44,14 +44,16 @@ all deterministic task-log operations.
    detailed read. Native approval is live Codex state, not a `needs_input`
    callback. An inactive status never proves semantic completion; it only
    permits a trustworthy cached MCP result to stand.
-4. In schema 5, treat `status`, `turnId`, and `updatedAt` as the latest reported
-   execution state and treat `lastResult` as the separately preserved semantic
-   result. A `working` state with a non-null `lastResult` means a newer executor
+4. In schema 6, treat `status`, `turnId`, and `updatedAt` as the latest reported
+   execution state and treat `results` as the ordered semantic history.
+   `lastResult` is the derived compatibility alias for `results.at(-1)`; prefer
+   the collection when full history matters and the alias for compact latest-state
+   reporting. A `working` state with a non-null `lastResult` means a newer executor
    turn started after that result; show the prior result as history, not as the
    current outcome. Treat a failed `lastResult` with null thread and turn IDs as
-   a fresh executor-creation failure. No live read is possible or needed.
-   Schema 4 snapshots normalize a structurally complete result into
-   `lastResult` without rewriting their log line. When identity is certain and
+   a fresh executor-creation failure. Schema 4/5 snapshots normalize zero or one
+   semantic result into `results` and `lastResult` without rewriting their log line.
+   No live read is possible or needed for that creation failure. When identity is certain and
    metadata says the thread is inactive, trust the latest semantic result by
    default in a broad overview unless a newer working state makes it historical.
    Do not read every idle terminal task in an overview merely because native

package/src/cli.js

@@ -14,6 +14,7 @@ import {
   initializeWorkspace,
   listProjects,
   listTasks,
+  migrateTaskLog,
   prepareDispatch,
   recordTask,
   removeProject,
@@ -182,11 +183,28 @@ function taskDetails(task) {
     `Updated by: ${singleLineDetail(task.updatedBy ?? "-")}`,
     `Task ID: ${singleLineDetail(task.id)}`,
     `Thread ID: ${singleLineDetail(task.threadId ?? "-")}`,
+    `Result count: ${task.results.length}`,
+    "Result history (newest first):",
+    ...[...task.results].reverse().map((result) => (
+      `- ${singleLineDetail(result.updatedAt)} | ${singleLineDetail(result.status)} | turn ${singleLineDetail(result.turnId ?? "-")} | ${singleLineDetail(result.summary)}`
+    )),
     "Instruction:",
     task.instruction,
   ].join("\n");
 }
 
+async function migrate(args) {
+  validateCommandArgs(args, 2, { values: ["--workspace"], switches: ["--json"] });
+  const result = await migrateTaskLog(workspaceRoot(args));
+  print(result, args, (value) => [
+    `Task log: ${value.action}`,
+    `Tasks: ${value.taskCount}`,
+    `Migrated: ${value.migratedCount}`,
+    `Backup: ${value.backupPath ?? "not needed"}`,
+  ].join("\n"));
+  return 0;
+}
+
 async function readTaskForShow(workspace, taskId) {
   const id = requireSafeId(taskId, "taskId");
   const tasks = await listTasks(workspace);
@@ -456,6 +474,7 @@ Usage:
   taskchef doctor [--json] [--workspace <path>]
   taskchef workspace path [--json] [--workspace <path>]
   taskchef workspace init [--register-codex] [--codex-cli <path>] [--json] [--workspace <path>]
+  taskchef workspace migrate [--json] [--workspace <path>]
   taskchef project add <path> [--name <name>] [--description <text>] [--github-repo <url> ... | --no-github] [--json] [--workspace <path>]
   taskchef project import [<file> | -] [--replace] [--json] [--workspace <path>]
   taskchef project list [--json] [--workspace <path>]
@@ -489,6 +508,7 @@ export async function runCli(args) {
   if (args[0] === "doctor") return doctor(args);
   if (args[0] === "workspace" && args[1] === "path") return workspacePath(args);
   if (args[0] === "workspace" && args[1] === "init") return initialize(args);
+  if (args[0] === "workspace" && args[1] === "migrate") return migrate(args);
   if (args[0] === "project" && args[1] === "add") return projectAdd(args);
   if (args[0] === "project" && args[1] === "import") return projectImport(args);
   if (args[0] === "project" && args[1] === "list") return projectList(args);