@sellable/mcp 0.1.238 → 0.1.239

package/dist/tools/content-posts.d.ts

@@ -58,6 +58,7 @@ export declare const contentPostToolDefinitions: ({
             keywords?: undefined;
             sourcePosts?: undefined;
             selectedPatterns?: undefined;
+            previewBudget?: undefined;
             notes?: undefined;
             createdAt?: undefined;
             draftId?: undefined;
@@ -130,6 +131,11 @@ export declare const contentPostToolDefinitions: ({
                     type: string;
                 };
             };
+            previewBudget: {
+                type: string;
+                description: string;
+                additionalProperties: boolean;
+            };
             notes: {
                 type: string;
             };
@@ -192,6 +198,7 @@ export declare const contentPostToolDefinitions: ({
             keywords?: undefined;
             sourcePosts?: undefined;
             selectedPatterns?: undefined;
+            previewBudget?: undefined;
             notes?: undefined;
         };
         required: string[];
@@ -245,6 +252,7 @@ export declare function saveHookResearchTool(input: {
     keywords?: string[];
     sourcePosts?: Array<Record<string, unknown>>;
     selectedPatterns?: string[];
+    previewBudget?: Record<string, unknown>;
     notes?: string;
     createdAt?: string;
 }): {

package/dist/tools/content-posts.js

@@ -66,6 +66,11 @@ export const contentPostToolDefinitions = [
                     type: "array",
                     items: { type: "string" },
                 },
+                previewBudget: {
+                    type: "object",
+                    description: "Optional structured LinkedIn preview-budget summary for studied hooks and selected patterns.",
+                    additionalProperties: true,
+                },
                 notes: { type: "string" },
                 createdAt: { type: "string" },
             },
@@ -202,11 +207,14 @@ export function capturePostIdeaTool(input) {
     const markdown = buildMarkdown(metadata, [
         ["Distilled Brief", input.distilledBrief || ""],
         ["Raw Source", rawBlock(input.rawSource)],
-        ["Source Metadata", jsonBlock(stripUndefined({
+        [
+            "Source Metadata",
+            jsonBlock(stripUndefined({
                 sourceType: input.sourceType,
                 sourceUrl: input.sourceUrl,
                 capturedAt: now,
-            }))],
+            })),
+        ],
     ]);
     writeArtifact(relativePath, markdown);
     return {
@@ -246,6 +254,7 @@ export function saveHookResearchTool(input) {
     const markdown = buildMarkdown(metadata, [
         ["Keywords", listBlock(input.keywords ?? [])],
         ["Selected Patterns", listBlock(input.selectedPatterns ?? [])],
+        ["Preview Budget", jsonBlock(input.previewBudget ?? {})],
         ["Source Posts", jsonBlock(input.sourcePosts ?? [])],
         ["Notes", input.notes || ""],
     ]);
@@ -332,18 +341,24 @@ export function markPostPublishedTool(input) {
     };
     const markdown = buildMarkdown(metadata, [
         ["Final Text", input.finalText || ""],
-        ["Publish Metadata", jsonBlock(stripUndefined({
+        [
+            "Publish Metadata",
+            jsonBlock(stripUndefined({
                 draftId: safeDraftId,
                 publishUrl: input.publishUrl,
                 activityId: activityId || undefined,
                 publishedAt,
-            }))],
-        ["Future Metrics", jsonBlock({
+            })),
+        ],
+        [
+            "Future Metrics",
+            jsonBlock({
                 impressions: null,
                 reactions: null,
                 comments: null,
                 snapshots: [],
-            })],
+            }),
+        ],
     ]);
     writeArtifact(relativePath, markdown);
     return {
@@ -483,7 +498,8 @@ function validateRelativePath(relativePath) {
 }
 function isPathInside(candidate, root) {
     const relative = path.relative(root, candidate);
-    return relative === "" || (!relative.startsWith("..") && !path.isAbsolute(relative));
+    return (relative === "" ||
+        (!relative.startsWith("..") && !path.isAbsolute(relative)));
 }
 function normalizeArtifactId(id, label) {
     requireString(id, label);

package/dist/tools/registry.d.ts

@@ -1214,6 +1214,7 @@ export declare const allTools: ({
             keywords?: undefined;
             sourcePosts?: undefined;
             selectedPatterns?: undefined;
+            previewBudget?: undefined;
             notes?: undefined;
             createdAt?: undefined;
             draftId?: undefined;
@@ -1279,6 +1280,7 @@ export declare const allTools: ({
             keywords?: undefined;
             sourcePosts?: undefined;
             selectedPatterns?: undefined;
+            previewBudget?: undefined;
             notes?: undefined;
         };
         required: string[];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.238",
+  "version": "0.1.239",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",
@@ -11,6 +11,7 @@
   },
   "scripts": {
     "build": "tsc",
+    "prepack": "npm run build",
     "start": "node dist/index.js",
     "start:dev": "node dist/index-dev.js",
     "dev": "ts-node src/index.ts"

package/skills/create-campaign-v2/references/validation-criteria.md

@@ -93,10 +93,10 @@ Required:
   select a blocked candidate. If all 3 candidates fail, route to
   `revise-message` with the failure reasons enumerated per candidate (cite the
   rule/filter name and the offending line).
-- **Concrete Language Audit.** The selected draft must highlight every abstract
-  verb, abstract noun, abstract adjective, abstract adverb, and cliche, then
-  either replace it with a buyer-visible action, object, workflow, artifact,
-  risk, result, or next step from the approved evidence, cut it, or block with
+- **Concrete Language Audit.** The selected draft must highlight every abstract verb,
+  abstract noun, abstract adjective, abstract adverb, and cliche, then either
+  replace it with a buyer-visible action, object, workflow, artifact, risk,
+  result, or next step from the approved evidence, cut it, or block with
   `revise-message` / `revise-filter`. Do not leave a vague phrase in place just
   because it sounds polished.
 

package/skills/create-post/SKILL.md

@@ -20,7 +20,7 @@ Hard fail patterns:
 - drafts that skip raw idea capture
 - hooks copied verbatim from another creator
 - using `~/.sellable/configs/content/linkedin-posts-drafts.md` as the normal save target
-</role>
+  </role>
 
 <scope>
 V1 is posts-only and hooks-first.
@@ -42,7 +42,7 @@ Do not:
 - optimize a comment workflow
 - move identity/proof/story memory into content files
 - append new drafts to the legacy flat file
-</scope>
+  </scope>
 
 <required_assets>
 Before drafting, load all required assets with `mcp__sellable__get_subskill_asset`:
@@ -90,7 +90,7 @@ Do not call outbound/campaign tools from this skill. Do not call message-generat
 Load user memory before hook generation or drafting:
 
 1. Call `mcp__sellable__get_engage_memory`.
-2. Read or use the returned core memory fields:
+2. Read or use the returned core identity memory and company memory fields:
    - `core/about-me.md`
    - `core/my-company.md`
    - `core/anti-ai-writing-style.md`
@@ -115,6 +115,30 @@ Load user memory before hook generation or drafting:
 New users may have blank or missing core files until they run `$sellable:interview`. If story, proof, identity, or company memory is missing, ask for the missing material or ask the user to run `$sellable:interview`. Never fabricate what should have come from `story-bank.md`, `proof-ledger.md`, or `answer-bank.md`.
 
 The interview/core memory files remain the durable source for stories and proof. This skill may read them, but it must not move them into `~/.sellable/content/**`.
+
+Use core context modes as drafting constraints, not decorative labels. If a
+post idea exposes durable memory that should help future writing, propose a
+core write-back before saving it. The user must be able to approve, edit, or
+reject each proposed memory update before it is written.
+
+Durable write-back targets:
+
+- `core/answer-bank.md` for reusable user answers, positioning, or taste rules
+- `core/wins-ledger.md` for verified wins and outcomes
+- `core/change-log.md` for approved corrections, rejected-but-useful proposals,
+  privacy decisions, and downstream prompt/operator notes
+- `core/story-bank.md` for reusable first-person stories
+- `core/transcripts/INDEX.md` for source interview or voice-memo references
+- `core/references/linkedin-posts/INDEX.md` and adjacent files for approved
+  gold-standard post references
+
+Write-backs must use stable source keys such as
+`create-post:{date}:{ideaId}:{slug}` or
+`create-post-research:{date}:{sourcePostHash}:{slug}`. Check existing copied
+paths before adding references, create no duplicate reference rows, and keep
+manual sections preserved. If the user says to mark private, store only the
+minimum private-safe metadata and do not promote it into public proof,
+references, or examples.
 </memory_contract>
 
 <modes>
@@ -221,6 +245,7 @@ Record provenance:
 - lead-magnet or engagement-bait penalties
 - story mechanism when relevant
 - full-text match status
+- source hook preview measurements and whether they came from full text or a search preview
 - selected hook patterns
 - why each pattern fits the user's idea and voice
 
@@ -233,8 +258,14 @@ Each hook must include:
 - source hook pattern
 - why it fits this idea
 - `charCount`
+- `charCountIncludingNewlines`
 - `firstLineChars`
 - `firstTwoLinesChars`
+- `physicalLineCount`
+- `contentLineCount`
+- `longestNonblankLineChars`
+- `blankLineVisualRisk`
+- `previewBudgetStatus`
 - `mobilePreviewFit`
 - `desktopPreviewFit`
 - `lineCountEstimate`
@@ -246,14 +277,22 @@ Each hook must include:
 
 Do not copy source wording. Copy only the structure.
 
-Use these LinkedIn preview budgets as conservative scoring constraints. LinkedIn rendering varies by device, font, and line break, so these are planning budgets, not exact guarantees:
+Use this conservative mobile-first LinkedIn preview gate. LinkedIn does not
+publish exact "see more" cutoff rules, and rendering varies by device, app
+version, font, media, and line break. These are v1 safety budgets, not claims
+about an official LinkedIn limit:
+
+- `pass`: hook is <= 110 chars including newlines, every nonblank line is <= 45 chars, and the hook's core point lands before likely truncation.
+- `warn`: hook is 111-140 chars including newlines, any nonblank line is 46-55 chars, or blank lines create visual-line risk. Blank lines are allowed, but they count as physical lines.
+- `fail`: hook is > 140 chars including newlines, any nonblank line is > 55 chars, or the hook's point depends on text after likely truncation.
 
-- mobile first line: 35-45 chars
-- mobile first two lines: 80-100 chars
-- desktop first line: 70-90 chars
-- desktop first two lines: 140-180 chars
+Desktop preview usually has more room. Still record `desktopPreviewFit`, but
+never let desktop fit compensate for a mobile `fail`.
 
-If a hook's point depends on text after the likely preview, rewrite it before selecting it.
+If a hook's point depends on text after the likely preview, rewrite it before
+selecting it. A selected hook may carry a `warn` only when the warning is about
+intentional blank-line rhythm or a slight line-length overage; include a compact
+fallback in the validation receipt.
 
 ## Step 3: Draft
 
@@ -287,6 +326,7 @@ Every saved draft needs a validation receipt with:
 - voice audit findings
 - anti-AI audit findings
 - outbound AI-tell audit findings
+- hook preview pass/warn/fail status and compact fallback when warned
 - finalizer changes
 - blocked/retry-needed reasons, if any
 
@@ -319,6 +359,7 @@ Published post records live under:
 ```text
 ~/.sellable/content/linkedin/published/
 ```
+
 </pipeline>
 
 <legacy>
@@ -341,8 +382,9 @@ validation_summary:
   proof: pass | needs_user_input | blocked
   voice: pass | needs_revision
   anti_ai: pass | needs_revision
-  linkedin_preview: pass | needs_revision
+  linkedin_preview: pass | warn | needs_revision
   concrete_language: pass | needs_revision
 next_step: <what the user should do next>
 ```
+
 </response_shape>

package/skills/create-post/references/gold-standard-post-pack.md

@@ -78,6 +78,7 @@ Show compact candidate cards. Include:
 - engagement breakdown when available
 - why it might belong in the pack
 - hook mechanism
+- hook preview budget status and measurement basis
 - content/body mechanism
 - rhythm notes
 - sentence-structure notes
@@ -144,8 +145,15 @@ Tags:
 
 - hook text:
 - char count:
+- char count including newlines:
 - first-line chars:
 - first-two-line chars:
+- physical line count:
+- content line count:
+- longest nonblank line chars:
+- blank-line visual risk:
+- source text basis:
+- preview budget status:
 - mobile preview fit:
 - desktop preview fit:
 - hook mechanism:

package/skills/create-post/references/hook-research-playbook.md

@@ -74,6 +74,47 @@ When full hook/body text matters:
 
 If full text is unavailable, record `full_text_unavailable`. Use only the preview for hook analysis and do not infer missing body details.
 
+## Opening Preview Measurement
+
+Measure the visible opening for every shortlisted source post before extracting
+the hook pattern. This makes the study useful for LinkedIn, not just generally
+"good writing."
+
+LinkedIn does not publish exact "see more" cutoff rules. Treat these as
+conservative v1 planning budgets:
+
+- `pass`: opening hook is <= 110 chars including newlines, every nonblank line
+  is <= 45 chars, and the hook's core point lands before likely truncation.
+- `warn`: opening hook is 111-140 chars including newlines, any nonblank line is
+  46-55 chars, or blank lines create visual-line risk. Blank lines are allowed,
+  but they count as physical lines.
+- `fail`: opening hook is > 140 chars including newlines, any nonblank line is
+  > 55 chars, or the hook's core point depends on text after likely truncation.
+
+Desktop preview has more room, so record it separately, but never let desktop
+fit compensate for a mobile `fail`.
+
+For each source, record:
+
+- `sourceTextBasis`: `full_text`, `search_preview`, or `manual_user_source`
+- `openingTextUsed`
+- `charCountIncludingNewlines`
+- `physicalLineCount`
+- `contentLineCount`
+- `firstLineChars`
+- `firstTwoPhysicalLinesChars`
+- `firstTwoContentLinesChars`
+- `longestNonblankLineChars`
+- `blankLineCountBeforeFold`
+- `mobilePreviewBudget`: `pass`, `warn`, or `fail`
+- `desktopPreviewBudget`: `pass`, `warn`, or `fail`
+- `blankLineVisualRisk`
+- `corePointBeforeLikelyTruncation`
+
+If only a search preview is available, do not pretend the opening is complete.
+Record `sourceTextBasis: search_preview` and lower confidence when the hook
+appears cut off or body context is unavailable.
+
 ## Hook Extraction
 
 Extract structure, not wording.
@@ -85,7 +126,7 @@ For each shortlisted source post, record:
 - engagement totals and available likes/comments/shares breakdown
 - creator repeat evidence
 - visible hook text or preview
-- line count and mobile preview fit
+- opening preview measurement fields from the section above
 - hook mechanism
 - story mechanism when the post is a story
 - internal question created

package/skills/create-post/references/post-file-contract.md

@@ -59,6 +59,9 @@ Hook research files must preserve:
 - author/profile URLs
 - engagement totals
 - full-text availability
+- source hook preview measurements, including text basis, char count including
+  newlines, physical/content line counts, longest nonblank line, blank-line
+  visual risk, and mobile/desktop preview budget status
 - extracted hook patterns
 - selected hook basis
 
@@ -67,7 +70,8 @@ Draft files must preserve:
 - source idea ID
 - hook research ID
 - draft body
-- validation receipt
+- validation receipt, including LinkedIn preview pass/warn/fail status and
+  compact fallback when the selected hook carries a warning
 - status: `draft`, `ready`, or `needs_revision`
 
 Published files must preserve:

package/skills/create-post/references/post-validation.md

@@ -32,7 +32,9 @@ Each candidate should include:
 - hook text
 - source pattern
 - score
-- char count and first-line / first-two-line preview measurements
+- char count including newlines and first-line / first-two-line preview measurements
+- physical line count, content line count, longest nonblank line, and blank-line risk
+- `previewBudgetStatus`: `pass`, `warn`, or `fail`
 - mobile and desktop preview fit
 - proof/story dependency
 - AI-tell risk
@@ -52,25 +54,44 @@ After the first draft:
 
 ## LinkedIn Preview Audit
 
-Audit the selected hook and top candidates against conservative LinkedIn preview budgets:
+Audit the selected hook and top candidates against conservative LinkedIn
+preview budgets. LinkedIn does not publish exact "see more" cutoff rules, and
+rendering varies by device, app version, font, media, and line break. This audit
+is a mobile-first safety gate, not a claim about an official LinkedIn limit.
 
-- mobile first line: 35-45 chars
-- mobile first two lines: 80-100 chars
-- desktop first line: 70-90 chars
-- desktop first two lines: 140-180 chars
+Use:
+
+- `pass`: hook is <= 110 chars including newlines, every nonblank line is <= 45 chars, and the hook's core point lands before likely truncation.
+- `warn`: hook is 111-140 chars including newlines, any nonblank line is 46-55 chars, or blank lines create visual-line risk. Blank lines are allowed, but they count as physical lines.
+- `fail`: hook is > 140 chars including newlines, any nonblank line is > 55 chars, or the hook's point depends on text after likely truncation.
+
+Desktop preview usually has more room. Still record desktop fit, but never let
+desktop fit compensate for a mobile `fail`.
 
 Record:
 
 - `charCount`
+- `charCountIncludingNewlines`
 - `firstLineChars`
 - `firstTwoLinesChars`
+- `physicalLineCount`
+- `contentLineCount`
+- `longestNonblankLineChars`
+- `blankLineCountBeforeFold`
+- `blankLineVisualRisk`
+- `corePointBeforeLikelyTruncation`
+- `previewBudgetStatus`
 - `mobilePreviewFit`
 - `desktopPreviewFit`
 - `lineCountEstimate`
 - `truncationRisk`
 - `rewriteIfTruncated`
+- `compactFallback` when `previewBudgetStatus` is `warn`
 
-LinkedIn rendering varies by device and line break, so this is a planning audit. If the hook only works after likely truncation, rewrite it.
+If the hook only works after likely truncation, rewrite it. A draft cannot be
+`ready` with `previewBudgetStatus: fail`. A draft may be `ready` with
+`previewBudgetStatus: warn` only when the warning is explicit, usually because
+the user prefers blank-line rhythm, and the receipt includes a compact fallback.
 
 ## Simplifier / Concrete-Language Audit
 

package/skills/generate-messages/SKILL.md

@@ -45,6 +45,11 @@ message assets through Sellable MCP tools:
 After candidate generation and revision, and before returning `ready`, load
 `create-campaign-v2-validation` through Sellable MCP as the final gate.
 
+Both live and dry runs must produce or validate `message-validation.md` with
+the same quality gates. The selected winner must pass the `Concrete Language Audit`:
+identify and replace or cut abstract verbs, abstract nouns, abstract adjectives,
+abstract adverbs, and cliches before the message is treated as ready.
+
 Never reconstruct that branch from `brief.md`, `lead-review.md`,
 `lead-sample.json`, `lead-filter.md`, `message-validation.md`, local files, or
 direct database reads. If any required message asset cannot be loaded through MCP