@sellable/install 0.1.72 → 0.1.73

package/bin/sellable-install.mjs

@@ -40,7 +40,7 @@ function getMcpVersion() {
   } catch {}
   return "latest";
 }
-const CODEX_PLUGIN_VERSION = "0.1.28";
+const CODEX_PLUGIN_VERSION = "0.1.29";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
   "0.1.9",
@@ -62,6 +62,7 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.25",
   "0.1.26",
   "0.1.27",
+  "0.1.28",
 ];
 const INSTALL_PACKAGE_SPEC =
   process.env.SELLABLE_INSTALL_PACKAGE_SPEC || "@sellable/install@latest";
@@ -632,11 +633,44 @@ gates. Never use it to collect open text input like LinkedIn URLs, company
 domains, notes, pasted context, campaign ideas, or feedback. For open text, ask
 in normal chat and wait for the user to paste the value.
 
+For campaign setup, every structured question is single-choice in both Claude
+Code and Codex. Use mutually exclusive options, set or assume
+\`multiSelect: false\`, and do not use checkbox or multi-select wording. If the
+user needs a blended/custom answer, route them through \`Other / custom\` or a
+free-text follow-up in normal chat.
+
 Customer-facing language must call this "a couple setup choices" during normal
 campaign progress. Use "quick question panel" only when explaining a missing
 Codex/Claude setup capability. Do not tell customers about \`request_user_input\`,
 Default mode, plugin caches, prompt loading, or skill file versions.
 
+## Host Runtime Functions
+
+Treat host capabilities as concrete functions, not prose conventions:
+
+- \`ask_user\`: Claude Code uses \`AskUserQuestion\`; Codex uses
+  \`request_user_input\`. Use this for multiple-choice intake, campaign-focus
+  choices, source decisions, and approvals. Campaign setup questions are
+  single-choice only; do not use multi-select or checkbox variants. Never
+  render numbered plain-chat choices in an interactive session when the
+  structured question function is exposed.
+- \`load_subprompt\`: call
+  \`mcp__sellable__get_subskill_prompt({ subskillName, offset?, limit? })\` and
+  continue chunks until \`hasMore\` is false.
+- \`load_subprompt_asset\`: call
+  \`mcp__sellable__get_subskill_asset({ subskillName, assetPath, offset?, limit? })\`
+  and continue chunks until \`hasMore\` is false.
+- \`load_source_scout_registry\`: call
+  \`mcp__sellable__get_source_scout_registry({})\` before any scout dispatch.
+- \`launch_source_scout\`: Claude Code uses \`Task\` with \`subagent_type\` equal to
+  the registry \`name\`; Codex uses named custom agents such as
+  \`source-scout-linkedin-engagement\`, \`source-scout-sales-nav\`, and
+  \`source-scout-prospeo-contact\` when subagents are available.
+
+If a required interactive host function is missing, stop and explain the
+Sellable install/reload problem. Do not silently simulate structured choices,
+subprompt loading, or source-scout dispatch with local scripts.
+
 Never narrate local draft housekeeping to the user. If you create directories,
 save drafts, write artifacts, or persist intermediate state, translate it into
 the campaign benefit: consistent brief, approved lead source, reviewed message,

package/package.json

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

package/skill-templates/create-campaign.md

@@ -161,11 +161,44 @@ gates. Never use it to collect open text input like LinkedIn URLs, company
 domains, notes, pasted context, campaign ideas, or feedback. For open text, ask
 in normal chat and wait for the user to paste the value.
 
+For campaign setup, every structured question is single-choice in both Claude
+Code and Codex. Use mutually exclusive options, set or assume
+`multiSelect: false`, and do not use checkbox or multi-select wording. If the
+user needs a blended/custom answer, route them through `Other / custom` or a
+free-text follow-up in normal chat.
+
 Customer-facing language must call this "a couple setup choices" during normal
 campaign progress. Use "quick question panel" only when explaining a missing
 Codex/Claude setup capability. Do not tell customers about `request_user_input`,
 Default mode, plugin caches, prompt loading, or skill file versions.
 
+## Host Runtime Functions
+
+Treat host capabilities as concrete functions, not prose conventions:
+
+- `ask_user`: Claude Code uses `AskUserQuestion`; Codex uses
+  `request_user_input`. Use this for multiple-choice intake, campaign-focus
+  choices, source decisions, and approvals. Campaign setup questions are
+  single-choice only; do not use multi-select or checkbox variants. Never
+  render numbered plain-chat choices in an interactive session when the
+  structured question function is exposed.
+- `load_subprompt`: call
+  `mcp__sellable__get_subskill_prompt({ subskillName, offset?, limit? })` and
+  continue chunks until `hasMore` is false.
+- `load_subprompt_asset`: call
+  `mcp__sellable__get_subskill_asset({ subskillName, assetPath, offset?, limit? })`
+  and continue chunks until `hasMore` is false.
+- `load_source_scout_registry`: call
+  `mcp__sellable__get_source_scout_registry({})` before any scout dispatch.
+- `launch_source_scout`: Claude Code uses `Task` with `subagent_type` equal to
+  the registry `name`; Codex uses named custom agents such as
+  `source-scout-linkedin-engagement`, `source-scout-sales-nav`, and
+  `source-scout-prospeo-contact` when subagents are available.
+
+If a required interactive host function is missing, stop and explain the
+Sellable install/reload problem. Do not silently simulate structured choices,
+subprompt loading, or source-scout dispatch with local scripts.
+
 Never narrate local draft housekeeping to the user. If you create directories,
 save drafts, write artifacts, or persist intermediate state, translate it into
 the campaign benefit: consistent brief, approved lead source, reviewed message,