@sellable/mcp 0.1.263 → 0.1.265

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

@@ -5,45 +5,49 @@ 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
-`mcp__sellable__render_linkedin_post_preview` or through a stricter
+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. Character counts and hand-written line
-blocks are only fallback diagnostics. The normal path is tool-rendered mobile
-and desktop artifacts: HTML always, and PNG screenshots whenever local Chrome is
-available.
+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__render_linkedin_post_preview({
+mcp__sellable__calculate_linkedin_hook_preview({
   "postText": "<full post text or candidate hook block>",
   "sourceLabel": "<draft id, hook id, or source label>",
-  "renderScreenshots": true
+  "measurementMode": "browser"
 })
 ```
 
-When screenshots are produced, the PNG files are the review artifact. When
-screenshots cannot be produced, the HTML artifact is still deterministic and
-must be opened or explicitly marked as lower confidence.
+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. Current third-party preview tools and 2026 creator references generally
-cluster around these working assumptions:
-
-- 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
-- posts with media may show fewer text lines before truncation, sometimes only
-  1-2 lines
+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
@@ -86,13 +90,16 @@ selected hook must include a `renderedPreview` record:
 
 ```text
 renderedPreview:
-  basis: local_chrome_headless_screenshot | linkedin_css_contract_html | 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 or tool estimated block when screenshot is the authority>
+    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>
@@ -106,13 +113,14 @@ renderedPreview:
     payoffPlannedImmediatelyAfterClamp: true | false
     seeMoreClickReason: <why a reader would click see more>
     seeMoreRisk: pass | warn | fail
-    htmlPath: <local path>
-    screenshotPath: <local path when Chrome rendered PNG>
   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>
@@ -122,8 +130,6 @@ renderedPreview:
     corePainProofOrCuriosityVisible: true | false
     corePointVisible: true | false
     seeMoreRisk: pass | warn | fail
-    htmlPath: <local path>
-    screenshotPath: <local path when Chrome rendered PNG>
   diagnostics:
     charCount: <number>
     charCountIncludingNewlines: <number>
@@ -136,11 +142,9 @@ renderedPreview:
     rewriteIfTruncated: <short fallback>
 ```
 
-If a host cannot produce screenshots, it must still produce and preserve the
-HTML artifacts from `render_linkedin_post_preview`. If it cannot produce
-screenshots, HTML artifacts, or literal wrapped line blocks, 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-file-contract.md

@@ -67,9 +67,14 @@ Hook research files must preserve:
 - 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
+- audience tension snapshot and selected angle
 - rendered preview records for kept source hooks and adapted hook blocks,
   including literal mobile/desktop preview blocks and whether the first-screen
   promise is visible
+- thought leader inspiration packets when the user supplied creators, including
+  worker status, profile URL/handle, recent posts reviewed, weighted winners,
+  follower-adjusted signal when available, allowed mechanics to adapt, and
+  forbidden borrowing
 - source-message outlines for keeper posts, preserving source paragraph order
   and branching each paragraph, line, or phrase into high-level goal, reader
   effect, reusable move, and adaptation guard without reproducing the full
@@ -94,6 +99,9 @@ Draft files must preserve:
 - draft body
 - source-message outline for any outside post being adapted, when the draft's
   body shape was learned from a specific source post
+- thought leader inspiration lab when used, including the selected inspiration
+  adapter, variants considered, Christian/Sellable voice layer, and
+  copying/voice-clone risk
 - pre-draft narrative outline: hierarchical `I.`, `A.`, `i.` outline covering
   hook debt, thesis, reader, core mechanism, definitions, proof claims,
   working body patterns adapted, narrative beats, mobile scan path, body

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

@@ -28,7 +28,8 @@ Every saved draft needs a validation receipt. A draft without this receipt is no
 - `storyFilesConsulted`
 - `goldStandardsConsulted`
 - `voiceRulesApplied`
-- `marketBeliefAudit`
+- `audienceTensionAudit`
+- `thoughtLeaderInspirationLab`
 - `premiseValueAudit`
 - `mobileScanabilityAudit`
 - `templateAdaptationAudit`
@@ -110,7 +111,7 @@ Each candidate should include:
 After the first draft:
 
 1. remove unsupported claims
-2. verify the draft is anchored to the selected market belief and controversy
+2. verify the draft is anchored to the selected audience tension and credible angle
 3. verify the real story/scene, tension, and reader value are visible early
 4. verify the body repays the selected hook's curiosity debt
 5. verify the final post follows the selected positioning sequence or explains
@@ -181,7 +182,7 @@ Record:
   artifact is `preDraftNarrativeOutline`
 - `premiseQualityGates`: pass/fail for `specific_scene_or_pattern`,
   `clear_reader`, `visible_tension`, `reader_value`, `credible_speaker`,
-  `proof_safety`, `market_heat`, and `pre_draft_narrative_outline`
+  `proof_safety`, `audience_tension`, and `pre_draft_narrative_outline`
 - `bodyOutline`: how the body delivers the premise before prose
 - `viralPostOutline`: the selected narrative structure, including beat jobs
 - `hookToBodyPromiseMap`: how the body repays the hook's open loop
@@ -296,27 +297,53 @@ Save as `needs_revision` when the draft copies outside wording, borrows outside
 proof, keeps a source template's status without equivalent user authority, or
 uses a hook whose promised body payoff is not delivered.
 
-## Market Belief Audit
+## Audience Tension Audit
 
 Before a draft can be `ready`, validate that it is not merely an internally
-coherent idea. It must be anchored to the saved research's market belief map.
+coherent idea. It must be anchored to the saved research's audience tension
+snapshot.
 
 Record:
 
 - `resonatingIdea`: the current-space idea this draft enters
-- `implicitBelief`: the belief the audience likely already holds
+- `visibleAudienceTension`: the contradiction, tradeoff, cost, or unfinished
+  question readers are reacting to
 - `audienceWant`: what the audience wants permission, leverage, proof, or a new
   category for
-- `audienceResentmentOrFear`: what frustration or risk gives the post tension
-- `selectedControversy`: the claim the post is testing
+- `audienceObjectionOrFear`: what skepticism, frustration, or risk gives the post tension
+- `selectedAngle`: the claim the post is testing
 - `credibleWhyUs`: why the user can credibly say this from raw idea, memory,
   story, proof, or product mechanism
 - `engagementReason`: why someone would react, comment, repost, or argue
 - `unsupportedHypeRemoved`: unsupported claims removed during finalizer
 
-If `selectedControversy` is missing, if the audience belief is only a generic
-label like "founders want growth," or if `credibleWhyUs` depends on borrowed
-proof from another creator, save as `needs_revision`.
+If `selectedAngle` is missing, if the audience tension is only a generic label
+like "founders want growth," or if `credibleWhyUs` depends on borrowed proof
+from another creator, save as `needs_revision`.
+
+## Thought Leader Inspiration Audit
+
+When the user supplied thought leaders or creators, validate that inspiration
+was used as structural adaptation, not persona cloning.
+
+Record:
+
+- `thoughtLeaderList`: names and profile URLs or handles
+- `workerPackets`: one packet per person, or `not_available` with reason
+- `weightedWinners`: best posts used, with follower-adjusted signal when
+  available
+- `normalizationConfidence`: high | medium | low
+- `inspirationAdapters`: hook/body mechanics selected for adaptation
+- `voiceLayer`: must be `Christian/Sellable`
+- `forbiddenBorrowingAvoided`: source wording, proof, jokes, personal stories,
+  status, and persona markers avoided
+- `variantsConsidered`: adapted variants generated from the selected premise
+- `selectedVariant`: winning adapter and why
+- `copyingOrVoiceCloneRisk`: pass | needs_revision | blocked
+
+Save as `needs_revision` when a draft imitates a living person's voice, borrows
+their proof/status, copies outside wording, or lets a creator with a giant
+audience win without any follower-adjusted or confidence-adjusted signal.
 
 ## LinkedIn Preview Audit
 

package/skills/create-post/references/premise-development.md

@@ -3,7 +3,7 @@
 A strong post is not an idea with a better hook. A strong post is a valuable
 premise wrapped in a sharp opening.
 
-Use this stage after market/hook research and before hook candidates. V2 premise
+Use this stage after audience/hook research and before hook candidates. V2 premise
 development also consumes the source post templates from hook research:
 post positioning breakdowns, viral-post outlines, hook-to-body promise maps, and
 body expression inputs.
@@ -109,7 +109,7 @@ tension:
 reader value:
 <what the reader learns, sees differently, or can do after reading>
 
-why now / market heat:
+why now / audience tension:
 <what current research says is resonating>
 
 credible why-us:
@@ -366,7 +366,7 @@ A premise can move to hook generation only when it passes all of these:
 - `reader_value`: pass
 - `credible_speaker`: pass
 - `proof_safety`: pass
-- `market_heat`: pass or explained
+- `audience_tension`: pass or explained
 - `template_fit`: pass or explicitly no-template
 - `hook_to_body_repayment`: pass
 - `pre_draft_narrative_outline`: pass