@sellable/mcp 0.1.401 → 0.1.402

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/mcp",
3
- "version": "0.1.401",
3
+ "version": "0.1.402",
4
4
  "type": "module",
5
5
  "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
6
6
  "main": "dist/index.js",
@@ -315,6 +315,12 @@ Short form: Receipt polling uses `find <receipt-dir> -maxdepth 1 -name 'evg_*.js
315
315
  Short form: Do not use naked `*.json` globs under zsh; no `no matches found` diagnostics.
316
316
  Short form: Do not embed `<<'WORKER_PROMPT'` heredocs inside a quoted `/bin/bash -lc` command string.
317
317
  Short form: Multi-worker launchers write prompt files and run `codex ... - < "$worker_prompt_file"`.
318
+ After the auto-executable plan returns, take at most one short planning pass to
319
+ choose the visible/durable worker runtime and build the worker launch packet.
320
+ Do not keep reasoning, re-reading prompts, or restating the workflow instead of
321
+ dispatching. If the parent cannot name the callable worker runtime and prepare
322
+ the first worker launch command/tool call immediately after that pass, stop with
323
+ `blocked: worker_dispatch_deadline_exceeded` before directory setup or mutation.
318
324
  After creating receipt directories, dispatch workers immediately; do not perform extended parent reasoning, extra inventory, or prompt rewriting loops.
319
325
  Before any campaign shell creation, the parent must dispatch every selected lane
320
326
  worker from the current plan and record the visible thread id or