taskchef 9.0.0 → 9.0.1

package/.codex-plugin/plugin.json

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

package/README.md

@@ -39,8 +39,12 @@ npm run check:mcp-app
 npm run build:mcp-app
 ```
 
-Keep the release plugin named **TaskChef** and the separately packaged
-`taskchef-next` plugin named **TaskChef Dev**. See
+Develop on a topic branch and update **TaskChef Dev** first. Keep **TaskChef**
+on the published release. After validation, independent review, merge, and a
+successful release workflow, update TaskChef from the released package when
+the merge publishes a release. Otherwise keep its existing published version.
+The Dev copy uses the separate `taskchef-next` plugin ID and **TaskChef Dev**
+name; apply that identity only to its local staging package. See
 [development packaging](docs/mcp-app.md#development-plugin-identity).
 
 [Native app guide](docs/mcp-app.md) · [GitHub setup](docs/taskchef-next-github.md)

package/docs/mcp-app.md

@@ -181,8 +181,25 @@ visibly and is preserved for repair.
 ## Development plugin identity
 
 Keep the released **TaskChef** plugin and a separate **TaskChef Dev** plugin.
-The development copy must already use the plugin ID `taskchef-next`.
-Before installing it through a local marketplace, run:
+Use this order for every development change:
+
+1. Work in a topic branch/worktree. Build and validate the current source.
+2. Copy the current runtime, built UI, skill, and production dependencies into
+   a separate local staging package. Update **TaskChef Dev** from that package
+   and test it before merging. Never copy development changes into TaskChef's
+   released installation.
+3. Pass independent review and the pull request checks, then merge when authorized.
+4. If the merge publishes a release, wait for the complete release workflow,
+   including its marketplace update. Update **TaskChef** from the published
+   package and verify its version. If no release is published, leave TaskChef
+   on its existing published version.
+
+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`.
+Before installing the staging package through the local development marketplace,
+run:
 
 ```sh
 node scripts/prepare-mcp-app-preview.js /path/to/staging/plugin
@@ -209,7 +226,7 @@ From the source checkout, run:
 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
+The helper builds the UI, checks the development plugin ID is `taskchef-next`, 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**.

package/package.json

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

package/src/user-prompt.js

@@ -3,6 +3,17 @@ import { normalizeUri } from "micromark-util-sanitize-uri";
 // Convert Codex's supplied prompt context to readable Markdown. Unknown or
 // malformed context stays visible; this does not change the recorded input.
 export function displayUserPrompt(text) {
+  const questionReply = /^\s*<send_user_message_question_reply>([\s\S]*)<\/send_user_message_question_reply>\s*$/.exec(text);
+  if (questionReply) {
+    try {
+      const value = JSON.parse(questionReply[1]);
+      const replies = Array.isArray(value) ? value : [value];
+      if (replies.length && replies.every(reply => reply && typeof reply.question === "string" && typeof reply.answer === "string")) {
+        return replies.map(reply => `${reply.question.split('\n').map(line => `> ${line}`).join('\n')}\n\n${reply.answer}`).join('\n\n');
+      }
+    } catch { /* Preserve unrecognized input rather than losing the user's prompt. */ }
+    return text;
+  }
   const requestHeading = /^##? My request:[ \t]*(?:\r?\n|$)/m.exec(text);
   if (!requestHeading || !/^(?:[ \t]*\r?\n)*(?:# Response annotations:|# Files mentioned by the user:|<in-app-browser-context source="ambient-ui-state">)\r?\n/.test(text)) return text;
   const context = text.slice(0, requestHeading.index);