@sellable/mcp 0.1.272 → 0.1.273

package/package.json

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

package/skills/create-post/SKILL.md

@@ -606,6 +606,7 @@ Visible Flow Trace
 - worker status per person:
 - recent posts sampled:
 - voice model:
+- mechanics receipts:
 - complete voice variants:
 - follower-adjusted signal when available:
 - hook/body moves worth stealing:
@@ -623,6 +624,11 @@ Visible Flow Trace
 - proof gate:
 - voice gate:
 - anti-AI gate:
+- local finalizer pass:
+- turn separators added:
+- contractions applied:
+- lowercase pass:
+- abstract-to-concrete rewrites:
 - mobile preview gate:
 - template adaptation gate:
 - hook-to-body repayment:
@@ -1242,6 +1248,42 @@ either completed for every active configured influencer or the validation
 receipt has an explicit user opt-out reason. A light source-research summary
 does not satisfy this gate.
 
+## Step 3.5: Local Finalizer Pass
+
+Run this pass after the canonical draft exists and before validation and save.
+
+1. Add `--` between each major turn in the post so the story is easier to read.
+   Use it to separate turns such as hook, context, problem, mechanism, product
+   proof, concrete example, and CTA. Do not add `--` inside a tight list where
+   it would make the post harder to scan.
+2. Use contractions in the draft body by default: `don't`, `isn't`, `that's`,
+   `it's`, `can't`, `we're`, `you're`, and similar natural phrasing. Keep the
+   non-contracted form only when the user explicitly wrote it that way, when a
+   quoted line must stay exact, or when the contraction would sound unnatural.
+3. Keep optional headings, section labels, and line starts lowercase by default
+   when the post still reads naturally. Preserve proper nouns, acronyms, product
+   names, and required capitalization such as `Claude`, `LinkedIn`, `Codex`,
+   `Sellable.dev`, `Clay`, `HeyReach`, and `ICP`.
+4. Run a Harry Dry-style concrete-language audit:
+   - highlight every abstract or vague word/phrase in the validation receipt
+     before saving
+   - replace each one in the draft with a concrete object, action, number,
+     example, screen, list, person, place, or visible workflow step
+   - prefer words a reader can picture, such as `lead list`, `send settings`,
+     `reply inbox`, `follow-up`, `team post`, `warm LinkedIn prospect`,
+     `reply handling`, or `one sentence in Claude Code`
+   - do not make a phrase concrete by inventing proof, metrics, customers, or
+     product behavior the user did not provide
+5. Record this pass in the validation receipt as `localFinalizerPass` with:
+   - `turnSeparatorsAdded: yes | no` and a short reason
+   - `contractionsApplied: yes | no`
+   - `lowercasePass: yes | no` with preserved proper nouns listed
+   - `abstractToConcreteRewrites`, listing each abstract phrase, why it was
+     weak, and the concrete replacement used
+
+If this pass cannot be completed, save the draft as `needs_revision` instead of
+`ready`, and explain which finalizer requirement failed.
+
 ## Step 4: Validation
 
 Use `references/post-validation.md`.
@@ -1280,6 +1322,8 @@ Every saved draft needs a validation receipt with:
 - outbound AI-tell audit findings
 - hook preview pass/warn/fail status and compact fallback when warned
 - finalizer changes
+- local finalizer pass with turn separators, contractions, lowercase pass, and
+  abstract-to-concrete rewrites
 - blocked/retry-needed reasons, if any
 
 If validation fails, do not save the draft as `ready`. Save as `needs_revision` or return blocked/retry-needed.

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

@@ -118,6 +118,10 @@ Draft files must preserve:
   promise, concrete examples, abstractions to remove, and draft risks
 - validation receipt, including LinkedIn preview pass/warn/fail status and
   compact fallback when the selected hook carries a warning
+- local finalizer pass: whether `--` turn separators were added, whether
+  contractions were applied, whether lowercase style was applied where safe,
+  preserved proper nouns/acronyms, and abstract-to-concrete rewrites with the
+  before/after phrases used in the final draft
 - visible flow trace when the user asked for whole-flow, debug, or step-by-step
   mode, including checkpoint statuses, quality break, downstream effect, and
   whether the trace was shown before saving

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

@@ -125,6 +125,41 @@ After the first draft:
 9. preserve the user's actual story and point
 10. remove AI tells
 11. re-check LinkedIn preview fit after edits
+12. add `--` between major story turns when it improves scanability
+13. use natural contractions by default
+14. keep optional headings, section labels, and line starts lowercase when safe
+15. run the concrete-language audit below and replace abstract phrasing before
+    saving
+
+### Local Finalizer Pass
+
+Before a draft can be saved as `ready`, record a local finalizer pass. This is
+the last copy pass after the draft body exists and before `save_post_draft`.
+
+Record:
+
+- `turnSeparatorsAdded`: yes | no
+- `turnSeparatorReason`: where `--` was inserted or why it was skipped
+- `contractionsApplied`: yes | no
+- `contractionsChanged`: examples such as `do not -> don't`, `is not -> isn't`,
+  `that is -> that's`, or `it is -> it's`
+- `lowercasePass`: yes | no
+- `preservedCapitalization`: proper nouns, acronyms, product names, and required
+  capitalization such as `Claude`, `LinkedIn`, `Codex`, `Sellable.dev`, `Clay`,
+  `HeyReach`, and `ICP`
+- `abstractToConcreteRewrites`: every abstract phrase flagged, why it was weak,
+  and the concrete replacement used
+
+Save as `needs_revision` when:
+
+- major story turns are visually hard to follow and no `--` separators or other
+  clear turn markers were added
+- the draft keeps stiff non-contracted phrasing without a user/source reason
+- optional headings or labels stay title-cased in a way that clashes with the
+  user's lowercase post style
+- meaningful abstract phrases remain in the draft after the concrete-language
+  audit
+- the validation receipt does not show what changed during this finalizer pass
 
 ## Visible Flow Trace Audit
 
@@ -260,7 +295,9 @@ or practical next action.
 ## Abstraction-To-Concrete Rewrite Audit
 
 Record every meaningful abstraction found in the draft and the concrete
-replacement. Do not merely say "made concrete."
+replacement. Do not merely say "made concrete." Use a Harry Dry-style standard:
+if the reader cannot picture the word on a screen, in a list, in a sentence they
+would type, or as a workflow step someone could perform, make it more concrete.
 
 Use this format:
 
@@ -279,11 +316,25 @@ Common abstractions to flag:
 - vague nouns such as `signal`, `market`, `attention`, `system`, `quality`,
   `context`, `machine`, or `workflow` when the sentence does not name the actual
   source, action, number, or object
+- vague product words such as `orchestrator`, `campaign object`, `GTM
+  superpowers`, `agentic`, `AI-native`, or `platform` when the sentence does not
+  name the visible work being done
 - broad persona labels used as lead sources
 - "warm" without explaining what made the source warm
 - "offer" without explaining why the recipient would believe or want it
 - "learning" without naming what metric changes the next decision
 
+Concrete replacements should name visible things, for example:
+
+- `lead list`
+- `send settings`
+- `reply inbox`
+- `follow-up`
+- `team post`
+- `warm LinkedIn prospect`
+- `reply handling`
+- `one sentence in Claude Code`
+
 Do not make language concrete by inventing facts. If the concrete replacement
 requires missing proof, ask the user or save as `needs_revision`.