@sellable/mcp 0.1.402 → 0.1.403
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
|
@@ -14,6 +14,33 @@ producing duplicates. This skill never launches campaigns; customer-visible
|
|
|
14
14
|
completion stops at paused send review.
|
|
15
15
|
</role>
|
|
16
16
|
|
|
17
|
+
## Operational Fast Path
|
|
18
|
+
|
|
19
|
+
In automation or `--yolo` customer-visible setup, use this path before the
|
|
20
|
+
long-form contract below:
|
|
21
|
+
|
|
22
|
+
1. Resolve the active workspace and explicit sender scopes, then call
|
|
23
|
+
`setup_evergreen_campaigns({ mode:"plan", yolo:true, postEngagerSenderIds,
|
|
24
|
+
sharedSenderIds })`.
|
|
25
|
+
2. If the plan is not current, lacks lane packets, or has
|
|
26
|
+
`autoExecutable:false`, return the exact blocker before mutation.
|
|
27
|
+
3. Choose the worker runtime immediately. When running under Codex CLI or on VPS,
|
|
28
|
+
the local Codex CLI fallback is the default accepted runtime. Use visible
|
|
29
|
+
Codex app threads only when the callable thread tools are actually available.
|
|
30
|
+
If shell execution is unavailable and no visible/durable thread surface is
|
|
31
|
+
callable, return `blocked: missing_visible_or_durable_lane_worker_runtime`
|
|
32
|
+
before mutation.
|
|
33
|
+
4. Write one compact prompt file per selected lane packet, create the receipt
|
|
34
|
+
directory, and launch all lane workers in parallel with the literal Codex CLI
|
|
35
|
+
worker command shape below. The parent does not create campaign shells.
|
|
36
|
+
5. Collect fresh durable receipts, verify with the original planRevision and
|
|
37
|
+
selectedActionIds, then run the idempotency plan and show sample messages.
|
|
38
|
+
|
|
39
|
+
Do not keep reasoning, re-reading prompts, or restating this workflow instead of
|
|
40
|
+
dispatching workers. If the first worker cannot be launched after at most one
|
|
41
|
+
short planning pass, return `blocked: worker_dispatch_deadline_exceeded` before
|
|
42
|
+
directory setup or product mutation.
|
|
43
|
+
|
|
17
44
|
<inputs>
|
|
18
45
|
The invoking prompt names the senders ("create evergreen campaigns for csreyes92 and thomas"). Resolve each via `list_senders`.
|
|
19
46
|
|