@sellable/mcp 0.1.7 → 0.1.8

package/README.md

@@ -83,14 +83,14 @@ The token is provided when you generate it. Use `list_workspaces` +
 For customer/package installs, use the public installer:
 
 ```bash
-npx -y @sellable/install@0.1.7 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
+npx -y @sellable/install@0.1.8 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
 ```
 
 If you already have `~/.sellable/config.json`, rerun/verify without rewriting
 auth:
 
 ```bash
-npx -y @sellable/install@0.1.7 --host codex
+npx -y @sellable/install@0.1.8 --host codex
 sellable --verify-only --host codex
 ```
 
@@ -131,9 +131,11 @@ Never tell users to run `/sellable:create-campaign-v2`,
 
 Claude Code should ask intake and approval gates with `AskUserQuestion`.
 Codex should ask them with `request_user_input` when it is exposed in an
-interactive Plan/collaboration-mode session. `codex exec` is non-interactive
-and cannot show the structured questionnaire UI, so it is only useful for smoke
-checks that stop before human intake/approval.
+interactive session. The installer enables Default mode support by writing
+`default_mode_request_user_input = true` under `[features]` in
+`~/.codex/config.toml`. `codex exec` is non-interactive and cannot show the
+structured questionnaire UI, so it is only useful for smoke checks that stop
+before human intake/approval.
 
 ## Usage
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign-v2/SKILL.md

@@ -76,13 +76,16 @@ Validated draft directory:
   compatibility run where all upstream artifacts already exist.
 - Use the host-native structured question gate whenever it is exposed. In
   Claude Code, this is `AskUserQuestion`. In Codex, this is
-  `request_user_input` (usually exposed in Plan/collaboration-mode interactive
-  sessions, not `codex exec`). Treat them as equivalent approval/intake gates and
-  persist the same draft artifacts after the user answers. If an interactive
+  `request_user_input` (enabled in Default mode by
+  `[features].default_mode_request_user_input = true`, not available in
+  `codex exec`). Treat them as equivalent approval/intake gates and persist the
+  same draft artifacts after the user answers. If an interactive
   Codex session does not expose `request_user_input`, do not silently degrade to
   a plain chat question; stop and tell the user: `Codex has not exposed
-request_user_input in this session. Switch to Plan mode / collaboration mode
-for the structured questionnaire, then rerun $sellable:create-campaign.` In
+request_user_input in this session. Can I update ~/.codex/config.toml with
+[features].default_mode_request_user_input = true? After that, fully quit and
+reopen Codex, then rerun $sellable:create-campaign.` If they decline, tell them
+  to switch to Plan/collaboration mode and rerun `$sellable:create-campaign`. In
   non-interactive `codex exec`, structured user input is unavailable by design;
   ask in chat only when the run is explicitly a non-interactive smoke/rehearsal.
 - Fast Intake Mode is mandatory for hosted/rehearsal net-new runs. Ask the

package/skills/create-campaign-v2/references/approval-gate-framing.md

@@ -103,11 +103,13 @@ with the six commit choices. In Claude Code, call `AskUserQuestion`. In Codex,
 call `request_user_input` when that tool is available. Do not show a standalone
 commit-gate question in a later turn without the approval packet above it. If an
 interactive Codex session does not expose `request_user_input`, do not silently
-fall back to chat. Stop and tell the user to switch to Plan mode /
-collaboration mode so Codex exposes the structured questionnaire tool, then
-rerun `$sellable:create-campaign`. A normal chat question is acceptable only for
-non-interactive `codex exec` smoke/rehearsal runs because structured user input
-is unavailable by design there.
+fall back to chat. Stop and ask permission to update `~/.codex/config.toml`
+with `[features].default_mode_request_user_input = true`, then tell the user to
+fully quit and reopen Codex before rerunning `$sellable:create-campaign`. If the
+user declines the settings update, tell them to switch to Plan/collaboration
+mode and rerun `$sellable:create-campaign`. A normal chat question is acceptable
+only for non-interactive `codex exec` smoke/rehearsal runs because structured
+user input is unavailable by design there.
 
 The packet should read like an AI GTM engineer explaining the campaign, not an
 internal validation report. Start with the practical direction in plain