@sellable/install 0.1.19 → 0.1.20
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 +18 -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.20";
|
|
19
19
|
const CODEX_PLUGIN_COMPAT_VERSIONS = [
|
|
20
20
|
"0.1.8",
|
|
21
21
|
"0.1.9",
|
|
@@ -28,6 +28,7 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
|
|
|
28
28
|
"0.1.16",
|
|
29
29
|
"0.1.17",
|
|
30
30
|
"0.1.18",
|
|
31
|
+
"0.1.19",
|
|
31
32
|
];
|
|
32
33
|
const INSTALL_PACKAGE_SPEC = `@sellable/install@${CODEX_PLUGIN_VERSION}`;
|
|
33
34
|
|
|
@@ -498,6 +499,13 @@ rows, sampled people, sampled fits as n/N (%), estimated usable people, and the
|
|
|
498
499
|
confidence basis. Never show a percent like "73% match" without the numerator,
|
|
499
500
|
denominator, and sample basis.
|
|
500
501
|
|
|
502
|
+
Every approval gate must include artifact access after the readable inline
|
|
503
|
+
content. Show an \`Open artifacts:\` line with clickable markdown links using
|
|
504
|
+
absolute paths when the host supports them, plus the plain path for CLI users.
|
|
505
|
+
Do this for brief approval, lead-source approval/review, message review, and the
|
|
506
|
+
final approval packet. The links are for deeper inspection; never use them as a
|
|
507
|
+
substitute for showing the content in chat.
|
|
508
|
+
|
|
501
509
|
Never mention MCP namespaces, prompt chunking, plugin cache paths, missing
|
|
502
510
|
linked skill versions, runbooks, or local skill files in normal customer-facing
|
|
503
511
|
copy.
|
|
@@ -842,6 +850,15 @@ approval should show who we are targeting, why they should care, the offer/CTA,
|
|
|
842
850
|
proof, lead source hypothesis, message angle, risks/assumptions, and what
|
|
843
851
|
happens after approval.
|
|
844
852
|
|
|
853
|
+
Every approval should also give the user a way to inspect the source artifact.
|
|
854
|
+
After the readable inline content, include an \`Open artifacts:\` line with links
|
|
855
|
+
or plain paths to the files behind the decision. The artifact links are a backup
|
|
856
|
+
for inspection, not a replacement for showing the content in chat.
|
|
857
|
+
|
|
858
|
+
This applies especially to message approvals. Never ask someone to approve a
|
|
859
|
+
message they cannot see. Show the subject, message body/template, filled example,
|
|
860
|
+
omit example, token notes, your take, and suggested adjustment first.
|
|
861
|
+
|
|
845
862
|
For lead-source decisions, confidence comes from concrete counts. Do not say
|
|
846
863
|
"strong sample", "73% match", or "meaningful concentration" without showing the
|
|
847
864
|
sample size and what was counted. Show lanes searched, timeframe, raw results,
|