@sellable/mcp 0.1.143 → 0.1.144

package/skills/create-campaign-v2/references/watch-guide-narration.md

@@ -14,14 +14,14 @@ Building campaign with {Claude Code or Codex}               [Exit watch mode]
 {visibleState} {agentIntent}
 
 Next: {nextAction}
-{safety?}
 ```
 
 UI owns the header, driver label, button, progress bar, step count, and static
 stage labels. The driver label comes from the watch URL mode (`mode=claude` or
 `mode=codex`), so do not add separate guide args for it. You own `stage`,
 `headline`, `visibleState`, `agentIntent`, and any exceptional `nextAction`,
-`safety`, `workerStatuses`, or `blockedReason`.
+`workerStatuses`, `blockedReason`, or concise `safety` note for blocked/recovery
+states.
 
 ## Copy Rules
 
@@ -40,6 +40,11 @@ stage labels. The driver label comes from the watch URL mode (`mode=claude` or
   sample you are checking, and why that helps this campaign.
 - At filter choice, do not say filtering the batch before rubrics and message approval are saved.
 - Avoid internal terms: MCP, tool, currentStep, workflow table, scout, debug.
+- Treat `safety` as optional internal context, not a visible disclaimer.
+- Do not repeat long negative lists like "no leads import, no enrichment, no
+  messages, no sequence, no sending" in routine watch copy. Prefer one concise
+  gate phrase only when it matters: "Approval covers scouting/search only" or
+  "Next gate: selected-post scrape."
 - Do not invent time estimates.
 
 ## Stages
@@ -86,8 +91,7 @@ Default source funnel:
   "headline": "Choosing the lead source",
   "visibleState": "The browser is on Pick Provider while Codex explains the source path before opening a provider lane.",
   "agentIntent": "Codex will start with people engaging with relevant LinkedIn posts when that looks plausible, then switch to Sales Nav to find ICP people actively posting on LinkedIn, then search by titles, and use Prospeo for a broader account/contact path. Sales Nav with recent activity remains the first LinkedIn fallback.",
-  "nextAction": "Review source",
-  "safety": "No leads import until you approve the source."
+  "nextAction": "Review source"
 }
 ```
 
@@ -99,8 +103,7 @@ Signal Discovery viability handoff:
   "headline": "Checking Signal Discovery viability",
   "visibleState": "The browser is moving from Pick Provider into Signal Discovery so the exact posts and sample math are visible.",
   "agentIntent": "Codex is testing whether relevant posts have enough ICP-looking engagers before recommending this as the source.",
-  "nextAction": "Review source math",
-  "safety": "No leads import until you approve the source."
+  "nextAction": "Review source math"
 }
 ```
 
@@ -112,8 +115,7 @@ Source direction override:
   "headline": "Testing the requested source",
   "visibleState": "The campaign asked for hiring and account signals, so Codex is starting with Prospeo instead of the default LinkedIn engagement path.",
   "agentIntent": "It is checking whether this source has enough reachable ICP-looking people before importing a review batch.",
-  "nextAction": "Review source",
-  "safety": "No leads import until you approve the source."
+  "nextAction": "Review source"
 }
 ```
 
@@ -125,8 +127,7 @@ Source fallback:
   "headline": "Switching source lanes",
   "visibleState": "The Signal Discovery sample did not show enough ICP-looking engagers for a confident first batch.",
   "agentIntent": "Codex is trying Sales Nav with recent activity so the source can still preserve some buyer activity context.",
-  "nextAction": "Review source",
-  "safety": "No leads import until you approve the source."
+  "nextAction": "Review source"
 }
 ```
 
@@ -149,9 +150,8 @@ Source recommendation ready:
   "stage": "find-leads",
   "headline": "Review the source in Codex",
   "visibleState": "The browser is showing the evaluated Signal Discovery source with counts and sample quality.",
-  "agentIntent": "Approve LinkedIn Engagement or ask for a source change in chat before any leads import.",
-  "nextAction": "Approve in Codex",
-  "safety": "No leads import until you approve the source."
+  "agentIntent": "Approve LinkedIn Engagement or ask for a source change in chat.",
+  "nextAction": "Approve in Codex"
 }
 ```
 
@@ -180,8 +180,7 @@ Source approved and import starting:
   "headline": "Importing the review batch",
   "visibleState": "The browser is still showing the approved LinkedIn Engagement source leads.",
   "agentIntent": "Codex is importing only the bounded 15-row review batch into the campaign now.",
-  "nextAction": "Review batch ready",
-  "safety": "This is still a review step; nothing launches or sends."
+  "nextAction": "Review batch ready"
 }
 ```
 
@@ -199,10 +198,9 @@ After review batch import:
   "visibleState": "The first review batch is in the campaign. The visible sample looks mixed enough that filters should be added before message review.",
   "agentIntent": "Codex is asking whether you want to further filter these leads before message review. Skip filters only if the visible rows already look clean.",
   "nextAction": "Choose filters or skip",
-  "safety": "Nothing enriches, validates, or sends until the message is ready and approved.",
   "workerStatuses": {
     "leadFitBuilder": "idle",
-    "messageDraftBuilder": "idle"
+    "messageDraftBuilder": "running"
   }
 }
 ```
@@ -211,7 +209,8 @@ Use this after the selected review rows are present and before filters are
 saved. This is add-filters intent, not active filtering. Recommend adding
 filters when the sample is mixed/noisy, tell the user to Choose filters or skip,
 and do not say filtering the batch before rubrics and message approval are
-saved. Only show worker statuses as running if those branches actually started.
+saved. The Message Draft Builder should start immediately after the bounded
+review batch exists; mark it running only when that branch actually started.
 When the user chooses filters, immediately persist `enableICPFilters: true` and
 move to `create-icp-rubric` so the watched app shows Filter Rules while Codex
 defines the rules in chat. After `save_rubrics`, move to `apply-icp-rubric`
@@ -242,11 +241,28 @@ Review ready:
   "headline": "Review the message template",
   "visibleState": "The browser remains on Filter Leads while the message template is reviewed in chat.",
   "agentIntent": "Codex is waiting for approval before saving the template to the campaign brief and queueing enrichment/filtering.",
-  "nextAction": "Approve or revise the template",
-  "safety": "Codex will only continue after you approve."
+  "nextAction": "Approve or revise the template"
 }
 ```
 
+Template approved, bounded filter test running:
+
+```json
+{
+  "stage": "fit-message",
+  "headline": "Template saved",
+  "visibleState": "The browser stays on Filter Leads while the bounded enrichment and filter test runs.",
+  "agentIntent": "Codex saved the approved message template, queued the review-batch Enrich Prospect cells, and is waiting for at least one row to pass before moving to Messages.",
+  "nextAction": "Move to Messages after a passing row"
+}
+```
+
+Do not move to Messages immediately after `approve-message`. The visible route
+is already Filter Leads after `save_rubrics`; approving the message only unlocks
+the bounded cascade from that screen. Move to Messages only once at least one
+review-batch row passes and Generate Message cells are ready/running for the
+passing rows.
+
 Messages waiting for template:
 
 ```json
@@ -255,8 +271,7 @@ Messages waiting for template:
   "headline": "Waiting for the template",
   "visibleState": "The fit rules are saved and the message template is still being prepared.",
   "agentIntent": "Codex is waiting until the template can be reviewed.",
-  "nextAction": "Review template",
-  "safety": "No enrichment, filtering, or Generate Message cells run until the template is approved."
+  "nextAction": "Review template"
 }
 ```
 

package/skills/create-campaign-v2/references/watch-link-handoff.md

@@ -36,7 +36,7 @@ Example skeleton:
 I created the campaign shell with the brief already in it.
 You can watch the lead source, filters, and messages fill in from here.
 
-No leads import and nothing sends yet.
+I’ll pause at the next approval gate before sourcing.
 
 Watch link: [Open campaign]({watchUrl})
 

package/skills/create-campaign-v2-tail/SKILL.md

@@ -36,10 +36,13 @@ Step 13 — import/confirm review batch only
   update_campaign(currentStep=filter-choice)
 
 Post-import main thread
-  launch Lead Fit Builder + Message Draft Builder after workflowTableId exists
+  launch Message Draft Builder immediately after workflowTableId + review rows exist
+  launch Lead Fit Builder only after user chooses filters
   save_rubrics({ campaignOfferId, leadScoringRubrics }) after the campaign table exists
-  show readable filters + one concrete sample message
-  after approval, update_campaign_brief writes `## Approved Message Template` with `{{...}}` tokens
+  keep the watched app on Filter Leads after rubrics are saved
+  while on Filter Leads, show the message template recommendation from the background Message Draft Builder
+  after approve-message, update_campaign_brief writes `## Approved Message Template` with `{{...}}` tokens
+  only then start the bounded review-batch cascade
 
 Step 14 — kick bounded cascade + observe sample
   queue_cells(cellIds=<review-batch Enrich Prospect cells only>)  <-- starts bounded chain
@@ -58,7 +61,9 @@ Step 15 — observe messaging
   get_rows_minimal                 # confirm passing rows have completed Generate Message cells
   (rare) queue_cells on any pending Generate Message cells
   token-contract spot check via get_rows
-  update_campaign(currentStep=awaiting-user-greenlight)
+  update_campaign(currentStep=auto-execute-messaging) with review-ready narration
+  ask the user to approve generated review-batch messages before Settings
+  only after approval: update_campaign(currentStep=awaiting-user-greenlight)
   (generate_messages is NOT an MCP tool; messages come from the cascade)
 
 Step 16 — awaiting-user-greenlight
@@ -144,7 +149,9 @@ what changed and orient the user to what the watch link will show next —
 reuse the v1 `create-campaign` watch-mode pattern verbatim.
 
 Resume currentStep names covered by this tail: `"auto-execute-leads"`,
-`"validate-sample"`, `"auto-execute-messaging"`,
+`"apply-icp-rubric"` (the visible Filter Leads home for the logical
+`validate-sample` loop), `"validate-sample"` (legacy resumes only),
+`"auto-execute-messaging"`,
 `"awaiting-user-greenlight"`, `"settings"`, `"sequence"`, `"send"`, and
 `"running"`. New mint-early runs normally
 enter Step 13 from `"confirm-lead-list"`; the `"auto-execute-leads"` string is
@@ -273,10 +280,12 @@ caller or start the workflow-table cascade too early. The cascade starts in
 Step 14 only after `save_rubrics` and `update_campaign_brief` have both
 succeeded.
 
-## Step 14: validate-sample (loop)
+## Step 14: validate-sample (logical loop on Filter Leads)
 
-Entered on `CampaignOffer.currentStep === "validate-sample"`. Full
-decision tree lives in `references/sample-validation-loop.md`.
+Entered after the message template is approved while the watched campaign is
+already on `CampaignOffer.currentStep === "apply-icp-rubric"` / Filter Leads.
+Do not route to a visible `validate-sample` step. Full decision tree lives in
+`references/sample-validation-loop.md`.
 
 **Step 14 starts the bounded cascade, then observes it.** Step 13 imported the
 review batch only. After `save_rubrics` and the approved message template are
@@ -381,8 +390,9 @@ Template`. If it does not, fail before the cascade runs. Do not repair
 5. If the sample fails the token contract, diagnose brief-vs-list
    (same revision loop as Step 14) and escalate if over
    `maxRevisionRounds`.
-6. On success, `update_campaign({ campaignId, currentStep:
-"awaiting-user-greenlight" })`.
+6. On success, keep `currentStep: "auto-execute-messaging"` and ask the user
+   to approve the generated review-batch messages. Only that approval may move
+   the campaign to Settings / `awaiting-user-greenlight`.
 
 **Do NOT hand-write message bodies via `update_cell`.** `update_cell`
 is reachable for legitimate operator overrides AFTER the tail hands
@@ -428,8 +438,11 @@ strings, which is why Step 16 requires Step 15 to be complete.
 6. If the sample fails the token contract or critique, diagnose +
    loop the same way Step 14 does (brief-vs-list), subject to the same
    `maxRevisionRounds` cap.
-7. On success, `update_campaign({ campaignId, currentStep:
-"awaiting-user-greenlight" })` and orient the user.
+7. On success, keep `currentStep: "auto-execute-messaging"`, show that the
+   review-batch messages are ready in Messages, and ask for approval before
+   Settings. Only after the user approves those generated messages should
+   `update_campaign({ campaignId, currentStep: "awaiting-user-greenlight" })`
+   run.
 
 Critique failure modes NEVER escalate. A critic timeout, a total
 timeout, a budget trip, a fake-proof rejection, or an unsupported-
@@ -451,7 +464,7 @@ Shape:
    `get_campaign_navigation_state` when available to confirm the watch link is
    visibly on Settings.
 4. Explain why the sender matters: Sellable needs a connected LinkedIn sender
-   before anything can send. Explain Slack reply review before launch: replies
+   for launch. Explain Slack reply review before launch: replies
    and approvals need a place the team will actually monitor, so Slack should be
    connected or intentionally skipped before launch.
 5. If no connected sender exists, surface a direct Settings link:

package/skills/research/config.json

@@ -0,0 +1,9 @@
+{
+  "parallelMode": "wide",
+  "agentCount": 6,
+  "maxToolCallsPerAgent": 2,
+  "senderMaxAgents": 2,
+  "senderMaxToolCallsPerAgent": 3,
+  "progressMode": true,
+  "debugMode": true
+}