@sellable/mcp 0.1.262 → 0.1.264

package/dist/tools/registry.d.ts

@@ -1260,6 +1260,19 @@ export declare const allTools: ({
             body?: undefined;
             validationReceipt?: undefined;
             status?: undefined;
+            postText?: undefined;
+            sourceLabel?: undefined;
+            measurementMode?: undefined;
+            requireBrowserMeasurement?: undefined;
+            clampLines?: undefined;
+            mobileClampLines?: undefined;
+            desktopClampLines?: undefined;
+            mobileTextWidthPx?: undefined;
+            desktopTextWidthPx?: undefined;
+            renderId?: undefined;
+            renderScreenshots?: undefined;
+            requireScreenshots?: undefined;
+            reviewClampLines?: undefined;
             updatedAt?: undefined;
             publishUrl?: undefined;
             activityId?: undefined;
@@ -1295,6 +1308,7 @@ export declare const allTools: ({
         properties: {
             draftId: {
                 type: string;
+                description?: undefined;
             };
             ideaId: {
                 type: string;
@@ -1339,6 +1353,19 @@ export declare const allTools: ({
             selectedPatterns?: undefined;
             previewBudget?: undefined;
             notes?: undefined;
+            postText?: undefined;
+            sourceLabel?: undefined;
+            measurementMode?: undefined;
+            requireBrowserMeasurement?: undefined;
+            clampLines?: undefined;
+            mobileClampLines?: undefined;
+            desktopClampLines?: undefined;
+            mobileTextWidthPx?: undefined;
+            desktopTextWidthPx?: undefined;
+            renderId?: undefined;
+            renderScreenshots?: undefined;
+            requireScreenshots?: undefined;
+            reviewClampLines?: undefined;
             updatedAt?: undefined;
             publishUrl?: undefined;
             activityId?: undefined;
@@ -1361,6 +1388,7 @@ export declare const allTools: ({
         properties: {
             draftId: {
                 type: string;
+                description?: undefined;
             };
             hookResearchId: {
                 type: string;
@@ -1403,6 +1431,19 @@ export declare const allTools: ({
             previewBudget?: undefined;
             notes?: undefined;
             createdAt?: undefined;
+            postText?: undefined;
+            sourceLabel?: undefined;
+            measurementMode?: undefined;
+            requireBrowserMeasurement?: undefined;
+            clampLines?: undefined;
+            mobileClampLines?: undefined;
+            desktopClampLines?: undefined;
+            mobileTextWidthPx?: undefined;
+            desktopTextWidthPx?: undefined;
+            renderId?: undefined;
+            renderScreenshots?: undefined;
+            requireScreenshots?: undefined;
+            reviewClampLines?: undefined;
             publishUrl?: undefined;
             activityId?: undefined;
             publishedAt?: undefined;
@@ -1424,6 +1465,7 @@ export declare const allTools: ({
         properties: {
             draftId: {
                 type: string;
+                description?: undefined;
             };
             publishUrl: {
                 type: string;
@@ -1464,6 +1506,19 @@ export declare const allTools: ({
             body?: undefined;
             validationReceipt?: undefined;
             status?: undefined;
+            postText?: undefined;
+            sourceLabel?: undefined;
+            measurementMode?: undefined;
+            requireBrowserMeasurement?: undefined;
+            clampLines?: undefined;
+            mobileClampLines?: undefined;
+            desktopClampLines?: undefined;
+            mobileTextWidthPx?: undefined;
+            desktopTextWidthPx?: undefined;
+            renderId?: undefined;
+            renderScreenshots?: undefined;
+            requireScreenshots?: undefined;
+            reviewClampLines?: undefined;
             updatedAt?: undefined;
             publishedPostId?: undefined;
             year?: undefined;
@@ -1516,6 +1571,19 @@ export declare const allTools: ({
             body?: undefined;
             validationReceipt?: undefined;
             status?: undefined;
+            postText?: undefined;
+            sourceLabel?: undefined;
+            measurementMode?: undefined;
+            requireBrowserMeasurement?: undefined;
+            clampLines?: undefined;
+            mobileClampLines?: undefined;
+            desktopClampLines?: undefined;
+            mobileTextWidthPx?: undefined;
+            desktopTextWidthPx?: undefined;
+            renderId?: undefined;
+            renderScreenshots?: undefined;
+            requireScreenshots?: undefined;
+            reviewClampLines?: undefined;
             updatedAt?: undefined;
             publishUrl?: undefined;
             activityId?: undefined;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.262",
+  "version": "0.1.264",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-post/SKILL.md

@@ -108,6 +108,8 @@ Use these MCP tools when available:
 - `mcp__sellable__get_post_idea`
 - `mcp__sellable__list_post_ideas`
 - `mcp__sellable__save_hook_research`
+- `mcp__sellable__calculate_linkedin_hook_preview`
+- `mcp__sellable__render_linkedin_post_preview`
 - `mcp__sellable__save_post_draft`
 - `mcp__sellable__update_post_draft`
 - `mcp__sellable__list_post_draft_iterations`
@@ -342,7 +344,9 @@ Visible Flow Trace
 
 4. Hook Autopsies
 - source hook:
-- rendered/mobile preview or preview-basis:
+- calculated mobile/desktop visible blocks from
+  `calculate_linkedin_hook_preview` or authenticated LinkedIn screenshot:
+- optional visual artifact from `render_linkedin_post_preview`:
 - see-more tension:
 - curiosity debt:
 - body promise:
@@ -402,7 +406,8 @@ Visible Flow Trace
 
 11. Hook Lab
 - at least 12 hooks:
-- rendered preview record or explicit preview-basis:
+- calculated preview from `calculate_linkedin_hook_preview`:
+- optional visual artifact from `render_linkedin_post_preview` for finalists:
 - hook-to-body promise:
 - score:
 - selected hook:
@@ -829,17 +834,36 @@ Each hook must include:
 
 Do not copy source wording. Copy only the structure.
 
-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.
+Use the rendered-preview contract from
+`references/linkedin-preview-rendering.md`. LinkedIn does not publish exact
+"see more" cutoff rules, and rendering varies by device, app version, font,
+media, and line break. Treat character counts as diagnostics only, not as proof
+that the hook will render before "see more."
+
+The selected hook and top candidates must include literal mobile and desktop
+visible blocks from `mcp__sellable__calculate_linkedin_hook_preview`.
+Observed LinkedIn screenshots and current third-party preview tools support a
+line-count model: review the first 3 rendered visual lines, not the first 210
+characters. Blank lines and `--` separators consume visible preview lines.
+Use `mcp__sellable__render_linkedin_post_preview` only when a visual QA artifact
+is useful.
+
+Use:
+
+- `pass`: rendered mobile preview shows the pain, proof, or curiosity by the end
+  of the first 3 rendered lines, and either the core point is visible or a
+  specific intentional open loop is visible with immediate body payoff planned
+- `warn`: rendered mobile preview creates useful curiosity but wrapping,
+  blank-line rhythm, media risk, or one missing context word weakens it; include
+  a compact fallback
+- `fail`: the hook's real point appears after the rendered mobile review clamp,
+  the visible open loop is vague, blank lines consume the preview before the
+  point, or desktop fit is the only reason it looks good
 
 Desktop preview usually has more room. Still record `desktopPreviewFit`, but
-never let desktop fit compensate for a mobile `fail`.
+never let desktop fit compensate for a mobile `fail`. Do not tell the user "we
+know" how LinkedIn will render unless there is an authenticated LinkedIn
+screenshot; say it passes the renderer and show the visible blocks.
 
 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

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

@@ -256,19 +256,33 @@ 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.
+LinkedIn does not publish exact "see more" cutoff rules. Treat preview fit as a
+rendered-line problem first, not a fixed character-count rule. Current
+third-party preview tools and 2026 creator references generally cluster around:
+
+- mobile feed: about 2-3 visible text lines, often around 140 characters when
+  there is no media
+- desktop feed: about 3-4 visible text lines, often around 210 characters when
+  there is no media
+- media posts can show fewer text lines before truncation
+- blank lines and `--` style separators consume visible preview lines
+
+Use `references/linkedin-preview-rendering.md` as the required gate. Character
+budgets are diagnostics only:
+
+- `pass`: rendered mobile preview shows the pain, proof, or curiosity by the end
+  of the first 3 rendered lines, and the hook creates a specific click reason
+- `warn`: rendered mobile preview creates useful curiosity but loses one useful
+  context word, wraps awkwardly, or spends a visible line on blank space or a
+  separator; include a compact fallback
+- `fail`: the hook's real point appears after the rendered mobile review clamp,
+  the visible open loop is vague, blank lines consume the preview before the
+  point, or desktop fit is the only reason it looks good
 
 Desktop preview has more room, so record it separately, but never let desktop
-fit compensate for a mobile `fail`.
+fit compensate for a mobile `fail`. Never say "we know" how LinkedIn will render
+the hook unless there is an authenticated LinkedIn screenshot. Say the hook
+`passes the renderer` and show the mobile/desktop visible blocks.
 
 For each source, record:
 
@@ -282,6 +296,8 @@ For each source, record:
 - `firstTwoContentLinesChars`
 - `longestNonblankLineChars`
 - `blankLineCountBeforeFold`
+- `renderedPreview`: literal mobile and desktop visible blocks from
+  `references/linkedin-preview-rendering.md`
 - `mobilePreviewBudget`: `pass`, `warn`, or `fail`
 - `desktopPreviewBudget`: `pass`, `warn`, or `fail`
 - `blankLineVisualRisk`

package/skills/create-post/references/linkedin-preview-rendering.md

@@ -5,14 +5,56 @@ research, hook candidate generation, gold-standard decomposition, and draft
 validation.
 
 Character budgets are only diagnostics. They are not the preview gate. A hook is
-not studied, selected, or ready until it has been rendered through this contract
-or through a stricter authenticated LinkedIn screenshot.
+not studied, selected, or ready until its visible mobile and desktop blocks come
+from `mcp__sellable__calculate_linkedin_hook_preview` or from a stricter
+authenticated LinkedIn screenshot.
+
+Do not let the LLM imagine wrapping. The normal path is a function call that
+returns rendered mobile and desktop lines. HTML and PNG outputs from
+`mcp__sellable__render_linkedin_post_preview` are optional visual QA artifacts,
+not the primary interface.
 
 ## Rendering Basis
 
 LinkedIn does not publish exact feed truncation rules, and rendering can vary by
 surface, app version, device, media attachment, and account state. Use this
-deterministic renderer as the MCP review gate for unpublished drafts.
+deterministic function as the MCP review gate for unpublished drafts.
+
+Simple operating policy: judge the hook by the first 3 rendered lines. Use ~140
+characters on mobile and ~210 characters on desktop as guardrails only. If the
+3-line preview and the character guardrail disagree, trust the rendered lines.
+
+Call:
+
+```json
+mcp__sellable__calculate_linkedin_hook_preview({
+  "postText": "<full post text or candidate hook block>",
+  "sourceLabel": "<draft id, hook id, or source label>",
+  "measurementMode": "browser"
+})
+```
+
+When local Chrome is available, browser measurement is the preferred functional
+basis because it asks the browser layout engine to wrap the text under the
+contract. When Chrome is unavailable, the tool falls back to the deterministic
+width model and must mark that basis.
+
+Treat "see more" as a rendered-line problem first and a character-count problem
+second. Observed LinkedIn screenshots show the current desktop feed behaving
+like a first-3-rendered-lines clamp: a first line, a blank line, and a third
+line can be all that appears before `... more`.
+
+- review gate: first 3 rendered visual lines
+- mobile feed: tighter because the text column is narrower
+- desktop feed: more characters can fit per line, but still review line count
+- posts with media may show fewer text lines before truncation
+- blank lines and intentional separators consume visible preview lines
+- device width, font scaling, app version, browser, and profile/page context can
+  move the cutoff
+
+Because of that variation, never say a hook is guaranteed to render before
+"see more." Say `pass`, `warn`, or `fail` under the rendered-preview contract,
+and show the visible mobile and desktop blocks.
 
 When an authenticated LinkedIn feed/composer/browser screenshot is available,
 that screenshot is the strongest evidence. Still record the fields below so
@@ -48,13 +90,16 @@ selected hook must include a `renderedPreview` record:
 
 ```text
 renderedPreview:
-  basis: linkedin_css_contract | authenticated_linkedin_screenshot | manual_user_source
-  cssContractVersion: linkedin-preview-rendering/v1
+  basis: linkedin_rendering_rule_function | authenticated_linkedin_screenshot | manual_user_source
+  cssContractVersion: linkedin-preview-rendering/v2
   mobile:
     textWidthPx: 308
     fontSizePx: 14
     lineHeightPx: 21
-    visibleTextBlock: <literal first rendered review-clamp block>
+    clampLines: 3
+    charGuardrail: 140
+    measurementBasis: local_chrome_browser_layout | estimated_width_model
+    visibleTextBlock: <literal first 3 rendered lines>
     renderedLines:
       - <line 1 exactly as wrapped>
       - <line 2 exactly as wrapped>
@@ -68,12 +113,14 @@ renderedPreview:
     payoffPlannedImmediatelyAfterClamp: true | false
     seeMoreClickReason: <why a reader would click see more>
     seeMoreRisk: pass | warn | fail
-    screenshotPath: <optional local path>
   desktop:
     textWidthPx: 582
     fontSizePx: 14
     lineHeightPx: 21
-    visibleTextBlock: <literal first rendered review-clamp block>
+    clampLines: 3
+    charGuardrail: 210
+    measurementBasis: local_chrome_browser_layout | estimated_width_model
+    visibleTextBlock: <literal first 3 rendered lines>
     renderedLines:
       - <line 1 exactly as wrapped>
       - <line 2 exactly as wrapped>
@@ -83,7 +130,6 @@ renderedPreview:
     corePainProofOrCuriosityVisible: true | false
     corePointVisible: true | false
     seeMoreRisk: pass | warn | fail
-    screenshotPath: <optional local path>
   diagnostics:
     charCount: <number>
     charCountIncludingNewlines: <number>
@@ -96,10 +142,9 @@ renderedPreview:
     rewriteIfTruncated: <short fallback>
 ```
 
-If a host cannot produce screenshots, it must still produce the literal wrapped
-line blocks using the CSS contract. If it cannot produce either screenshots or
-literal line wraps, return `blocked` or `needs_revision`; do not claim the hook
-passed preview validation from character counts alone.
+If a host cannot produce literal wrapped line blocks from
+`calculate_linkedin_hook_preview`, return `blocked` or `needs_revision`; do not
+claim the hook passed preview validation from character counts alone.
 
 ## Study Rules
 

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

@@ -320,22 +320,38 @@ proof from another creator, save as `needs_revision`.
 
 ## LinkedIn Preview Audit
 
-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.
+Audit the selected hook and top candidates against the rendered-preview
+contract. LinkedIn does not publish exact "see more" cutoff rules, and rendering
+varies by device, app version, font, media, line break, and whether the post has
+media attached. This audit is a mobile-first safety gate, not a claim about an
+official LinkedIn limit.
+
+Treat character counts as diagnostics only. The gate is the literal rendered
+mobile and desktop visible block from `references/linkedin-preview-rendering.md`
+or an authenticated LinkedIn screenshot.
 
 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.
+- `pass`: the rendered mobile preview shows the pain, proof, or curiosity by the
+  end of the first 3 rendered lines, and either the core point is visible or a
+  specific intentional open loop is visible with immediate body payoff planned
+- `warn`: the rendered mobile preview creates useful curiosity but wrapping,
+  blank-line rhythm, media risk, or one missing context word weakens it; include
+  a compact fallback
+- `fail`: the hook's real point appears after the rendered mobile review clamp,
+  the visible open loop is vague, blank lines consume the preview before the
+  point, or desktop fit is the only reason it looks good
 
 Desktop preview usually has more room. Still record desktop fit, but never let
 desktop fit compensate for a mobile `fail`.
 
 Record:
 
+- `renderedPreview`
+- `renderedPreviewBasis`: `linkedin_css_contract` |
+  `authenticated_linkedin_screenshot` | `manual_user_source`
+- literal mobile visible block
+- literal desktop visible block
 - `charCount`
 - `charCountIncludingNewlines`
 - `firstLineChars`
@@ -355,9 +371,11 @@ Record:
 - `compactFallback` when `previewBudgetStatus` is `warn`
 
 If the hook only works after likely truncation, rewrite it. A draft cannot be
-`ready` with `previewBudgetStatus: fail`. A draft may be `ready` with
+`ready` with `previewBudgetStatus: fail`, with no rendered preview block, or
+with only a character-count claim. 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.
+the user prefers blank-line rhythm, separators, or a deliberate open loop, and
+the receipt includes a compact fallback.
 
 ## Simplifier / Concrete-Language Audit