@sellable/install 0.1.17 → 0.1.18

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.
@@ -15,7 +15,7 @@ import { createInterface } from "node:readline/promises";
15
15
  const DEFAULT_API_URL = "https://app.sellable.dev";
16
16
  const DEFAULT_SERVER_PACKAGE =
17
17
  process.env.SELLABLE_MCP_PACKAGE || "@sellable/mcp";
18
- const CODEX_PLUGIN_VERSION = "0.1.17";
18
+ const CODEX_PLUGIN_VERSION = "0.1.18";
19
19
  const CODEX_PLUGIN_COMPAT_VERSIONS = [
20
20
  "0.1.8",
21
21
  "0.1.9",
@@ -26,6 +26,7 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
26
26
  "0.1.14",
27
27
  "0.1.15",
28
28
  "0.1.16",
29
+ "0.1.17",
29
30
  ];
30
31
  const INSTALL_PACKAGE_SPEC = `@sellable/install@${CODEX_PLUGIN_VERSION}`;
31
32
 
@@ -827,6 +828,13 @@ tell them what they will see next.
827
828
  Every customer-facing update should say what Sellable learned, what decision is
828
829
  being made, what the user will see next, or what is protected until approval.
829
830
 
831
+ Approvals only feel safe when the user can see what they are approving. Before
832
+ any approve/revise question, show the relevant decision in plain language. For a
833
+ brief approval, render the brief itself, not just a direction summary. The brief
834
+ approval should show who we are targeting, why they should care, the offer/CTA,
835
+ proof, lead source hypothesis, message angle, risks/assumptions, and what
836
+ happens after approval.
837
+
830
838
  Good wait update:
831
839
 
832
840
  \`\`\`text
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/install",
3
- "version": "0.1.17",
3
+ "version": "0.1.18",
4
4
  "type": "module",
5
5
  "description": "One-command installer for Sellable MCP in Claude Code and Codex",
6
6
  "bin": {