@sellable/install 0.1.49 → 0.1.50

package/package.json

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

package/skill-templates/create-campaign.md

@@ -133,11 +133,17 @@ approval:
   installer enables this in Default mode with
   `[features].default_mode_request_user_input = true`.
 
-Use the structured question gate only for crisp identity confirmations and
-approval gates. Never use it to collect open text input like LinkedIn URLs,
-company domains, notes, pasted context, campaign ideas, buyer strategy,
-offer/CTA, proof, lead source, or feedback. For open text, ask in normal chat
-and wait for the user to type an answer and press Enter.
+Use the structured question gate for crisp identity confirmations, compact setup
+intake, and approval gates. Never use it to collect raw open text like LinkedIn
+URLs, company domains, pasted notes, long campaign ideas, or detailed feedback.
+For buyer strategy, offer/CTA, proof, and lead source, use the structured gate
+when it is exposed, but treat the visible choices as shortcuts, not a rigid
+multiple-choice survey. Every setup question must allow a custom typed answer.
+In Codex, `request_user_input` adds a freeform Other path; in Claude, include an
+`Other / custom` option. Keep setup intake to two panels because Codex supports
+at most three questions per panel: target/offer/proof first, lead source second.
+Do not use checkbox/radio multi-select language like "pick one",
+"multi-select", or "choose all that apply" for these setup questions.
 
 Use "quick question panel" only when explaining a missing Codex/Claude setup
 capability for approvals. Do not tell customers about `request_user_input`,
@@ -281,9 +287,10 @@ proof, and lead source.
 ```
 
 Do not silently ask approval questions as plain chat when `request_user_input` is
-unavailable in an interactive session. Normal setup strategy questions are
-free-text chat and do not need `request_user_input`. Stop only when an approval
-gate needs the quick question panel:
+unavailable in an interactive session. Setup strategy questions should use the
+quick question panel when available, but may fall back to normal chat if the host
+does not expose structured setup input. Stop only when an approval gate needs the
+quick question panel:
 
 ```text
 I need Codex’s quick question panel for campaign approvals.