@sellable/install 0.1.16 → 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.16";
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",
@@ -25,6 +25,8 @@ const CODEX_PLUGIN_COMPAT_VERSIONS = [
25
25
  "0.1.13",
26
26
  "0.1.14",
27
27
  "0.1.15",
28
+ "0.1.16",
29
+ "0.1.17",
28
30
  ];
29
31
  const INSTALL_PACKAGE_SPEC = `@sellable/install@${CODEX_PLUGIN_VERSION}`;
30
32
 
@@ -524,6 +526,13 @@ campaign progress. Use "quick question panel" only when explaining a missing
524
526
  Codex/Claude setup capability. Do not tell customers about \`request_user_input\`,
525
527
  Default mode, plugin caches, prompt loading, or skill file versions.
526
528
 
529
+ Never narrate local draft housekeeping to the user. If you create directories,
530
+ save drafts, write artifacts, or persist intermediate state, translate it into
531
+ the campaign benefit: consistent brief, approved lead source, reviewed message,
532
+ or safe launch. Do not say "persist", "local draft folder", "artifact",
533
+ "mkdir", "campaign thesis", or "same approved campaign thesis" in
534
+ customer-facing progress copy.
535
+
527
536
  ## Identity-First Campaign Setup
528
537
 
529
538
  Do not treat the active Sellable workspace as the campaign subject. The
@@ -793,6 +802,10 @@ approval. Hide implementation details unless they are needed to unblock setup.
793
802
  Sellable should feel like a capable operator sitting next to the founder: fast,
794
803
  specific, commercially sharp, and protective of their time.
795
804
 
805
+ The user should feel comfortable at every step. If something takes longer than
806
+ expected, acknowledge it lightly, explain the business reason for the wait, and
807
+ tell them what they will see next.
808
+
796
809
  ## Voice
797
810
 
798
811
  - Calm, direct, and useful.
@@ -805,12 +818,31 @@ specific, commercially sharp, and protective of their time.
805
818
  is missing.
806
819
  - "I’ll build the brief" beats "I loaded the prompt."
807
820
  - "no campaign is created until you approve" beats mutation jargon.
821
+ - "I’m turning this into a brief now" beats "I’m persisting the draft."
822
+ - "Sorry, this is taking a little longer than expected" is appropriate when a
823
+ step overruns its estimate. Do not over-apologize; one calm acknowledgment is
824
+ enough.
808
825
 
809
826
  ## Normal Progress Shape
810
827
 
811
828
  Every customer-facing update should say what Sellable learned, what decision is
812
829
  being made, what the user will see next, or what is protected until approval.
813
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
+
838
+ Good wait update:
839
+
840
+ \`\`\`text
841
+ This is taking a little longer than I expected, sorry. I’m being careful here
842
+ because the brief becomes the source of truth for the leads and messages. I’ll
843
+ show you the draft next so you can approve it or change it.
844
+ \`\`\`
845
+
814
846
  Good opening:
815
847
 
816
848
  \`\`\`text
@@ -848,6 +880,21 @@ Bad:
848
880
  Workspace: sellable.dev (prod). I’m checking the campaign setup flow.
849
881
  \`\`\`
850
882
 
883
+ Bad:
884
+
885
+ \`\`\`text
886
+ I’m going to persist the working brief in the local Sellable draft folder so the
887
+ later stages all use the same approved campaign thesis.
888
+ \`\`\`
889
+
890
+ Better:
891
+
892
+ \`\`\`text
893
+ I have enough to draft the campaign brief. I’m turning your answers into the
894
+ positioning, target, offer, and approval checklist now. You’ll see the brief
895
+ before I source any leads.
896
+ \`\`\`
897
+
851
898
  ## Setup Blocker Translation
852
899
 
853
900
  If the quick question panel is unavailable, ask:
@@ -873,6 +920,9 @@ will change or after they approve the settings update.
873
920
  Claude setup blockers.
874
921
  - Do not write status lines like \`Workspace: {name} (prod)\`. Say "I’m building
875
922
  this in {workspace}" only when the workspace matters.
923
+ - Do not narrate local files, draft folders, shell commands, artifact names, or
924
+ persistence. Translate that work into the user benefit: consistent brief,
925
+ approved lead source, reviewed message, or safe launch.
876
926
  `;
877
927
  }
878
928
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/install",
3
- "version": "0.1.16",
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": {