taskchef 9.7.0 → 9.7.2

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "taskchef",
-  "version": "9.7.0",
+  "version": "9.7.2",
   "description": "Native Codex dashboard with lightweight project delegation.",
   "author": {
     "name": "Favo Yang",

package/docs/mcp-app.md

@@ -1,6 +1,6 @@
 # TaskChef sidebar
 
-The public app name is **TaskChef**. “TaskChef Next” remains the internal project name.
+The released app is **TaskChef**. The development app is **TaskChef Dev**, with plugin and MCP server ID `taskchef-dev`.
 
 The native dashboard requires Node.js 22.18+, 23.2+, or 24+ for local Codex SQLite access.
 
@@ -196,7 +196,7 @@ Use this order for every development change:
 For a full Dev update, give the staging package a unique development version
 in both `package.json` and `.codex-plugin/plugin.json` (and package-lock metadata
 if present), such as `9.0.0-dev.1`. Set only the staging manifest's plugin name
-to `taskchef-next`; keep the source release manifest named `taskchef`.
+to `taskchef-dev`; keep the source release manifest named `taskchef`.
 Before installing the staging package through the local development marketplace,
 run:
 
@@ -205,12 +205,21 @@ node scripts/prepare-mcp-app-preview.js /path/to/staging/plugin
 ```
 
 The script sets the copied plugin’s display name to **TaskChef Dev** and
-normalizes its MCP server key to `taskchef-next`. It refuses release manifests. The sidebar tool reads its
+normalizes its MCP server key to `taskchef-dev`. It refuses release manifests. The sidebar tool reads its
 name from that manifest. The release checkout and release package keep
 **TaskChef**. Run this step again whenever rebuilding the development package.
 Do not register a standalone preview MCP server alongside these two plugins.
 Restart Codex after changes to plugin identity or backend code.
 
+When migrating an existing Dev installation, prepare a new staging package with
+plugin ID `taskchef-dev` and a unique Dev version. Set its local marketplace
+name and plugin entry to `taskchef-dev`, then add the marketplace and install
+`taskchef-dev@taskchef-dev`. Verify the new installation before removing
+`taskchef-next@taskchef-next-preview` and the old marketplace registration.
+Both editions continue to share `~/.agents/taskchef`; preserve that state and
+the legacy GitHub credential key. After restarting Codex, the Dev skill is
+`$taskchef-dev:delegate` and its MCP namespace is `taskchef_dev`.
+
 ## Local UI review without restarting Codex
 
 For UI-only changes, update the HTML in the installation that the running MCP
@@ -222,10 +231,10 @@ folder. Its next resource read then fails with `ENOENT`, and the sidebar shows
 From the source checkout, run:
 
 ```sh
-npm run update:mcp-app-preview -- /path/to/the/running/taskchef-next/version
+npm run update:mcp-app-preview -- /path/to/the/running/taskchef-dev/version
 ```
 
-The helper builds the UI, checks the development plugin ID is `taskchef-next`, and replaces only
+The helper builds the UI, checks the development plugin ID is `taskchef-dev`, and replaces only
 `src/mcp-app/dist/index.html` atomically. It preserves the plugin version, server
 code, dependencies, and local data. It refuses missing or redirected HTML paths.
 Then right-click **TaskChef Dev** in the Codex sidebar and choose **Refresh**.
@@ -351,13 +360,13 @@ uses this repository's GitHub token; no shared-marketplace deploy key is needed.
 If the push loses a race with another main update, rerun the Release workflow
 on main to retry after checking the current published version. Do not force push.
 
-Keep TaskChef Dev in a separate local marketplace named `taskchef-next-preview`,
-with plugin ID `taskchef-next` and display name **TaskChef Dev**. Store that
+Keep TaskChef Dev in a separate local marketplace named `taskchef-dev`,
+with plugin ID `taskchef-dev` and display name **TaskChef Dev**. Store that
 marketplace and its staging packages in a persistent local folder, outside
 this public checkout. Its catalog uses `source.source: local` with a path to
 the prepared staging package. Add that folder with
 `codex plugin marketplace add /path/to/local-dev-marketplace`, then install
-`codex plugin add taskchef-next@taskchef-next-preview`. This can coexist with
+`codex plugin add taskchef-dev@taskchef-dev`. This can coexist with
 `taskchef@taskchef`. Never rename the source release manifest for Dev.
 
 Retire the old shared catalog entry only after this repository's catalog is
@@ -378,14 +387,14 @@ There is no custom range. Dates use the view's local timezone, including DST.
 Range changes and reopening Usage query one shared history snapshot without
 rescanning logs. The combined snapshot is also saved atomically with private file
 permissions under `~/.agents/taskchef/cache/usage-history/`, scoped by Codex home
-and CLI/exec visibility. It contains the fields needed for charts, including
+and the all-sources accounting policy. It contains the fields needed for charts, including
 weekly readings, and no message content or per-file parsing records. After an
 MCP server restart, the first Usage request loads a compatible disk snapshot
 and returns saved charts before refreshing history in the background. Range and
 timezone changes share that refresh. A missing, damaged, or incompatible snapshot
 falls back to a normal scan. A failed background refresh retains the last good
-snapshot, shows a Retry action, and never overwrites it with a failed result. The snapshot is scoped by CLI/exec visibility, independently of
-range or timezone. After one minute it refreshes in the background while cached
+snapshot, shows a Retry action, and never overwrites it with a failed result. The snapshot is independent of Board visibility, range, and timezone. Older
+visibility-filtered snapshots are not reused. After one minute it refreshes in the background while cached
 charts remain visible. Refresh explicitly rebuilds it, reusing existing per-file
 metadata and incremental parsing caches. Unchanged files retain parsed records
 on disk across restarts and turn or price changes. A session filename index
@@ -419,10 +428,11 @@ interpolate between recorded points; they are not additional measurements.
 Codex writes service-provided seven-day primary or secondary allowance windows
 into local rollout token-count events, including events without token counters.
 TaskChef reads these logs; it does not poll the service for current allowance.
-Root-chat CLI/exec visibility controls which logs supply observations.
+Weekly observations include all root-chat sources, regardless of Board visibility.
 
-Archived chats and descendant usage are included. CLI/exec visibility settings
-still apply to root chats. Descendants are counted once under their root chat's
+Desktop, CLI, exec, archived chats, and descendant usage are included. Board
+visibility settings do not narrow Usage or change its cached history.
+Descendants are counted once under their root chat's
 current project. Unassigned chats share one Unassigned project. Daily usage
 comes from recorded call timestamps, not chat creation or last-update dates.
 Unexplained cumulative counter gaps stay in lifetime totals but are excluded
@@ -440,9 +450,9 @@ refreshes, with their last-update time and scan progress.
 Calendar sits beside Board and Usage. It opens on the current local month;
 previous/next arrows surround the month title. Next is disabled at the current
 local month, so future months cannot be selected. There is no Today control.
-Arrows stay hidden until the month navigation is hovered or contains focus;
-a clicked arrow remains visible while focused. This also applies in embedded
-hosts that do not report mouse hover support. Project, search, update window, and Pinned
+Arrows are always visible, with a dimmed Next arrow at the current month.
+Button borders appear only when an enabled arrow is hovered; keyboard focus
+keeps a visible outline. Project, search, update window, and Pinned
 filters are remembered locally. An unavailable saved project resets to All
 projects only after the project inventory loads.
 Project, Search Chats, Pinned, and native visibility settings apply. The Board's
@@ -457,6 +467,8 @@ Each chat's recorded turn intervals become calendar dates in the viewer's
 timezone. Adjacent dates merge into one bar. One full idle date breaks the bar,
 including weekends; a later segment has a resumed marker and opens the same
 chat Details. Continuous work across a week boundary uses continuation arrows.
+Hovering a bar highlights every visible segment of the same chat across the month,
+including resumed segments.
 An exact midnight end does not occupy the following date. A current running
 turn extends to now; completed turns do not extend through idle review waits.
 Project colors stay consistent when navigating or filtering. Crowded weeks show

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "taskchef",
-  "version": "9.7.0",
+  "version": "9.7.2",
   "description": "A native Codex dashboard for chats, usage, pull requests, and schedules.",
   "license": "Apache-2.0",
   "author": "Favo Yang",

package/scripts/migrate-taskchef-state.js

@@ -28,7 +28,7 @@ export async function assertNoStateWriters(paths, runCommand = run) {
     if (!identities.has(root)) {
       let name;
       try { name = JSON.parse(await readFile(join(root, ".codex-plugin/plugin.json"), "utf8")).name; } catch { /* Unrelated process. */ }
-      identities.set(root, ["taskchef", "taskchef-next"].includes(name));
+      identities.set(root, ["taskchef", "taskchef-dev", "taskchef-next"].includes(name));
     }
     return identities.get(root);
   }

package/src/codex-session-scanner.js

@@ -674,10 +674,10 @@ export class CodexSessionScanner {
     }
     return { month, timeZone, chats };
   }
-  async usageAnalytics({ range, timeZone, settings }) {
-    return aggregateUsage(await this.usageHistory({ settings }), { range, timeZone, now: this.now() });
+  async usageAnalytics({ range, timeZone }) {
+    return aggregateUsage(await this.usageHistory(), { range, timeZone, now: this.now() });
   }
-  async usageHistory({ settings, onProgress = () => {}, rescan = false }) {
+  async usageHistory({ onProgress = () => {}, rescan = false } = {}) {
     if (rescan) this.sessionUsage.inventoryAt = -Infinity;
     const snapshot = await this.refresh();
     if (!snapshot.healthy) throw new Error(snapshot.scan.error);
@@ -690,8 +690,8 @@ export class CodexSessionScanner {
     })), records.projects);
     const families = [];
     const seen = new Set();
-    // History includes archived chats. CLI/exec preferences still apply.
-    const tasks = grouped.tasks.filter(task => (settings.showCli || task.observed?.source !== "cli") && (settings.showExec || task.observed?.source !== "exec"));
+    // Accounting includes every root, independent of Board visibility settings.
+    const tasks = grouped.tasks;
     let completed = 0;
     onProgress({ completed, total: tasks.length });
     for (const task of tasks) {