@brainervirus/workit-codex 1.0.0 → 1.0.1

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "workit",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Adaptive engineering workflow rails for Codex",
   "author": {
     "name": "BrainerVirus"

package/dist/workit-hook.js

@@ -10489,7 +10489,10 @@ check and review kinds auto-bind the current tree and need no digests. Record
 verification evidence last: later evidence or commits can reopen fixed findings
 for re-verification, so verify, resolve, then close with nothing in between.
 decision.record {binding with taskId/workspaceId from inspect plus presented and
-approvedContent} only through a native approval question, task.close {outcome,
+approvedContent} only through a native approval question asked receipt-shaped:
+header Workit decision: <purpose>, the same label repeated in the question
+text (some host UIs do not render headers), exactly two options approved and
+rejected; ask once, never re-ask to mint a receipt. task.close {outcome,
 summary, decisionIds}. A completed native subagent run stops its bound worker
 by itself; if a worker strands in cancelling with its run verifiably over,
 repeat worker.cancel {reason} to confirm the stop. Check and review evidence

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brainervirus/workit-codex",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "private": false,
   "description": "Workit Codex CLI and desktop plugin",
   "keywords": [
@@ -34,8 +34,8 @@
     "build": "bun scripts/build.ts"
   },
   "dependencies": {
-    "@brainervirus/workit-core": "^1.0.0",
-    "@brainervirus/workit-mcp": "^1.0.0"
+    "@brainervirus/workit-core": "^1.0.1",
+    "@brainervirus/workit-mcp": "^1.0.1"
   },
   "engines": {
     "node": ">=24"

package/skills/workit-challenge/SKILL.md

@@ -28,8 +28,10 @@ selects requirements; do not wait for a rule that can only exist after assess.
    dependency order and recompute after every answer — a wall of questions is
    not an interview.
 4. Funnel every resolution: the moment a consequential choice settles, bind it
-   with a receipt-shaped question (header `Workit decision: <purpose>`, exactly
-   `approved`/`rejected`, the approved description carrying the exact content).
+   with a receipt-shaped question — header `Workit decision: <purpose>` and the
+   same label repeated in the question text (host UIs may not render headers) —
+   exactly `approved`/`rejected` options, the approved description carrying the
+   exact content.
    If the user already stated the choice in conversation and no receipt can be
    minted, record it in task progress and reassess so the settled requirement
    retires — never re-ask to mint a receipt, and never leave it for close to