@sellable/mcp 0.1.57 → 0.1.58
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
|
@@ -141,6 +141,19 @@ summary.
|
|
|
141
141
|
4. **message validation** — the `Selected Winner` from `message-validation.md`,
|
|
142
142
|
rendered as it will appear in the outbound, plus the `Findings` + `Recommendation`
|
|
143
143
|
|
|
144
|
+
The inline approval packet must include exactly one concrete sample message
|
|
145
|
+
rendered as the recipient would see it. Do not make the user mentally expand
|
|
146
|
+
tokens at the final approval moment. If the selected winner contains supported
|
|
147
|
+
prospect-row `{{tokens}}`, show the template in `## Approved Message Template`
|
|
148
|
+
and also include a short `## Sample Message` section with one realistic filled
|
|
149
|
+
example from the lead sample. Keep the full token rules in the artifact, not in
|
|
150
|
+
the top chat summary.
|
|
151
|
+
|
|
152
|
+
Do not include sequence, cadence, sending-window, mailbox, or campaign settings
|
|
153
|
+
review in the pre-mint approval packet. Those are configured and reviewed after
|
|
154
|
+
the campaign is created in the autonomous tail. The pre-mint packet approves
|
|
155
|
+
only the brief, lead source, lead filter/rubric, and first message direction.
|
|
156
|
+
|
|
144
157
|
The packet must include a dedicated `## Message Review` section immediately
|
|
145
158
|
before `## Approved Message Template`. This is the customer-facing messaging
|
|
146
159
|
gate. It should not be a raw validation dump; it should answer:
|