@sellable/install 0.1.149 → 0.1.151

package/agents/post-find-leads-message-scout.md

@@ -37,17 +37,22 @@ the branch input.
 
 ## Required First Steps
 
-1. Load the compact normal-path message prompt:
-
-   `get_subskill_prompt({ subskillName: "generate-messages-compact" })`
-
-2. Use that prompt as the drafting contract. Load
-   `generate-messages-compact/references/examples-critique-revision.md` only for
-   critique, revision, or close-call examples. Do not use create-campaign
-   safety/checklist instructions as a substitute for the message prompt.
-3. Draft only from the campaign brief, selected source context, and initial
+1. Load the full normal-path message prompt:
+
+   `get_subskill_prompt({ subskillName: "generate-messages" })`
+
+2. Use that prompt as the drafting contract. Do not use any alternate prompt,
+   examples-only shortcut, or create-campaign safety/checklist instructions as a
+   substitute for the full message prompt.
+3. Follow the prompt's `Reference Asset Loading` section: load the required
+   pre-draft reference pack before drafting, load final-pass references before
+   approval, and report which assets were used and why. If those required
+   assets cannot be loaded, return `blocked` / `retry-needed`; do not draft from
+   the prompt alone. `ai-tells.md` is part of the required pack and is never
+   optional.
+4. Draft only from the campaign brief, selected source context, and initial
    campaign-table execution slice rows supplied by the parent.
-4. Keep the work provisional until the user chooses `Use Template` in Messages.
+5. Keep the work provisional until the user chooses `Use Template` in Messages.
 
 ## Owned Output
 
@@ -55,10 +60,12 @@ Return the following to the parent thread:
 
 - proposed first-message template using supported `{{...}}` tokens
 - token fill rules and fallbacks
+- `Reference Asset Loading` note naming the required and conditional assets used
+  and why each was used
 - one rendered good-fill sample for a plausible passing campaign-table row
 - one omit/fallback sample when the row signal is not safe
-- pass/fail notes against the generate-messages-compact quality gates
-- compact runtime status: `ready`, `blocked`, `retry-needed`, or `stale`
+- pass/fail notes against the generate-messages quality gates
+- message-draft runtime status: `ready`, `blocked`, `retry-needed`, or `stale`
 - basis token containing campaign revision/updatedAt, brief hash,
   `selectedLeadListId`, `workflowTableId`, execution-slice row ids/hash, filter
   choice, and rubric/filter basis when present
@@ -78,7 +85,7 @@ When reporting branch runtime proof, use this shape under
 - `runId` or `fallbackId`
 - `startedAt` and `updatedAt`
 - `basisToken` and `basis`
-- optional `compactOutputRef`, `compactOutput`, and `error`
+- optional `messageDraftOutputRef`, `messageDraftOutput`, and `error`
 
 Do not tell the UI to show Message Draft Builder as running unless this proof
 exists and points at the current non-empty campaign-table execution slice.
@@ -120,11 +127,33 @@ blocker.
 - Engagement-source personalization is a special case, not the default opener.
   Do not write `saw you {{engagement_context}} on {{post_context}}`, `saw you
 reacted to`, `saw you engaging with`, or equivalent source-citation copy as a
-  default hook. Only refer to engagement when the line is self-aware and
-  low-certainty, for example: `you might not remember the thread, but I found
-you through a [topic] discussion and your [observable role/company context]
-looked close to [problem]`. Otherwise omit the engagement signal and use
-  role/company/problem context.
+  default hook. For LinkedIn-post-sourced campaigns, you may reference the
+  source when it explains why the note exists, but keep it topic-level, not
+  activity-log-level. Good: `saw you in a few conversations around [topic], so
+hope this is relevant`, `saw you in a few conversations about [topic], so
+may be off, but this seemed relevant`, `saw you might be interested in [topic],
+so hope this is relevant`, `hope this is relevant if [topic] is on your plate`,
+or `found you in a thread about [topic], so may be off, but this seemed relevant`.
+Only use `saw you raise your hand for [topic], so figured this was (hopefully)
+worth sending` when the source was an explicit lead-magnet comment, reply, or
+opt-in.
+The cheekier `saw you raise your hand for [topic] (creepy to reach out based
+on that, i know) - but this felt too on the nose to ignore` version is also
+allowed only for explicit lead-magnet comments, replies, or opt-ins and when the
+sender's voice can carry it. Bad: `you commented on...`, `you reacted
+to...`, `saw you engaging with...`, `your LinkedIn activity...`, `you might
+not remember the thread...`, or `found you through [source] and your role
+looked close...`. Otherwise omit the engagement signal and use role/company/problem context.
+- Do not use a PS to defend the source. Lines like `p.s. if the source thread
+  was just casual reading, ignore me` or `only reaching out where the role and
+  topic looked close` are blocked. If the source is too weak, omit it.
+- Do not assert fit from title/company. `Your [role] role at [company] looked
+  close to this problem` is blocked. Keep the apologetic uncertainty instead:
+  `may be off, but if [workflow] is anywhere near your lane...`.
+- Low-pressure relevance opt-outs are allowed when they do not defend the
+  source: `p.s. if this is nowhere near your outbound workflow, ignore me`.
+- Do not use `Caught` as opener language. It reads unnatural in LinkedIn
+  outreach.
 - Do not describe the sender in third person inside the outbound message.
   Lines like `p.s. Saju's angle is...`, `Christian's angle is...`, or
   `[sender]'s approach is...` are internal notes leaking into copy. If the point
@@ -137,7 +166,7 @@ enablement`, or omit it.
 
 Return a concise status with:
 
-- prompt basis loaded: `generate-messages-compact`
+- prompt basis loaded: `generate-messages`
 - live campaign basis used
 - proposed template
 - token fill rules/fallbacks

package/agents/source-scout-linkedin-engagement.md

@@ -43,7 +43,7 @@ sales Claude`; do not treat broad anchor-only lanes like `Claude Code`, `MCP`,
 5. Promote the first narrow sample set when campaign-attached. If a
    `campaignOfferId` was supplied, call `select_promising_posts({
 campaignOfferId, selectionMode: "replace", selections, headlineICPCriteria,
-currentStep: "signal-discovery" })` before sampling so the watched Signal
+scrapePlanMode: "all-selected", currentStep: "signal-discovery" })` before sampling so the watched Signal
    Discovery table shows the promoted posts and the exact posts being tested.
    Do not move the campaign to `confirm-lead-list`; `import_leads` owns that
    visible transition after source approval.

package/bin/sellable-install.mjs

@@ -1110,8 +1110,8 @@ updates.
 3. Follow that prompt and workflow config exactly.
 4. For message generation, use the \`post-find-leads-message-scout\` agent when
    available. The worker and parent-thread fallback must load
-   \`mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages-compact" })\`.
-   Load lazy examples/critique/revision references only when needed. Message review requires Message Draft Builder output:
+   \`mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages" })\`.
+   Do not use any alternate or examples-only message prompt. Message review requires Message Draft Builder output:
    do not draft from a checklist, local markdown artifact, or parent-thread
 	   intuition. Use campaign state, campaign brief content, selected source state,
 	   and initial campaign-table execution slice rows as the source of truth; do not read stale
@@ -1244,8 +1244,8 @@ Desktop, then start a new thread.
 2. When the canonical prompt asks for \`references/*.md\`, load those files
    with \`mcp__sellable__get_subskill_asset({ subskillName: "interview", assetPath: "references/<file>.md" })\`.
 3. Follow the canonical prompt exactly. Save local memory only where that prompt
-   directs, under \`.sellable/configs/core/**\` and
-   \`.sellable/interviews/**\`.
+   directs, under \`~/.sellable/configs/core/**\` and
+   \`~/.sellable/interviews/**\`.
 
 ## MCP Prompt Fallback
 
@@ -1291,7 +1291,7 @@ Desktop, then start a new thread.
    If the response has \`hasMore=true\`, continue with \`nextOffset\` until
    \`hasMore=false\`.
 2. Follow the canonical prompt exactly. Read the relevant
-   \`.sellable/configs/**\` memory files it names.
+   \`~/.sellable/configs/**\` memory files it names.
 3. Apply the loaded memory silently to the user's requested writing or answer.
    If the user only asked to load voice, summarize the active rules briefly and
    ask what they want drafted, answered, or reviewed.
@@ -2044,7 +2044,7 @@ function patchClaudeAlwaysLoad(opts) {
 }
 
 function installCodex(opts) {
-  if (!commandExists("codex")) {
+  if (!opts.dryRun && !commandExists("codex")) {
     const message =
       "Codex CLI not found. Install/login to Codex, then rerun: sellable --host codex";
     if (opts.host === "all") {
@@ -2053,6 +2053,9 @@ function installCodex(opts) {
     }
     throw new Error(message);
   }
+  if (!opts.dryRun) {
+    mkdirSync(codexHome(), { recursive: true, mode: 0o700 });
+  }
   if (opts.server === "hosted") {
     run("codex", codexMcpAddArgs(opts), opts);
     const info = installCodexDesktopPlugin(opts);
@@ -2619,6 +2622,13 @@ async function main() {
         process.exit(2);
       }
       const token = rawArgs[2];
+      const authSetFlags = rawArgs.slice(3);
+      const dryRun = authSetFlags.includes("--dry-run");
+      const unknownAuthSetFlag = authSetFlags.find((arg) => arg !== "--dry-run");
+      if (unknownAuthSetFlag) {
+        console.error(`Unknown auth set option: ${unknownAuthSetFlag}`);
+        process.exit(2);
+      }
       if (!token) {
         console.error(
           "Usage: sellable auth set <token>\n" +
@@ -2643,9 +2653,13 @@ async function main() {
       writeJson(
         authPath(),
         { token, activeWorkspaceId: null, apiUrl },
-        { dryRun: false }
+        { dryRun }
       );
-      console.log(`✓ Token saved to ${authPath()}`);
+      if (dryRun) {
+        console.log(`Dry run: token would be saved to ${authPath()}`);
+      } else {
+        console.log(`✓ Token saved to ${authPath()}`);
+      }
       console.log(`  apiUrl: ${apiUrl}`);
       console.log(`  Continue in your agent:`);
       console.log(`    Claude Code: /sellable:create-campaign`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.149",
+  "version": "0.1.151",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/create-campaign.md

@@ -270,8 +270,13 @@ only an internal approval proof.
 
 For campaign-attached Signal Discovery sampling, promote/select the exact posts
 with `select_promising_posts` before `fetch_post_engagers` so the user can see
-which posts are being sampled in the watched app. The watch guide should say
-that we are checking people from these posts to confirm the right people are
+which posts are being sampled in the watched app. Use
+`selectionMode: "replace"` for a fresh absolute promoted set and
+`selectionMode: "add"` only when intentionally expanding existing promoted
+posts. Use `scrapePlanMode: "all-selected"` when the approval/import should use
+every promoted post; use `scrapePlanMode: "capacity-target"` only when source
+math should import the smallest set that covers a target. The watch guide should
+say that we are checking people from these posts to confirm the right people are
 actually engaging and the source is viable.
 
     After confirmed source rows exist in the campaign table, use the same registry pattern for
@@ -755,8 +760,8 @@ updates.
 3. Follow that prompt and workflow config exactly.
 4. For message generation, use the `post-find-leads-message-scout` agent when
    available. The worker and parent-thread fallback must load
-   `mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages-compact" })`.
-   Load lazy examples/critique/revision references only when needed. Message review requires Message Draft Builder output:
+   `mcp__sellable__get_subskill_prompt({ subskillName: "generate-messages" })`.
+   Do not use any alternate or examples-only message prompt. Message review requires Message Draft Builder output:
    do not draft from a checklist, local markdown artifact, or parent-thread
    intuition. Use campaign state, campaign brief content, selected source state, and
    initial campaign-table execution slice rows as the source of truth; do not read stale local