@sellable/mcp 0.1.549 → 0.1.550

package/skills/create-evergreen-campaigns/SKILL.md

@@ -134,19 +134,6 @@ run without user input, or similar, run in **automation mode**:
     exactly one quality-valid route-proof row when needed, and attach the
     recommended sequence, but it still must not launch campaigns, schedule
     sends, send messages, or spend paid InMail.
-  - **Connection-only evergreen completion is optional and non-default.** Use it
-    only when the prompt explicitly says connection-only, invite-only,
-    connection request only, no DMs, or no follow-ups. Pass the typed option
-    `campaignSequenceOptions:{ mode:"connection_only" }` plus an explicit
-    `workspaceId` to `setup_evergreen_campaigns`. Omit
-    `campaignSequenceOptions` for the standard tier-recommended Premium,
-    Sales Nav, Recruiter, and paid InMail behavior.
-    Connection-only completion still creates/reuses the same evergreen lanes,
-    source rows, and paused/unlaunched review state, but it attaches only the
-    canonical invite template and persists `currentStep:"send"` as the paused
-    review step. It does not require Message Drafting, generated messages,
-    route-proof approval, first DM, InMail, View Profile fallback, follow-up
-    branch, launch, scheduling, or sends.
 
 If the invoking prompt explicitly asks for interactive message polish or sample
 proof, run in **interactive polish mode** and use the confirmation/sample steps
@@ -733,9 +720,6 @@ not a parent-thread summary. The receipt must include:
   creation, preserve that original packet only in a separate `parentLanePacket`
   object; do not leave `setupPlanCall.campaignId:null` or
   `setupPlanCall.tableId:null`.
-  If the parent plan used connection-only, the receipt must also include
-  `setupPlanCall.campaignSequenceOptions:{ "mode":"connection_only" }` or
-  `setupPlanCall.sequencePolicy.mode:"connection_only"`.
   Short form: For create lanes, `setupPlanCall.campaignId` and `setupPlanCall.tableId` must be the actual created campaign/table ids.
   Short form: Do not leave `setupPlanCall.campaignId:null` or `setupPlanCall.tableId:null`.
 - `createCampaignWorkflowReceipt`: proof the worker loaded the actual installed
@@ -826,40 +810,22 @@ not a parent-thread summary. The receipt must include:
   them into canonical `promptLoadedToHasMoreFalse`, `requiredAssetsLoaded`,
   `validationLoaded`, `reviewBatchRowHash`, and
   `messageDraftRecommendation`.
-  Connection-only lanes are the exception: do not include
-  `messageDraftingReceipt` or run generated-message prep unless the operator
-  separately asked for message copy. The parent verifier expects no message
-  proof for connection-only lanes.
 - `reviewBatchReceipt`: review-batch row ids/hash, generated row count,
   quality-valid route-proof row id when approved, and proof that no broad
   approve-all occurred.
-  Connection-only lanes are the exception: do not approve a route-proof row and
-  do not include a required review-batch receipt.
 - `sequenceReceipt`: exact current workflowTableId, recommended non-paid
   sequence attach/precheck result, and readback showing `hasSequence:true` when
   completion is claimed. If the tool output uses
   `attachRecommendedSequenceResult.actionTypes` or
   `nonPaidRecommendedSequence`, copy them to canonical `actionTypes` and
   `nonPaid`.
-  For connection-only lanes, do not call `attach_recommended_sequence`. Attach
-  with `attach_sequence({ tableId, templateRef:"connection_only", currentStep:"send" })`, then
-  include exact current-template proof:
-  `sequenceReceipt.hasSequence:true`,
-  `sequenceReceipt.actionTypes:["send_invite"]`, and
-  `sequenceReceipt.nonPaid:true`. Receipts that only say
-  `tool:"attach_recommended_sequence"` or include `send_dm`,
-  `send_inmail_open`, `send_inmail_closed`, or `view_profile` are failing
-  connection-only receipts.
 - final paused-send proof: if the current campaign table is `DRAFT` after the
   sequence is attached, call the product `pause_campaign({ campaignId })`
   endpoint/tool to put the unlaunched campaign into `PAUSED` review state, then
   reread the campaign/table. Do not raw-write `campaignStatus`, do not start or
   launch, and do not schedule/send. Completion requires reread proof of
-  `currentStep:"send"` and `campaignStatus:"PAUSED"` for standard and
-  connection-only customer-visible lanes. `send` is the product's paused
-  review step; do not use unsupported aliases such as `review` as final proof.
-  If the raw output nests this in `finalCampaignRead` or `finalTableRead`, copy
-  it to canonical
+  `currentStep:"send"` and `campaignStatus:"PAUSED"`. If the raw output nests
+  this in `finalCampaignRead` or `finalTableRead`, copy it to canonical
   `finalPausedSendProof.currentStep` and
   `finalPausedSendProof.campaignStatus`.
 - `verifyCall`: the exact `setup_evergreen_campaigns({ mode:"verify",
@@ -1122,14 +1088,9 @@ plain row generation. The lane worker must inline the same
    approvedGeneratedMessageCount exactly 1. Do not report completion with 2+
    approved rows.
    Approval shorthand: Do not report completion with 2+ approved rows.
-8. Standard mode: continue to
-   `attach_recommended_sequence({ campaignId, currentStep:"send" })` and, if
-   the campaign is still `DRAFT`, `pause_campaign({ campaignId })`. Reread the
-   campaign/table before claiming completion.
-   Connection-only mode: skip Message Drafting and route-proof approval, call
-   `attach_sequence({ tableId, templateRef:"connection_only", currentStep:"send" })`, prove
-   `sequenceReceipt.actionTypes:["send_invite"]`, and pause/reread without
-   launching or sending.
+8. Continue to `attach_recommended_sequence({ campaignId, currentStep:"send" })`
+   and, if the campaign is still `DRAFT`, `pause_campaign({ campaignId })`.
+   Reread the campaign/table before claiming completion.
 
 That packaged worker path must return `messageDraftingReceipt.statusSource:
 "packaged-generate-messages-worker"`. It is accepted only when the receipt
@@ -1554,14 +1515,11 @@ Message, and verify current-revision sample messages before final completion.
      - DM lanes: add a `Delivery format:` line — either `multiline (each paragraph sends as its own DM message)` or `single message`. When multiline, the template's blank-line paragraphs ARE the message boundaries — write each one as a standalone typed message.
      - **InMail lanes can never be multiline**: an InMail is one message and the recipient must reply before anything else can be sent. InMail-bound templates must read as one cohesive message — declare `Delivery format: single message (InMail — no follow-up until reply)` and never structure the copy to depend on multi-message pacing.
 
-   - In standard mode, the sequence is auto-selected by sender tier; do not hand-author sequence
+   - The sequence is auto-selected by sender tier; do not hand-author sequence
      templates here. Sales Nav/Recruiter senders may receive the unified Sales
      Nav cascade through `attach_recommended_sequence`; attaching it does not
      spend paid InMail credits by itself. Do not substitute the manual Paid
      InMail Campaign template.
-     For explicit connection-only evergreen lanes only, use the backend-owned
-     `attach_sequence({ tableId, templateRef:"connection_only", currentStep:"send" })` path and do
-     not call `attach_recommended_sequence`.
 3. **Customer-Visible Completion Contract**: a named evergreen lane that appears
    as a campaign card or campaign-backed table is not done when the shell exists.
    It is done only when the customer can open the campaign and land on final
@@ -1585,7 +1543,7 @@ Message, and verify current-revision sample messages before final completion.
       evergreen setup. Do not leave customer-visible campaigns at
       `filter-choice`, `filter-rules`, or `apply-icp-rubric` and report success.
       Do not proceed to Message Drafting until saved filters are applied.
-   - In standard mode, Message Drafting has run from the current campaign/table basis, using the
+   - Message Drafting has run from the current campaign/table basis, using the
      create-campaign message prompt/assets and validation gate. Updating
      `currentStep:"messages"` is not proof. Parent-thread handwritten copy is
      not a substitute. The proof receipt must show
@@ -1626,9 +1584,6 @@ Message, and verify current-revision sample messages before final completion.
       Fallback samples must still reject source/conversation hedges such as
       `"hope this is relevant"`, `"might be interested"`, or `"saw you in a few
       conversations"`.
-     For explicit connection-only lanes, this whole Message Drafting and sample
-     proof block is not required and must not be faked with parent-written
-     messages.
    - The first review batch exists and at least 3 review rows have generated
      messages from the approved brief. If fewer than 3 usable rows exist, report
      the actual count and why.
@@ -1641,7 +1596,7 @@ Message, and verify current-revision sample messages before final completion.
      completion, approve exactly one quality-valid generated row. If one or more
      rows are already approved, do not add more approvals during evergreen
      completion. Never broad approve all rows.
-    - In standard mode, the recommended tier-aware sequence is attached to the current campaign
+    - The recommended tier-aware sequence is attached to the current campaign
       table, and the watched campaign is on Send. Use
       `attach_recommended_sequence({ campaignId, currentStep:"send" })` when a
       safe attach is needed. After `confirm_lead_list` or any source-list copy,
@@ -1656,10 +1611,6 @@ Message, and verify current-revision sample messages before final completion.
       manual Paid InMail Campaign, and never attach/replace sequence outside the
       current table unless the current lane packet explicitly allowed sequence
       repair.
-      For explicit connection-only lanes, the current campaign table must have
-      exactly the canonical invite-only sequence:
-      `sequenceReceipt.actionTypes:["send_invite"]`. Any DM, InMail, or View
-      Profile action means the lane is not complete.
     - If the current campaign table is still `DRAFT` after sequence/readiness
       proof, call `pause_campaign({ campaignId })` and reread. `pause_campaign`
       is the product-native review-state transition; it is not a launch and does

package/skills/refill-sends/SKILL.md

@@ -196,11 +196,6 @@ rather than asking which campaign class to fill. If a stale target plan selects
 planner before mutation.
 Short form: trust the target plan's inferred lane when it is a connection invite,
 paid-InMail refill lane, or unified Sales Nav cascade.
-Connection-only evergreen campaigns with exact `["send_invite"]` sequence proof
-are plain invite capacity: treat them as `selectedLane:"send_invite"` only. Do
-not infer DM, InMail, Sales Nav cascade, paid-credit refresh, message
-generation, follow-up, sequence mutation, launch/start, scheduling override, or
-direct-send work from a connection-only lane.
 
 Structured planner packet:
 

package/skills/refill-sends-v2/SKILL.md

@@ -62,11 +62,6 @@ for lease expiry; never guess a fence.
 The default `intent:"auto"` inspects `managed_waterfall`,
 `dashboard_evergreen`, and `active_campaign` lane sources. Report the lane
 source and lane chain as proof for every selected sender.
-Connection-only evergreen lanes are invite-only refill targets. When the packet
-or campaign proof shows exactly `["send_invite"]`, report and execute only
-`selectedLane:"send_invite"` work; do not infer DM, InMail, Sales Nav cascade,
-paid-credit refresh, message generation, follow-up, sequence mutation,
-launch/start beyond packet authority, scheduler writes, or direct sends.
 
 If membership blocks a workspace read, report the structured
 `workspace_access` blocker instead of retrying auth or switching workspaces.

package/skills/refill-sends-v2-workflow/SKILL.md

@@ -61,13 +61,6 @@ the repair rung, such as re-run errored enrichment/message cells
 (`start_campaign`). The loop bounds and refuses repair loops; it never invents
 a fix list.
 
-Connection-only evergreen packets are invite-only. If the selected lane or
-campaign proof is exactly `["send_invite"]`, the workflow may refill only
-`selectedLane:"send_invite"` capacity. Do not treat that lane as a DM, InMail,
-Sales Nav cascade, paid-credit refresh, generated-message requirement,
-follow-up branch, sequence-repair task, scheduler write, launch/send, or
-provider-family continuation.
-
 Use plain-language labels first and tokens second, for example "copy leads
 already found into the campaign table (`reconcile_source_copy`)".
 

package/skills/refill-sends-v2-workflow/core/flow.v1.json

@@ -52,7 +52,6 @@
     "awaiting scheduler is not an end state; window-closed reports name remaining-ready, expected pickup time, and resume handle",
     "honest-rubric-fail means a human updates the rubric or changes lead source",
     "source replenishment beyond same-source-automatic is a scoped create-campaign handoff, never refill-owned provider search",
-    "connection-only evergreen lanes with exact [\"send_invite\"] proof are invite-only refill capacity; never infer DM, InMail, Sales Nav cascade, paid-credit refresh, message generation, follow-up, sequence mutation, scheduler writes, launch, or send work from them",
     "no campaign creation, provider-family switch, threshold lowering, scheduler writes, sends, archives, deletes, or brief/filter/message/sequence/sender mutation without a separate approval packet"
   ],
   "requiredBootstrap": [