@sellable/install 0.1.17 → 0.1.19
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.
- package/bin/sellable-install.mjs +22 -1
- package/package.json +1 -1
package/bin/sellable-install.mjs
CHANGED
|
@@ -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.
|
|
18
|
+
const CODEX_PLUGIN_VERSION = "0.1.19";
|
|
19
19
|
const CODEX_PLUGIN_COMPAT_VERSIONS = [
|
|
20
20
|
"0.1.8",
|
|
21
21
|
"0.1.9",
|
|
@@ -26,6 +26,8 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
|
|
|
26
26
|
"0.1.14",
|
|
27
27
|
"0.1.15",
|
|
28
28
|
"0.1.16",
|
|
29
|
+
"0.1.17",
|
|
30
|
+
"0.1.18",
|
|
29
31
|
];
|
|
30
32
|
const INSTALL_PACKAGE_SPEC = `@sellable/install@${CODEX_PLUGIN_VERSION}`;
|
|
31
33
|
|
|
@@ -490,6 +492,12 @@ clear business decisions, tradeoffs, and approval gates. Use product language:
|
|
|
490
492
|
- "lead source", not provider internals unless comparing source options
|
|
491
493
|
- "nothing is created until you approve", not mutation jargon
|
|
492
494
|
|
|
495
|
+
When explaining lead-source decisions, show the concrete counts behind the
|
|
496
|
+
logic: lanes searched, timeframe, raw result counts, finalist posts or preview
|
|
497
|
+
rows, sampled people, sampled fits as n/N (%), estimated usable people, and the
|
|
498
|
+
confidence basis. Never show a percent like "73% match" without the numerator,
|
|
499
|
+
denominator, and sample basis.
|
|
500
|
+
|
|
493
501
|
Never mention MCP namespaces, prompt chunking, plugin cache paths, missing
|
|
494
502
|
linked skill versions, runbooks, or local skill files in normal customer-facing
|
|
495
503
|
copy.
|
|
@@ -827,6 +835,19 @@ tell them what they will see next.
|
|
|
827
835
|
Every customer-facing update should say what Sellable learned, what decision is
|
|
828
836
|
being made, what the user will see next, or what is protected until approval.
|
|
829
837
|
|
|
838
|
+
Approvals only feel safe when the user can see what they are approving. Before
|
|
839
|
+
any approve/revise question, show the relevant decision in plain language. For a
|
|
840
|
+
brief approval, render the brief itself, not just a direction summary. The brief
|
|
841
|
+
approval should show who we are targeting, why they should care, the offer/CTA,
|
|
842
|
+
proof, lead source hypothesis, message angle, risks/assumptions, and what
|
|
843
|
+
happens after approval.
|
|
844
|
+
|
|
845
|
+
For lead-source decisions, confidence comes from concrete counts. Do not say
|
|
846
|
+
"strong sample", "73% match", or "meaningful concentration" without showing the
|
|
847
|
+
sample size and what was counted. Show lanes searched, timeframe, raw results,
|
|
848
|
+
sampled people, sampled fits as n/N (%), estimated usable people, and whether
|
|
849
|
+
the estimate is sample-backed or directional.
|
|
850
|
+
|
|
830
851
|
Good wait update:
|
|
831
852
|
|
|
832
853
|
\`\`\`text
|