taskchef 8.6.2 → 8.7.0

package/.codex-plugin/plugin.json

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

package/README.md

@@ -47,10 +47,14 @@ every task.
 
 The screenshots in this walkthrough use illustrative demo data. Open the
 dashboard beside TaskChef master to see both tasks across your projects.
-In Codex, you can also call `open_taskchef_board` for a compact [sidebar app](docs/mcp-app.md)
-with a task board, task details, chat links, and confirmed manual status changes.
-**Board** groups tasks by **Working**, **Needs input**, **Completed**, and
-**Failed** so you can see their status at a glance.
+In Codex, call `open_taskchef_board` for the [TaskChef sidebar](docs/mcp-app.md).
+It reads local Codex data and groups chats as **Scheduled**, **Running**,
+**Waiting for input/review**, and **Done**. Interrupted chats stay in Waiting with an **Interrupted** tag. Empty board columns remain visible with a short message. Ambiguous records stay
+**Unverified**. Running follows the latest selected turn
+state; these labels do not prove task outcomes. Mark Done writes only TaskChef's separate local state. A new Codex turn
+resets that mark.
+The main dashboard's **Board** groups reported tasks by **Working**,
+**Needs input**, **Completed**, and **Failed** so you can see their status at a glance.
 
 ![TaskChef master beside the dashboard board with recipe-book working and payments needing input](docs/images/readme-board.png)
 

package/assets/README.md

@@ -0,0 +1,19 @@
+# TaskChef icons
+
+All icons use the same chef hat and T artwork. The SVG files are the editable sources.
+
+| Use | File | Background |
+| --- | --- | --- |
+| App and navbar, light theme | `taskchef.svg` | Rounded orange square; transparent outside |
+| App and navbar, dark theme | `taskchef-dark.svg` | Rounded orange square; transparent outside |
+| App icon PNG export, dark theme | `taskchef-app-rounded.png` | Rounded orange square; transparent outside |
+| Sidebar preview, light theme | `taskchef-sidebar-light.svg` | Dark strokes; transparent |
+| Sidebar preview, dark theme | `taskchef-sidebar-dark.svg` | Light strokes; transparent |
+| Codex sidebar | `taskchef-sidebar.svg` | Monochrome `currentColor`; transparent |
+| GitHub and other services that apply a circle crop | `taskchef-avatar-square.svg`, `taskchef-avatar-square.png` | Solid orange to all four edges |
+
+The app and sidebar SVGs are unchanged. The square avatar uses the current dark-theme navbar artwork and colors. Its hat is enlarged by 30% and centered for circle crops. The two sidebar preview files show the same light/dark colors that the MCP server already provides; the runtime continues to use the theme-neutral template. Both PNG exports are 512 × 512 pixels.
+
+For GitHub, upload `taskchef-avatar-square.png` and set the badge background color to `#F59E0B`. Keep the full image when GitHub asks for a crop.
+
+Export PNGs directly from the SVG sources. Do not use an image generator: these are flat vector icons, with no gradients, shadows, or texture.

package/assets/taskchef-avatar-square.svg

@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="512" height="512" viewBox="0 0 48 48" fill="none">
+  <rect width="48" height="48" fill="#F59E0B"/>
+  <g transform="translate(24 24) scale(1.3) translate(-24 -23.5)">
+  <path d="M15 37V27.5C11.9 26.3 10 23.6 10 20.5C10 16.4 13.4 13 17.5 13C19 10 21.2 8.5 24 8.5C26.8 8.5 29 10 30.5 13C34.6 13 38 16.4 38 20.5C38 23.6 36.1 26.3 33 27.5V37H15Z" fill="#FFFBEB"/>
+  <path d="M18.5 20H29.5M24 20V31" stroke="#78350F" stroke-width="3.5" stroke-linecap="round"/>
+  <path d="M15 37H33" stroke="#78350F" stroke-width="3" stroke-linecap="round"/>
+  </g>
+</svg>

package/assets/taskchef-sidebar-dark.svg

@@ -0,0 +1,6 @@
+<svg style="color:#dddddd" xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 20 20" fill="none">
+  <g transform="scale(.625) translate(-8 -7)" stroke="currentColor" stroke-width="2.128" stroke-linecap="round" stroke-linejoin="round">
+    <path d="M15 37V27.5C11.9 26.3 10 23.6 10 20.5C10 16.4 13.4 13 17.5 13C19 10 21.2 8.5 24 8.5C26.8 8.5 29 10 30.5 13C34.6 13 38 16.4 38 20.5C38 23.6 36.1 26.3 33 27.5V37H15Z"/>
+    <path d="M18.5 20H29.5M24 20V31M15 33H33"/>
+  </g>
+</svg>

package/assets/taskchef-sidebar-light.svg

@@ -0,0 +1,6 @@
+<svg style="color:#333333" xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 20 20" fill="none">
+  <g transform="scale(.625) translate(-8 -7)" stroke="currentColor" stroke-width="2.128" stroke-linecap="round" stroke-linejoin="round">
+    <path d="M15 37V27.5C11.9 26.3 10 23.6 10 20.5C10 16.4 13.4 13 17.5 13C19 10 21.2 8.5 24 8.5C26.8 8.5 29 10 30.5 13C34.6 13 38 16.4 38 20.5C38 23.6 36.1 26.3 33 27.5V37H15Z"/>
+    <path d="M18.5 20H29.5M24 20V31M15 33H33"/>
+  </g>
+</svg>

package/assets/taskchef-sidebar.svg

@@ -0,0 +1,6 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 20 20" fill="none">
+  <g transform="scale(.625) translate(-8 -7)" stroke="currentColor" stroke-width="2.128" stroke-linecap="round" stroke-linejoin="round">
+    <path d="M15 37V27.5C11.9 26.3 10 23.6 10 20.5C10 16.4 13.4 13 17.5 13C19 10 21.2 8.5 24 8.5C26.8 8.5 29 10 30.5 13C34.6 13 38 16.4 38 20.5C38 23.6 36.1 26.3 33 27.5V37H15Z"/>
+    <path d="M18.5 20H29.5M24 20V31M15 33H33"/>
+  </g>
+</svg>

package/docs/advanced-guide.md

@@ -7,15 +7,10 @@ Detailed setup, operation, recovery, and development reference for TaskChef.
 TaskChef requires Node.js 18 or newer, Git, Codex desktop, and local access to
 the projects that will receive work.
 
-TaskChef pins [`ccusage`](https://github.com/ccusage/ccusage) as an optional
-dependency for dashboard token and API-equivalent cost estimates. A normal npm
-installation uses that package-local executable; plugin-only installations use
-an npm-cache-friendly `npx` fallback to resolve the same exact version's native
-executable. `npx` never launches the analyzer against Codex data. TaskChef then
-requests ccusage's live-capable online pricing and falls back to its bundled
-offline snapshot, while never parsing Codex rollout files itself. Lifecycle
-reporting and the dashboard continue to work when ccusage, npm, or pricing is
-unavailable.
+TaskChef uses its own accounting engine for token usage and API-equivalent cost
+estimates. Usage requires Node.js 22.18+ and readable local Codex records.
+It includes linked subagents and uses the same pricing data as the board.
+Lifecycle reporting and the dashboard continue to work when usage is unavailable.
 
 ```sh
 codex plugin marketplace add favoyang/codex-plugins
@@ -49,7 +44,7 @@ The canonical workspace is `~/.agents/taskchef`. TaskChef owns only:
 AGENTS.md       managed dispatcher instructions plus user additions
 taskchef.json   schema-2 Codex project index, dashboard preference, and delegation metadata
 tasks.jsonl     one task snapshot per line (schema 10; schema 4-9 migration supported)
-.taskchef-usage.json   optional mode-0600 ccusage snapshot and turn-boundary cache
+.taskchef-usage.json   optional mode-0600 normalized usage cache
 ```
 
 To inspect or manually adjust the project index later, use the bootstrap skill:
@@ -356,24 +351,21 @@ will keep the feature disabled until Codex exposes a reliable supported
 app-callable archive interface or guarantees CLI compatibility. The dormant
 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. 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
-figures are labeled API-equivalent estimates; provenance identifies the online
-pricing request or offline fallback mode, and zero-priced unknown models show
-cost unavailable rather than a misleading `$0.00`. Per-turn cost is also
-unavailable when its cumulative boundaries used different ccusage versions or
-pricing modes. TaskChef displays the cumulative estimate supplied by ccusage
-without applying a separate model-family or cache-write coverage policy.
+Task details show chat totals and native per-turn usage from saved Codex records.
+Historical tasks are read when needed, rather than scanned at startup. A turn
+without a matching native Codex turn ID shows usage unavailable; its chat total
+can still be shown. Missing logs and parent links make the known subtotal
+incomplete. Input, cached input, output, reasoning, and total counts use Codex's
+categories. Cached input and reasoning are subsets, not additional tokens.
+Dollar figures are API-equivalent estimates, using the board's pricing table.
+Unknown prices show cost unavailable or a known priced subtotal. Existing saved
+usage projections remain readable. A partial scan cannot replace a larger known
+historical subtotal; missing model prices cannot erase a saved priced subtotal.
+`.taskchef-usage.json` holds the web view's
+normalized projections; the underlying engine reuses the board disk caches.
+
 The same detail view reports lifecycle wall-clock elapsed time independently of
-ccusage. Each terminal turn shows **Elapsed** from `startedAt` to
+token accounting. Each terminal turn shows **Elapsed** from `startedAt` to
 `result.updatedAt`; **Total reported work** sums only valid terminal-turn
 durations, excluding idle gaps and unfinished work. A working turn shows live
 **Elapsed so far** without contributing to the total. This is reported
@@ -381,8 +373,7 @@ 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 Settings page identifies TaskChef as the usage provider.
 The canonical port is normally owned by a dashboard session process initialized
 by the TaskChef MCP before its tool transport connects. MCP recovery reuses an
 exact-compatible same-workspace dashboard and reports its actual launcher;

package/docs/dashboard-ui.md

@@ -23,3 +23,18 @@ rules.
 
 Check a dashboard page at desktop and narrow widths. Confirm keyboard focus,
 control operation, reachable overflow, and a clean browser console.
+
+### Latest-turn request and response
+
+Running local Codex cards show the current request. Other cards show the latest
+turn's response. Cards use a plain two-line preview without request bubbles.
+Details pairs the same turn's request and response, each initially capped at
+three lines with a Show more control. The request uses a right-aligned bubble.
+Actual scheduled requests show their recorded instructions with a clock;
+human follow-ups in scheduled chats use the normal request bubble.
+Quoted selections render as Markdown quotes. File and image references show
+attachment names, while generated request headings and context metadata are
+removed from the display. Recorded input remains unchanged.
+
+Earlier-turn PR fallbacks remain separate from this content: the status popup
+shows `(Earlier turn PR)` below the PR link, aligned with the other row text.

package/docs/diagrams/taskchef-next-reply-lookup.drawio

@@ -0,0 +1,38 @@
+<?xml version='1.0' encoding='utf-8'?>
+<mxfile host="Electron">
+  <diagram id="main" name="Current reply lookup">
+    <mxGraphModel page="0" background="#ffffff">
+      <root>
+        <mxCell id="0" />
+        <mxCell id="1" parent="0" />
+        <mxCell id="title" value="&lt;b&gt;Example: find the current reply after reverting a chat&lt;/b&gt;" vertex="1" parent="1" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;fillColor=none;strokeColor=none;fontSize=23;spacing=0;">
+          <mxGeometry as="geometry" x="40" y="20" width="1100" height="50" />
+        </mxCell>
+        <mxCell id="chat" value="&lt;b&gt;1. Chat C&lt;/b&gt;&lt;hr&gt;state_5.sqlite&lt;br&gt;threads.id = C&lt;br&gt;&lt;br&gt;rollout_path names&lt;br&gt;…-C_R.jsonl" vertex="1" parent="1" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;fillColor=#edf4ff;">
+          <mxGeometry as="geometry" x="40" y="110" width="235" height="205" />
+        </mxCell>
+        <mxCell id="rollout" value="&lt;b&gt;2. Rollout R&lt;/b&gt;&lt;hr&gt;Take R from the&lt;br&gt;selected filename.&lt;br&gt;&lt;br&gt;This is a lookup step,&lt;br&gt;not a database table." vertex="1" parent="1" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;fillColor=#fff8df;">
+          <mxGeometry as="geometry" x="340" y="110" width="235" height="205" />
+        </mxCell>
+        <mxCell id="turn" value="&lt;b&gt;3. Latest turn T&lt;/b&gt;&lt;hr&gt;thread_turns&lt;br&gt;thread_id = R&lt;br&gt;&lt;br&gt;Latest rollout_ordinal&lt;br&gt;gives turn_id = T." vertex="1" parent="1" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;fillColor=#edf9f4;">
+          <mxGeometry as="geometry" x="640" y="110" width="235" height="205" />
+        </mxCell>
+        <mxCell id="reply" value="&lt;b&gt;4. Saved reply I&lt;/b&gt;&lt;hr&gt;thread_items&lt;br&gt;thread_id = R&lt;br&gt;turn_id = T&lt;br&gt;item_id = final_agent_item_id&lt;br&gt;&lt;br&gt;Read item_json.text." vertex="1" parent="1" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;fillColor=#edf9f4;">
+          <mxGeometry as="geometry" x="940" y="110" width="255" height="205" />
+        </mxCell>
+        <mxCell id="edge0" parent="1" source="chat" target="rollout" edge="1" style="edgeStyle=orthogonalEdgeStyle;endArrow=classic;strokeWidth=2;">
+          <mxGeometry as="geometry" relative="1" />
+        </mxCell>
+        <mxCell id="edge1" parent="1" source="rollout" target="turn" edge="1" style="edgeStyle=orthogonalEdgeStyle;endArrow=classic;strokeWidth=2;">
+          <mxGeometry as="geometry" relative="1" />
+        </mxCell>
+        <mxCell id="edge2" parent="1" source="turn" target="reply" edge="1" style="edgeStyle=orthogonalEdgeStyle;endArrow=classic;strokeWidth=2;">
+          <mxGeometry as="geometry" relative="1" />
+        </mxCell>
+        <mxCell id="note" value="&lt;b&gt;The chat ID stays C. The selected history may change to R.&lt;/b&gt;&lt;br&gt;&lt;br&gt;Ordinary filename: …-C.jsonl → history lookup uses C.&lt;br&gt;After revert: …-C_R.jsonl → history lookup uses R. Old rows under C may remain.&lt;br&gt;Real IDs are UUIDs; compressed .jsonl.zst files use the same rule.&lt;br&gt;If no final reply is linked yet, TaskChef reads the latest saved agent message in turn T.&lt;br&gt;These arrows show lookup steps, not SQL foreign-key constraints." vertex="1" parent="1" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;fillColor=#f7f9fc;">
+          <mxGeometry as="geometry" x="40" y="365" width="1155" height="205" />
+        </mxCell>
+      </root>
+    </mxGraphModel>
+  </diagram>
+</mxfile>

package/docs/diagrams/taskchef-next-storage.drawio

@@ -0,0 +1,41 @@
+<?xml version='1.0' encoding='utf-8'?>
+<mxfile host="Electron">
+  <diagram id="main" name="Files and tables">
+    <mxGraphModel page="0" background="#ffffff">
+      <root>
+        <mxCell id="0" />
+        <mxCell id="1" parent="0" />
+        <mxCell id="title" value="&lt;b&gt;Codex storage: which table belongs where&lt;/b&gt;" vertex="1" parent="1" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;fillColor=none;strokeColor=none;fontSize=24;spacing=0;">
+          <mxGeometry as="geometry" x="40" y="20" width="1030" height="45" />
+        </mxCell>
+        <mxCell id="state" value="&lt;b&gt;state_5.sqlite — chat inventory&lt;/b&gt;" vertex="1" parent="1" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;swimlane;container=1;startSize=48;fillColor=#edf4ff;swimlaneFillColor=#edf4ff;">
+          <mxGeometry as="geometry" x="40" y="90" width="470" height="500" />
+        </mxCell>
+        <mxCell id="threads" value="&lt;b&gt;threads&lt;/b&gt;&lt;hr&gt;id: stable chat ID&lt;br&gt;name / title, project folder, archived&lt;br&gt;rollout_path: selected history file&lt;br&gt;model, tokens, timestamps" vertex="1" parent="state" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;">
+          <mxGeometry as="geometry" x="20" y="65" width="430" height="170" />
+        </mxCell>
+        <mxCell id="children" value="&lt;b&gt;thread_spawn_edges&lt;/b&gt;&lt;hr&gt;parent_thread_id → child_thread_id&lt;br&gt;Chat IDs; used to hide subagents&lt;br&gt;and count direct children" vertex="1" parent="state" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;">
+          <mxGeometry as="geometry" x="20" y="265" width="430" height="140" />
+        </mxCell>
+        <mxCell id="history" value="&lt;b&gt;thread_history_1.sqlite — turns and messages&lt;/b&gt;" vertex="1" parent="1" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;swimlane;container=1;startSize=48;fillColor=#edf9f4;swimlaneFillColor=#edf9f4;">
+          <mxGeometry as="geometry" x="550" y="90" width="520" height="500" />
+        </mxCell>
+        <mxCell id="turns" value="&lt;b&gt;thread_turns&lt;/b&gt;&lt;hr&gt;thread_id: selected rollout ID&lt;br&gt;turn_id, status, start / end time&lt;br&gt;first_user_item_id, final_agent_item_id" vertex="1" parent="history" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;">
+          <mxGeometry as="geometry" x="20" y="60" width="480" height="140" />
+        </mxCell>
+        <mxCell id="items" value="&lt;b&gt;thread_items&lt;/b&gt;&lt;hr&gt;thread_id + turn_id + item_id&lt;br&gt;item_type, item_json: saved message or tool data" vertex="1" parent="history" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;">
+          <mxGeometry as="geometry" x="20" y="225" width="480" height="120" />
+        </mxCell>
+        <mxCell id="projection" value="&lt;b&gt;thread_history_projection_state&lt;/b&gt;&lt;hr&gt;Rollout ID, next byte offset and ordinal&lt;br&gt;Tracks history import; not queried by the board" vertex="1" parent="history" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;">
+          <mxGeometry as="geometry" x="20" y="365" width="480" height="110" />
+        </mxCell>
+        <mxCell id="jsonl" value="&lt;b&gt;Selected rollout .jsonl / .jsonl.zst file&lt;/b&gt;&lt;hr&gt;Ordered records: type, timestamp, payload&lt;br&gt;Examples: session_meta, event_msg, response_item&lt;br&gt;Saved history used to build the history database.&lt;br&gt;TaskChef reads logs only for optional selected-chat details." vertex="1" parent="1" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;fillColor=#f4effa;">
+          <mxGeometry as="geometry" x="40" y="620" width="680" height="155" />
+        </mxCell>
+        <mxCell id="scope" value="&lt;b&gt;Reading this diagram&lt;/b&gt;&lt;br&gt;&lt;br&gt;Boxes inside a database are tables.&lt;br&gt;The log is a separate file.&lt;br&gt;Selected fields only; full notes are in the storage guide." vertex="1" parent="1" style="whiteSpace=wrap;html=1;fontSize=16;fontColor=#172b4d;align=left;verticalAlign=top;spacing=14;fillColor=#ffffff;strokeColor=#9caec2;fillColor=none;strokeColor=none;">
+          <mxGeometry as="geometry" x="750" y="620" width="320" height="155" />
+        </mxCell>
+      </root>
+    </mxGraphModel>
+  </diagram>
+</mxfile>

package/docs/mcp-app.md

@@ -1,11 +1,266 @@
-# TaskChef sidebar app
+# TaskChef sidebar
 
-Call `open_taskchef_board` in Codex to open the TaskChef MCP App in the sidebar. The app reads the same local workspace and task log as the web dashboard. It needs the TaskChef MCP server to be connected and an MCP Apps-capable Codex host.
+The public app name is **TaskChef**. “TaskChef Next” remains the internal project name.
 
-The sidebar uses the dashboard's task cards, horizontal board lanes, and detail view. Switch between **List** and **Board**. In List, filter by project, update window, and status; status counts reflect the selected project and window, and the summary reports visible tasks. Board shows all status lanes for the selected project and window. Task cards include request and result summaries, relative update times, reported work and usage summaries, and related GitHub links. Select a task for its usage, activity timeline, instruction, and metadata.
+TaskChef requires Node.js 22.18+, 23.2+, or 24+ for read-only SQLite connections. The rest of TaskChef continues to support the package's Node.js 18 minimum. An unsupported Node runtime produces a fatal version error before TaskChef opens a database.
 
-**Open chat** opens a linked Codex thread, or the configured project when the task has no usable direct chat link. **Mark completed** and **Mark failed** require confirmation and use the same audited, conflict-checked manual transition as the web dashboard. The app refreshes every five seconds and offers manual refresh. A refresh does not replace a newer selection or a changed task with an older response.
+Call `open_taskchef_board` in Codex to open **TaskChef**. In a sidebar or fullscreen host view, it shows the read-only board, filters, and chat details. In an inline chat view, it shows a short recent-chat list with direct **Open chat** actions. The app uses local Codex metadata and does not modify the TaskChef dispatcher workspace.
 
-The UI is a bundled `ui://taskchef/task-board/v2` MCP resource. Its read, open, and transition calls are app-only tools on the existing stdio MCP server. The iframe does not read files or contact the local HTTP dashboard. The web dashboard remains available separately.
+The server reads all eligible top-level chats from `~/.codex/state_5.sqlite` and their latest turn from `~/.codex/thread_history_1.sqlite`. Both SQLite connections are read-only. It excludes typed subagents and Guardian reviews, JSON subagent sources, known `thread_spawn_edges` children, chats with no turn record. Standalone `source=exec` and regular `source=cli` chats remain eligible in the collector, but the view hides them by default. The plugin details page has native switches for Show exec sessions, Show CLI sessions, and Show archived chats. The MCP server stores these choices in `~/.agents/taskchef-next/settings.json`, shared by all TaskChef views. Each visible poll reads the current settings, even when the database snapshot is unchanged. These choices apply to the board, counts, project choices, Details eligibility, and the compact inline view. Archived chats are hidden by default and use their own Archived column when shown. Details shows the recorded lifetime direct child count. Names and titles can contain user text; the app prefers name, then title, then a chat ID fallback.
 
-For development, run `npm run build:mcp-app` after editing `src/mcp-app/react/`. The generated single-file resource is `src/mcp-app/dist/index.html`. Run `npm run check:mcp-app` and `npm test` before release. Reopen the sidebar after rebuilding to load the new resource.
+The board uses these queue labels:
+
+| Column | Rule |
+| --- | --- |
+| Scheduled | Active schedule with a normally completed scheduled prompt, a completed human turn whose PRs are all merged, or a human turn acknowledged by a drop into Scheduled. |
+| Running | Latest selected turn is `inProgress`. There is no age cutoff. |
+| Waiting for input/review | Latest turn completed, interrupted, or failed and the chat remains open. Interrupted or failed turns have an Interrupted tag. This does not prove Codex asked a question. |
+| Done | A chat is marked Done in TaskChef, or its latest turn completed and all attached PRs are confirmed merged. Manual marks require any attached PRs to be confirmed merged. Both require no active schedule. This does not prove the larger task succeeded. |
+| Archived | Chat is archived in Codex. Hidden by default; separate from Done. |
+| Unverified | An unrecognized turn state. |
+
+Archived takes precedence. Manual Done marks apply only without active schedules; every attached PR must be confirmed merged. A normally completed scheduled prompt returns to Scheduled regardless of PR status. After a completed human turn, attached PRs determine Done or Waiting for ordinary chats, and Scheduled or Waiting for actively scheduled chats. A manual acknowledgement returns an idle scheduled human turn to Scheduled. Active schedules remain visible as a badge even when the chat is Running or Waiting. After ordinary input, a completed scheduled chat goes to Waiting. The app reads active heartbeat links from `automations/*/automation.toml` and the latest first input from `thread_items`. It checks the observed `<heartbeat><automation_id>` wrapper; this internal format can change. Missing or unrecognized input markers use Waiting rather than guessing Scheduled. Schedule read errors appear as a warning. Paused schedules do not give an active schedule badge. Cron run history is not treated as an active heartbeat chat.
+
+**Mark Done** changes only `~/.agents/taskchef-next/done.json`, using a lock and atomic write. The mark is bound to the current turn ID, so a new turn resets it. There is no Reopen button; send a new prompt in Codex to start another turn. Archived, in-progress, and actively scheduled chats cannot be marked Done from this app. PR-linked chats require confirmed merge status before a Done drop is allowed. Codex databases, rollout files, and dispatcher task reports are never modified. An unreadable or invalid Done state file produces a separate local-state error and blocks Done changes; the app preserves the file and does not call it a Codex database failure. The inferred input source and display-formatted request are returned to the app; original recorded input is not modified. See [the research note](taskchef-next-status-research.md) for the optional Luna judgment route.
+
+Both databases and the expected tables must be available. Missing or incompatible databases, or failed queries, produce a fatal app error and clear the visible inventory. Rollout files never replace database inventory or status. The selected-chat detail may optionally read a bounded head and tail of the JSONL file at its database `rollout_path` for message counts and byte coverage. The path stays server-side. This detail never changes the database-derived status. If the path or file is absent or cannot be parsed, database metadata remains available. The board returns bounded latest-turn request and response excerpts for cards. Details returns the full recorded request and response for that turn, not the whole conversation. All reads are local and read-only.
+
+In sidebar or fullscreen mode, the mounted app requests a fresh snapshot every five seconds while `document.visibilityState` is `visible`. It pauses polling when the document becomes hidden and refreshes immediately when visible again. If Codex only hides a mounted iframe with CSS, the document may remain visible and polling may continue. Inline mode loads once and does not poll; manual **Refresh** remains available. Switching from inline to a full view starts polling and requests a fresh snapshot. Whether the host hides or unmounts the app is host-dependent. Mount, React unmount, document `visibilitychange`, window `pagehide`, display-mode, and host-teardown events are logged as single-string browser console warnings with the `[TaskChef] TaskChef lifecycle:` prefix, followed by JSON with only `visibility` and `displayMode`. For browser debugging, right-click the sidebar app and select **Dev Tools** in Codex. The console shows these lifecycle events. Repeated events are logged individually. `pagehide` can indicate iframe navigation or disposal even when React cleanup does not run. It does not prove that a sidebar switch disposed the iframe: the host may keep the iframe mounted, and a destroyed iframe may not deliver a final event.
+
+The UI is bundled as the `ui://taskchef/task-board/v3/<package-version>` MCP resource. The GitHub settings resource also includes the package version. Resource registration and tool metadata share these release-specific URIs, so a new release advertises a different host UI cache key. This does not live-reload an already-open sidebar. Same-version preview edits keep their URI and use explicit sidebar Refresh. Build the UI with `npm run build:mcp-app`; run `npm run check:mcp-app` and the relevant tests before release. Use Codex’s sidebar context-menu **Refresh** to reload its HTML and restart the widget. The app’s own Refresh button updates board data only.
+
+The selected rollout filename determines the history lookup ID. Ordinary chats use the chat ID. After a revert, Codex keeps the chat ID but selects a filename ending in `<chat-id>_<rollout-id>.jsonl`. `thread_history_1.sqlite.thread_turns.thread_id` and `thread_items.thread_id` then use the rollout ID. The scanner follows `state_5.sqlite.threads.rollout_path` to select that ID; it does not open logs to get board status. For paginated history, a missing or unrecognized selected filename or invalid timestamp produces an explicit metadata error; old chat-ID rows are never substituted. A canonical filename must also identify the same stable chat. Legacy histories may use noncanonical filenames and retain Codex's stable-ID lookup rule.
+
+Old history rows can remain under the original chat ID. Reading those rows instead of the selected rollout can show an old interrupted turn. This was a TaskChef lookup bug, not evidence that Codex's database was stale.
+
+## Query and refresh rules
+
+Every visible-document poll checks for database changes, at five-second intervals. Unchanged database records are cached; there is no timestamp cursor or changed-row query. Concurrent requests share an in-flight refresh. Showing the document again or clicking Refresh requests an immediate refresh.
+
+Each database reload reads the eligible chat metadata, then runs `WHERE thread_id = ? ORDER BY rollout_ordinal DESC LIMIT 1` for each selected rollout ID. Codex's existing `idx_thread_turns_page` index supports this lookup. It no longer ranks every turn in the history table. The latest first input and linked final reply are read by their full primary keys: rollout ID, turn ID, and item ID; it never scans all message bodies. This server creates no indexes and writes nothing to Codex.
+
+There is no 300-chat cap. All eligible chats with a current-rollout turn are included. Done cards still expand in small groups in Board view. This reduces the initial rendered board while keeping complete counts. List view includes all matching chats. If larger installations become slow, measure database time and rendering separately before adding pagination.
+
+See the [storage schema](taskchef-next-storage.md), including the editable diagram and PNG.
+
+### TaskChef card content
+
+Cards show the chat title, project, a plain two-line preview, activity time, and Open chat. Running cards show the current request; other cards show the latest response. Excerpts are capped at 2,000 characters. Actual scheduled inputs display the recorded heartbeat instructions, even after the schedule is removed. No model summarizes or judges the text.
+
+Details pairs the full recorded latest-turn request and response, each initially capped at three lines with independent Show more/Show less controls. Selected quotes render as Markdown quotes and file/image references as named attachments. Generated request headings and context metadata are hidden in the display. Recorded input remains unchanged. Raw HTML is ignored and relative file links appear as text.
+
+Time labels use compact relative dates by default, with calendar dates available in settings. Schedule and PR icons appear in the status line. Queue reasons and lifetime subagent counts remain in Details. See [dashboard UI](dashboard-ui.md) for the presentation contract.
+
+
+
+
+### Database change checks
+
+Every visible five-second poll reads `PRAGMA data_version` on the same two read-only connections. The first poll, manual Refresh, or a changed counter runs the indexed database queries and replaces the cached records. An unchanged poll reuses those records; it does not query chat, turn, or item tables. Counters are captured before queries so commits during a read cause another read on the next poll. Neither connection holds a transaction between polls.
+
+Every poll separately reads and parses `automations/*/automation.toml`. For the Done file, each poll checks file identity, modification/change timestamps, and size; it reads and parses contents only when those metadata change. Manual Refresh also rereads the contents. A missing file means no manual marks. Added, removed, paused, or changed schedules and Done marks therefore apply on the next poll, including when the databases are unchanged. Queue labels are rebuilt from cached records and current schedules/Done marks. An open chat whose latest selected turn is `inProgress` remains Running regardless of timestamp age. Time passing alone never changes its queue label.
+
+Each poll checks both database file identities. Replacement reconnects and reloads; missing files or database/query errors discard the cache and clear the board with a fatal error. A later poll retries. Server shutdown closes the connections. The scan readout reports whether database records were queried or reused. This skips unchanged snapshots; it does not fetch only changed rows.
+
+PR-based Done labels use saved Codex attachments and authenticated GitHub status. After a completed turn, all attached PRs confirmed merged means Scheduled while a schedule is active, otherwise Done. An unmerged or unavailable PR means Waiting for review. See [GitHub setup](taskchef-next-github.md); registration and real sign-in remain required.
+
+### Native plugin settings
+
+TaskChef advertises `openai/settings` with `taskchef_settings_read` and
+`taskchef_settings_update`. The read tool returns the schema, current values,
+and Chat visibility, Card display, and GitHub groups. The update tool accepts
+changed Boolean preferences and preserves other values. **Show usage on cards** defaults to on; the other switches default
+to off. Disable it to hide token counts and estimated cost from cards and their
+status popups. Chat details always keeps its Usage section. Card timestamps default to compact ages: `<1m`, `1m`, `2h`, `5d`,
+and `1mo` (30-day months). Enable **Show calendar dates** to use the previous
+local format: `2:30PM` today, `Yesterday`, or `Oct 3rd`. Running cards keep
+their hourglass and elapsed work duration in either mode.
+Updates use the existing local workspace lock and atomic file writer. Codex
+SQLite files remain read-only. Invalid settings fail visibly rather than
+silently resetting preferences.
+
+Open the installed TaskChef plugin details page to edit its native
+settings. The sidebar receives them at its next visible refresh, or immediately
+when Refresh is clicked. Settings persist across sidebar and embedded views.
+The old browser-local visibility keys are no longer used; configure the native
+switches once after upgrading. The Board/List choice stays browser-local.
+See the [OpenAI structured settings specification](https://github.com/openai/mcp-extensions/blob/main/docs/spec.md#structured-settings).
+
+### Board presentation
+
+TaskChef exposes only Board. The List implementation remains in the
+source, but the Board/List selector is hidden and saved List choices are
+ignored. Interrupted chats appear in Waiting for input/review with an
+Interrupted tag; their recorded status remains available in Details.
+Scheduled, Running, Waiting, and Done remain visible when empty, with a short
+message specific to each column. This keeps their positions steady when chats
+change state or filters change. Archived remains an optional column.
+
+The header Settings icon calls the app-only `taskchef_app_open_settings` tool.
+The server resolves this installed plugin's marketplace catalog file and requests its
+native details page through the operating system's Codex URL handler, using the
+same method as Open chat. It does not depend on the MCP view's link handler.
+An unresolved plugin location or failed desktop opener produces a notification.
+The deep link is based on the installed desktop parser, not the published MCP
+settings specification. A successful opener only confirms that navigation was
+requested; the native page still needs a manual check where host automation is
+unavailable.
+
+### Project picker
+
+The searchable picker uses `projects` and `project_roots` from `state_5.sqlite`,
+including saved projects that have no visible chats. Project names and order
+come from the saved registry. Chats use `threads.project_id` first. Older
+assignments use the desktop's project ID migration map and project root hints
+from `.codex-global-state.json`. Git's `.git` pointer and `commondir` identify a
+worktree's original checkout when no assignment is saved. Nested folders match
+the most specific saved project root. Working folders remain in chat details.
+
+Projectless chat IDs, folders under `~/Documents/Codex`, and folders that do not
+match a saved project share the **No project** entry. **All projects** clears the
+filter. The dropdown has folder icons, a check for the selection, search by name
+or path, and keyboard navigation. It does not create projects.
+
+Project settings changes are checked on the next visible poll. The desktop
+settings file is parsed only when its file stamp changes. Its unrelated fields
+are never returned to the view. Invalid project metadata produces a visible
+error; it does not silently replace the saved inventory.
+
+### Reply image covers
+
+TaskChef board cards feature the first supported Markdown image in the latest
+selected assistant reply, above the title. The full saved reply is inspected,
+even when the image occurs after the 2,000-character text excerpt. Code examples
+and raw HTML do not count as images. No image is borrowed from an older turn.
+
+Local covers load when near the visible area. Remote images remain caption
+links in the reply; the sidebar does not load them automatically. Local absolute
+paths load through an app-only MCP
+tool tied to the chat, turn and saved image URL. Local PNG, JPEG, GIF and WebP
+files up to 4 MiB are supported; no remote URL is fetched by the MCP server.
+Missing, oversized, unsupported or failed image covers are hidden.
+Click a cover to open chat Details. Text and navigation remain available.
+The Markdown text renderer still shows image captions rather than inline images.
+
+This follows Trello’s image-above-title cover option:
+[Add a card cover](https://support.atlassian.com/trello/docs/what-is-a-card-cover).
+
+
+### TaskChef notifications
+
+The bell beside Settings opens the notification center. It has All and Unread
+filters, Mark all read, and Clear all. Click a chat message to open Details and
+mark it read. New messages appear in a five-second overlay toast; the board does
+not move. At most three toasts are shown at once. Saved messages do not replay
+as toasts when a view opens.
+
+- A new completed turn with a verified ordinary input creates an unread “ready for input or review” message.
+- An interrupted or failed turn creates an unread interruption message, including scheduled failures.
+- Routine scheduled completions stay quiet.
+- Mark Done creates a confirmation that is already read. It does not increase the unread badge.
+- Opening a chat, copying an ID, and refreshing have no success message. Action failures use the same center.
+- Database read errors remain visible on the board until recovery.
+
+The MCP process stores the newest 100 messages, read status, and per-chat turn
+watermarks in `notifications.json` beside its settings file. Views share this
+file through the existing lock and atomic writer; no daemon is added. Clear all
+removes messages but keeps watermarks, so polling cannot replay cleared events.
+The first successful scan establishes a quiet baseline. Subsequent visible
+five-second refreshes reconcile changes, including cached database snapshots.
+Exec and CLI visibility settings also suppress notifications from hidden sources;
+project and date filters only change the board. Archived chats stay quiet. Saved notifications can still open Details for a chat
+that is now hidden by Settings.
+
+When views are closed or hidden, no background scan runs. A later refresh can
+notice the latest saved turn change. It cannot reconstruct intermediate turns
+that finished while no view was checking. Notifications are local app messages;
+this feature does not send OS notifications. A damaged notification file fails
+visibly and is preserved for repair.
+
+
+## Local UI review without restarting Codex
+
+For UI-only changes, update the HTML in the installation that the running MCP
+server uses. Do not install a new preview version for each style change. Codex
+can keep the old MCP process running while a plugin update removes its old
+folder. Its next resource read then fails with `ENOENT`, and the sidebar shows
+“Couldn't refresh app”.
+
+From the source checkout, run:
+
+```sh
+npm run update:mcp-app-preview -- /path/to/the/running/taskchef-next/version
+```
+
+The helper builds the UI, checks the target is TaskChef, 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** in the Codex sidebar and choose **Refresh**.
+Switching sidebar apps only hides the loaded view; it does not reload its HTML.
+
+Use the current installation’s version folder. If Refresh reports a missing
+older version in the desktop logs, the MCP process still uses that old folder;
+updating a different folder will not repair it. A full plugin/runtime update is
+still needed for server code or dependency changes. This helper is for local
+preview review, not production plugin distribution.
+
+## GitHub PR status
+
+TaskChef reads saved PR attachments and can connect to GitHub with device
+sign-in. See [GitHub setup and board rules](taskchef-next-github.md).
+
+
+### Chat search
+
+**Search chats** matches chat titles, saved reply excerpts, project names,
+known project repositories, and latest-turn PR titles and repository names.
+Matching ignores letter case; every word must match somewhere in those fields.
+Project and time filters still apply.
+
+Search uses the current snapshot. PR titles become searchable after GitHub
+loads them; repository names from saved PR URLs are searchable before status
+loads. Search does not add a separate GitHub lookup or scan local Git remotes.
+The existing visible-card refresh still runs when the displayed cards change.
+
+
+## Dragging chats between queues
+
+Every card can drag. Valid destination columns are highlighted during dragging, with padding between
+the rounded column border and its cards.
+Done and Scheduled moves require a Waiting card (including Interrupted cards).
+Cards from any column can drop into Archived to show the archive instructions. Dropping a chat
+without an active schedule into Done uses the existing local Done mark.
+Attached PRs must all be confirmed merged by the server. The mark also records
+the confirmed URLs; a newly attached PR invalidates that acknowledgement.
+Blocked drops leave the card in place and explain the rule through TaskChef
+notifications. An active scheduled chat with a human turn can return to
+Scheduled. This acknowledgement is stored under `scheduled:<chat-id>` in the
+local mark file and is bound to the selected turn ID. It expires when a new
+turn starts and does not change or pause the automation.
+
+Dropping into the visible Archived column opens instructions and an Open chat
+button. The user archives the chat through Codex's top-right **… → Archive**
+menu. This sidebar does not invoke CLI archiving, and it does not show an
+Archive drop target when the Archived column is hidden.
+
+
+The first board fetch shows Loading… in empty columns. Later empty columns use
+their normal queue messages. Cards slide between positions when the board updates;
+reduced-motion preferences disable the slide. Opening the notification center
+marks notifications read as they become visible in its scrollable panel.
+
+The Waiting column is titled Waiting for review. Hovering the notification bell
+opens the center; moving into its panel keeps it open, and leaving closes it after
+a short delay. The button remains usable with a keyboard or touch.
+
+The palette icon after Refresh opens Appearance settings on hover, keyboard activation, or tap. DAY, NIGHT (default), and SYSTEM control light/dark appearance; the separate Theme list offers ChatGPT and 29 Codex presets. Only presets with a native variant for the current appearance are listed. Theme selections are remembered separately for Light and Dark in `taskchef.app.visualTheme.light` and `taskchef.app.visualTheme.dark`; appearance uses `taskchef.app.theme`. The previous Default selection maps to ChatGPT. Existing light/dark/system choices are preserved. System follows operating-system appearance.
+
+TaskChef's selected appearance takes priority over a host-applied inline `color-scheme`. Verify Light inside a dark host as well as in a standalone browser: the page, cards, and controls must change together.
+
+
+The palette seeds live in `src/mcp-app/react/themes.ts`. They mirror the desktop
+registry's surface, ink, accent, contrast, semantic colors, and font families. TaskChef derives
+its cards, controls, borders, and elevated surfaces from those seeds. Links and
+small muted text are adjusted when needed to meet a 4.5:1 contrast ratio on the
+UI surfaces. Native font families use locally available fonts with system fallbacks. Font assets are not copied from the desktop application. Palette definitions ship with TaskChef; opening the board does not
+read the installed desktop application or fetch theme files from the network.