@sellable/install 0.1.103 → 0.1.104

package/agents/post-find-leads-message-scout.md

@@ -61,9 +61,9 @@ Return the following to the parent thread:
   choice, and rubric/filter basis when present
 - output timestamp/hash and any retry/error detail
 
-Write `message-validation.md`, `message-prep.md`, or
-`message-candidate-drafts.md` only when the parent explicitly asks for debug
-artifacts. Normal live campaign runs can return the same content directly.
+Do not write local markdown/json artifacts in normal live campaign runs. Return
+the recommendation directly to the parent thread. Emit debug artifacts only when
+the parent explicitly asks for debug/UAT output.
 
 When reporting branch runtime proof, use this shape under
 `watchNarration.workerDetails.messageDraftBuilder`:

package/agents/registry.json

@@ -211,11 +211,7 @@
         "token fill rules",
         "rendered sample"
       ],
-      "optionalProducesArtifacts": [
-        "message-validation.md",
-        "message-prep.md",
-        "message-candidate-drafts.md"
-      ],
+      "optionalProducesArtifacts": [],
       "ownership": "proof inventory, token strategy, angle drafting, skeptical-prospect review, and selected winner only",
       "codex": {
         "description": "Message Draft Builder for campaign-backed template proposals after confirm_lead_list imports a non-empty bounded review batch.",

package/bin/sellable-install.mjs

@@ -40,7 +40,7 @@ function getMcpVersion() {
   } catch {}
   return "latest";
 }
-const CODEX_PLUGIN_VERSION = "0.1.31";
+const CODEX_PLUGIN_VERSION = "0.1.32";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
   "0.1.9",
@@ -960,7 +960,7 @@ updates.
    supplemental approval checklist, not a replacement for the long prompt. Use
    campaign state, campaign brief content, selected source state, and imported
    review-batch rows as the source of truth; do not read stale local markdown,
-   inspect the database directly, or synthesize \`message-validation.md\` from
+   inspect the database directly, or synthesize local validation artifacts from
    general knowledge.
 5. Create the campaign shell early with the v1 brief so the user can open the
    watch link and see useful setup state immediately. Import only the first

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.103",
+  "version": "0.1.104",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/create-campaign.md

@@ -159,8 +159,8 @@ The create-campaign-v2 subskill calls `get_source_scout_registry` before
 dispatch so the current registry, not this copy, is the runtime source of truth.
 If the host runs them sequentially or the named agents are unavailable, do not
 claim they ran in parallel and do not surface install status to the customer. In
-chat, call the downstream copy stage `message generation`;
-`message-validation.md` is only an internal proof artifact.
+chat, call the downstream copy stage `message generation`; message validation is
+only an internal approval proof.
 
 For campaign-attached Signal Discovery sampling, promote/select the exact posts
 with `select_promising_posts` before `fetch_post_engagers` so the user can see
@@ -597,7 +597,7 @@ updates.
    supplemental approval checklist, not a replacement for the long prompt. Use
    campaign state, campaign brief content, selected source state, and imported
    review-batch rows as the source of truth; do not read stale local markdown,
-   inspect the database directly, or synthesize `message-validation.md` from
+   inspect the database directly, or synthesize local validation artifacts from
    general knowledge.
 5. Create the campaign shell early with the v1 brief so the user can open the
    watch link and see useful setup state immediately. Import only the first