@sellable/mcp 0.1.370 → 0.1.371
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
|
@@ -63,6 +63,16 @@ immediately with `blocked: setup_evergreen_campaigns_unavailable`. Do not fall
|
|
|
63
63
|
back to ad hoc create-campaign calls, inventory-only guesses, or direct shell
|
|
64
64
|
creation when the command-backed plan is missing.
|
|
65
65
|
|
|
66
|
+
MCP/product-visible proof only: every success claim must be observable through
|
|
67
|
+
the installed Sellable MCP tools and product-visible readbacks a normal user or
|
|
68
|
+
agent can access. Do not inspect the product database directly to prove success.
|
|
69
|
+
Direct SQL, Prisma, or DB snapshots are diagnostic only; they are not success proof for command completion. Receipts must cite MCP tool calls, command
|
|
70
|
+
responses, prompt/asset loads, and product-visible readbacks such as campaign
|
|
71
|
+
context, campaign message preview, table rows, cell selectors, sequence
|
|
72
|
+
readback, and setup plan/verify results. If MCP surfaces disagree on counts or
|
|
73
|
+
state, record the discrepancy and resolve or explain the canonical gate before
|
|
74
|
+
reporting the command complete.
|
|
75
|
+
|
|
66
76
|
Plan shape:
|
|
67
77
|
|
|
68
78
|
- one Post Engagers lane per sender in the **Post Engagers sender scope**;
|