taskchef 9.2.0 → 9.3.0

package/.codex-plugin/plugin.json

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

package/README.md

@@ -6,9 +6,33 @@ Chats appear regardless of how they were started.
 
 ## Install
 
-Install **TaskChef** from the `favoyang-plugins` Codex marketplace. TaskChef uses
-a local Node.js MCP server; Node.js 22.18+, 23.2+, or 24+ is required. Open **TaskChef**
-from the Codex sidebar. No dispatcher workspace or project indexing is needed.
+TaskChef's marketplace lives in this repository. In Codex, open **Settings →
+Plugins → Add → Add a marketplace** and use
+`https://github.com/favoyang/taskchef.git`. Leave the Git ref as `main` and Sparse
+paths empty. Open **Plugins → Personal**, find **TaskChef** under **TaskChef**,
+and install it.
+
+Alternatively, use the Codex CLI:
+
+```sh
+codex plugin marketplace add favoyang/taskchef
+codex plugin add taskchef@taskchef
+```
+
+Restart Codex. Open **…** below Plugins in the left dock, find **TaskChef**, and
+pin it to keep the board in the sidebar. TaskChef uses a local Node.js MCP
+server and npm. Supported Node.js versions are 22.18+ in the 22 series, or
+23.2 and newer. Node.js 24 is recommended for a new installation. Server
+dependencies are included in the published package.
+
+### Move from the shared marketplace
+
+If you installed `taskchef@favoyang-plugins`, add the new marketplace and install
+`taskchef@taskchef` with the commands above. After it installs successfully,
+remove the old plugin with `codex plugin remove taskchef@favoyang-plugins`, then
+restart Codex. Keep only one released TaskChef installation enabled. Local
+settings, GitHub credentials, and Codex chat history are independent of the
+marketplace cache and do not need to be reset. TaskChef Dev stays separate.
 
 Codex databases and logs stay on your computer and remain the source of truth.
 TaskChef keeps its own settings, manual Done marks, notification state, and
@@ -48,3 +72,8 @@ 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)
+
+## Feedback
+
+[Report a bug](https://github.com/favoyang/taskchef/issues/new?template=bug_report.yml)
+or [request a feature](https://github.com/favoyang/taskchef/issues/new?template=feature_request.yml).

package/docs/mcp-app.md

@@ -337,3 +337,31 @@ message does not cause polling to replay it. Other features continue working. Th
 second, and missing chat snapshots wait at most 250 ms for all subscriptions
 combined. Hidden views do not initiate refreshes; an existing subscription can
 still receive live updates while the MCP process remains running.
+
+## Marketplace and release ownership
+
+The public catalog is `.agents/plugins/marketplace.json` in this repository.
+Its marketplace name is `taskchef`; the released install is `taskchef@taskchef`.
+The catalog pins a published npm package containing the built UI and production
+server dependencies. A raw Git checkout is not a packaged release.
+
+After semantic-release publishes, the marketplace job checks the expected npm
+version and archive, then commits only the catalog pin on the latest `main`.
+A failed check leaves the prior pin in place and fails the workflow. The job
+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
+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
+`taskchef@taskchef`. Never rename the source release manifest for Dev.
+
+Retire the old shared catalog entry only after this repository's catalog is
+live, the release workflow has completed, and a clean installation from the
+new marketplace succeeds. Existing users must migrate explicitly; changing
+a marketplace does not automatically move their installed plugin identity.

package/package.json

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

package/src/mcp-app.js

@@ -43,9 +43,13 @@ export async function pluginSettingsUrl({ pluginRoot = fileURLToPath(new URL("..
   const marketplace = basename(dirname(dirname(pluginRoot)));
   try {
     const config = parseToml(await readFile(join(codexHome, "config.toml"), "utf8"));
-    const source = config.marketplaces?.[marketplace]?.source;
-    if (typeof source === "string" && isAbsolute(source)) {
-      const marketplacePath = join(source, ".agents", "plugins", "marketplace.json");
+    const entry = config.marketplaces?.[marketplace];
+    const source = entry?.source;
+    const root = entry?.source_type === "git"
+      ? join(codexHome, ".tmp", "marketplaces", marketplace)
+      : source;
+    if (typeof source === "string" && typeof root === "string" && isAbsolute(root)) {
+      const marketplacePath = join(root, ".agents", "plugins", "marketplace.json");
       const catalog = JSON.parse(await readFile(marketplacePath, "utf8"));
       if (catalog.name !== marketplace || !catalog.plugins?.some((entry) => entry.name === plugin)) return null;
       return `codex://plugins/${encodeURIComponent(plugin)}?${new URLSearchParams({ marketplacePath })}`;