@sellable/install 0.1.24 → 0.1.25

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.24";
18
+ const CODEX_PLUGIN_VERSION = "0.1.25";
19
19
  const CODEX_PLUGIN_COMPAT_VERSIONS = [
20
20
  "0.1.8",
21
21
  "0.1.9",
@@ -33,6 +33,7 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
33
33
  "0.1.21",
34
34
  "0.1.22",
35
35
  "0.1.23",
36
+ "0.1.24",
36
37
  ];
37
38
  const INSTALL_PACKAGE_SPEC = `@sellable/install@${CODEX_PLUGIN_VERSION}`;
38
39
 
@@ -869,8 +870,9 @@ the tokens should and should not be filled.
869
870
 
870
871
  Every token needs a fallback. If the row does not have clean data for a token,
871
872
  the approval view should say whether to use a safe segment-level phrase, omit
872
- the sentence, or revise the message. Missing data should never produce robotic
873
- or creepy copy.
873
+ the sentence, or revise the message. It should include the exact fallback
874
+ example, like \`omit the noticed... line\` or \`use "operators"\`. Missing data
875
+ should never produce robotic or creepy copy.
874
876
 
875
877
  Approved token guidance is part of the campaign, not just the review. When a
876
878
  campaign is minted, the approved brief should carry forward the token fill
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/install",
3
- "version": "0.1.24",
3
+ "version": "0.1.25",
4
4
  "type": "module",
5
5
  "description": "One-command installer for Sellable MCP in Claude Code and Codex",
6
6
  "bin": {