taskchef 7.15.4 → 7.15.5

package/.codex-plugin/plugin.json

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

package/docs/spec.md

@@ -143,6 +143,25 @@ the final link, preserving the delegate skill's immediate-return contract.
    TaskChef MUST atomically close it as `interrupted` before appending the new
    working turn; the executor MUST NOT report semantic `failed` for recovery.
 
+Normal executor completion MUST stop after the terminal callback and return
+normally. It MUST NOT archive, hand off, close, navigate away from, or otherwise
+terminate the Codex task merely because work completed. Archive is authorized
+only by an explicit request in the current assignment or follow-up for that
+exact Codex task; `finish`, `complete`, `done`, `ship`, and ordinary cleanup do
+not imply authorization.
+
+For an explicitly authorized archive, the executor MUST finish and verify the
+work, read its exact task identity, submit the current turn's terminal
+`report_state`, verify TaskChef accepted that state, and only then invoke the
+native archive operation as the final state-changing action. It MUST require
+native confirmation before claiming archive succeeded. The same callback-first
+ordering applies to any separately authorized action that can make the executor
+unavailable before reporting, including handoff or terminating or restarting
+the process that owns the TaskChef MCP transport; this rule does not itself
+authorize those actions. A terminal reporting failure MUST prevent the later
+action and leave the executor accessible. Failure of a later action MUST NOT
+change or reopen the already accepted semantic terminal state.
+
 Request and result summaries are the durable source for dashboard related-link
 projection; TaskChef does not scan full Codex transcripts. When known, an
 executor MUST preserve the selected repository as a canonical GitHub repository

package/docs/workflows.md

@@ -163,6 +163,16 @@ sequenceDiagram
 A native approval prompt is not a semantic result. `needs_input` is reserved
 for a user decision or fact required to proceed.
 
+Ordinary completion returns after the terminal callback; it does not archive,
+hand off, close, navigate away from, or otherwise terminate the native Codex
+task. An archive requires an explicit request in the current assignment or
+follow-up for that exact task. `finish`, `complete`, `done`, `ship`, and cleanup
+alone do not authorize it. Any explicitly requested action that could make the
+executor unavailable must follow, never precede, an accepted terminal callback.
+If reporting fails, the later action is forbidden and the executor remains
+accessible. If the later action fails, its error does not reopen or replace the
+accepted semantic state.
+
 ## Follow-up turns
 
 Turn refs are freshness tokens for semantic callbacks. The workspace rejects a

package/package.json

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

package/skills/taskchef-executor/SKILL.md

@@ -80,6 +80,33 @@ and unnecessary personal data. Identical lifecycle retries are safe; never
 replace a same-`turnRef` report with different content or let an older turn
 overwrite newer state.
 
+### Keep terminal reporting ahead of executor-ending actions
+
+Normal completion ends with the semantic terminal `report_state` callback and
+then returns normally. Never archive, hand off, close, navigate away from, or
+otherwise terminate the Codex task merely because the work or turn completed.
+An archive is authorized only when the current assignment or follow-up
+explicitly requests archiving this exact Codex task. Words such as `finish`,
+`complete`, `done`, `ship`, and ordinary cleanup do not authorize archive.
+
+When archive is explicitly authorized, finish and verify the requested work,
+read the exact task identity required by this protocol, submit the terminal
+`report_state` callback for the current `turnRef`, and verify that TaskChef
+accepted the terminal state. Only then call the native Codex archive operation.
+Archive must be the final state-changing action, and native confirmation is
+required before claiming it succeeded.
+
+Apply the same terminal-callback-first rule when the user explicitly requests
+another action that can make this executor unavailable before it reports, such
+as handing off the task or terminating or restarting the process that owns the
+TaskChef MCP transport. This ordering rule does not authorize any such action.
+If terminal reporting fails, do not archive or perform the requested
+executor-ending action; leave the executor accessible and report the lifecycle
+failure visibly. If terminal reporting succeeds but the later action fails,
+preserve the accepted `completed`, `failed`, or `needs_input` state, report only
+the later action's failure, and do not reopen the lifecycle or report `working`
+again.
+
 ### Preserve repository and delivery links
 
 Treat lifecycle summaries as the durable TaskChef timeline; the dashboard does