taskchef 7.28.1 → 7.29.0

package/.codex-plugin/plugin.json

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

package/README.md

@@ -342,7 +342,10 @@ server path also rejects requests before discovering or invoking the CLI.
 Task details also show whole-task and per-turn token usage when `ccusage` can
 map the linked Codex thread. A completed turn briefly shows “Calculating token
 usage…” while TaskChef performs bounded deferred reconciliation, because
-the terminal lifecycle callback precedes Codex's final output write. Historical
+the terminal lifecycle callback precedes Codex's final output write. The
+dashboard also preloads missing, interrupted, and retry-eligible usage in a
+bounded background queue at startup, after task changes, and on a periodic
+recovery pass; opening task details is not required to start collection. Historical
 tasks may show a trustworthy task total while older turns remain “Token usage
 unavailable” when no cumulative turn boundaries were recorded. Input, cached
 input, output, reasoning, and total counts retain ccusage's categories. Dollar
@@ -361,6 +364,8 @@ wall-clock elapsed time, not model compute time, and malformed or reversed
 timestamp ranges are shown as unavailable.
 The header shows the running TaskChef package version reported by the same
 bounded health identity used for compatible-listener checks.
+The Settings page shows the ccusage version reported by the executable that
+TaskChef resolves at runtime.
 The canonical port is owned by a dashboard session process initialized by the
 TaskChef MCP before its tool transport connects. Health identity records a
 `session` launcher, and MCP recovery reuses only another exact-compatible,

package/docs/dashboard-lifecycle.md

@@ -33,6 +33,13 @@ the token total and API-equivalent USD estimate. Task cards keep the latest
 cumulative value visible during a newer active turn and label it as updating;
 pending is reserved for tasks that do not have a usage snapshot yet.
 
+The dashboard owns a small background recovery queue for derived usage. It
+deduplicates tasks, limits concurrent ccusage reads, preserves successful cache
+records, and revisits missing, interrupted, or cooldown-expired records without
+requiring a detail request. The queue starts with the dashboard, reacts to task
+log revisions, performs periodic recovery passes, and stops with the dashboard.
+Settings reports the version returned by the resolved ccusage executable.
+
 ![Pending token usage in the task detail view](images/dashboard-token-pending.jpg)
 
 ## Reported work presentation

package/docs/spec.md

@@ -162,6 +162,13 @@ into totals a second time.
 
 After a terminal report, TaskChef MUST mark the turn `calculating` and perform
 bounded deferred reconciliation without delaying the lifecycle response.
+The dashboard MUST also preload eligible derived usage in its existing service
+lifecycle without requiring a task-detail request. Startup, task-log changes,
+and periodic recovery passes MUST consider missing, interrupted, and
+cooldown-expired records; successful current-generation records MUST remain
+cached. Background work MUST be deduplicated, MUST enforce a small global
+concurrency limit, MUST use bounded delayed retries, and MUST stop when the
+dashboard closes.
 Per-turn usage MUST be a non-negative delta between adjacent reliable cumulative
 boundaries. A first recorded turn MAY use zero as its baseline. Historical
 turns without boundaries and decreasing or ambiguous snapshots MUST be labeled
@@ -183,6 +190,8 @@ cumulative boundaries use different analyzer versions, requested pricing modes,
 or declared cost coverage. For GPT-5.6 with ccusage 20.0.20, provenance MUST
 disclose unverified cache-write coverage and TaskChef MUST NOT claim that the
 estimate includes those charges.
+The dashboard Settings response MUST report the provider version returned by
+the executable resolved for runtime use, not merely copy the dependency pin.
 
 Task IDs and non-null thread identities MUST be unique. The immutable intent
 fields MUST NOT change after recording.

package/package.json

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