@sellable/mcp 0.1.112 → 0.1.114

package/agents/source-scout-linkedin-engagement.md

@@ -17,14 +17,22 @@ Use the inherited Sellable MCP tools when available:
 - `search_signals` to find recent post lanes. Include `campaignOfferId` whenever
   the parent provides one so selected searches/lists stay attached to the
   campaign.
-- `fetch_post_engagers` to sample engagers from selected posts.
+- `select_promising_posts` to promote the exact posts you will sample into the
+  campaign UI before fetching engagers. In campaign-attached runs, do this
+  before the first `fetch_post_engagers` call so the user can see which posts
+  are being sampled.
+- `fetch_post_engagers` to sample engagers from promoted/selected posts.
 
 Process:
 
 1. Read the campaign brief, kickoff doc, or lane prompt supplied by the parent.
 2. Search 3-5 keyword/topic lanes, favoring fresh posts from the last 7-14 days.
-3. Select 3-5 promising posts when available.
-4. Fetch or sample engagers for selected posts and score rough ICP fit from visible headline/display-name cues only. Do not enrich people during viability estimation.
+3. Select 3-5 promising posts when available. If a `campaignOfferId` was
+   supplied, call `select_promising_posts({ campaignOfferId, selectionMode:
+"replace", selections, headlineICPCriteria, currentStep:
+"signal-discovery" })` before sampling so the watched Signal Discovery table
+   shows the promoted posts.
+4. Fetch or sample engagers for promoted posts and score rough ICP fit from visible headline/display-name cues only. Do not enrich people during viability estimation.
 5. Estimate usable prospects per selected post from sampled pass rate. If the sample is good but volume is low, say how many more similar posts should be added or scraped.
 6. Return false positives and dead ends explicitly.
 

package/dist/tools/campaigns.js

@@ -25,6 +25,9 @@ export function buildWatchUrl(config, path) {
     if (workspaceId && !url.searchParams.has("workspaceId")) {
         url.searchParams.set("workspaceId", workspaceId);
     }
+    if (config.token && !url.searchParams.has("token")) {
+        url.searchParams.set("token", config.token);
+    }
     return url.toString();
 }
 export function getCampaignBuilderWatchModeParam() {

package/dist/tools/context.d.ts

@@ -81,7 +81,8 @@ export declare function getCampaignContext(input: GetCampaignContextInput): Prom
         };
         watchUrl: {
             urlPresent: boolean;
-            direct: boolean | undefined;
+            direct: boolean;
+            autoLogin: boolean;
             redirectPath: string | null;
         };
         table: {

package/dist/tools/context.js

@@ -179,6 +179,7 @@ export function markCampaignContextDirty(campaignId, reason) {
             watchUrl: {
                 urlPresent: false,
                 direct: false,
+                autoLogin: false,
                 redirectPath: null,
             },
             table: {

package/dist/tools/leads.js

@@ -1047,7 +1047,7 @@ export const leadToolDefinitions = [
     },
     {
         name: "select_promising_posts",
-        description: "Select the most promising LinkedIn posts for lead scraping AND provide headline ICP criteria. Use the selectionTarget returned by search_signals (default 3).",
+        description: "Select the most promising LinkedIn posts for lead scraping AND provide headline ICP criteria. Use the selectionTarget returned by search_signals (default 3). In campaign-attached sampling, call select_promising_posts first to promote the sampled posts into the watched UI before fetch_post_engagers.",
         inputSchema: {
             type: "object",
             properties: {

package/dist/tools/linkedin.js

@@ -21,7 +21,7 @@ export const linkedinToolDefinitions = [
     },
     {
         name: "fetch_post_engagers",
-        description: "Fetch people who engaged with a LinkedIn post (reactions and/or comments). Returns deduplicated engagers with name, headline, profileUrl, and source. Use 'comments' for lead magnets to get people who actively engaged. Uses smart rate limiting and parallel fetching.",
+        description: "Fetch people who engaged with a LinkedIn post (reactions and/or comments). Returns deduplicated engagers with name, headline, profileUrl, and source. Use 'comments' for lead magnets to get people who actively engaged. Uses smart rate limiting and parallel fetching. In campaign-attached Signal Discovery sampling, call select_promising_posts first to promote the sampled posts into the watched UI.",
         inputSchema: {
             type: "object",
             properties: {

package/dist/tools/navigation.d.ts

@@ -81,7 +81,8 @@ export declare function computeCampaignNavigationStateFromCampaign(campaign: Cam
     };
     watchUrl: {
         urlPresent: boolean;
-        direct: boolean | undefined;
+        direct: boolean;
+        autoLogin: boolean;
         redirectPath: string | null;
     };
     table: {
@@ -125,7 +126,8 @@ export declare function getCampaignNavigationState(input: GetCampaignNavigationS
     };
     watchUrl: {
         urlPresent: boolean;
-        direct: boolean | undefined;
+        direct: boolean;
+        autoLogin: boolean;
         redirectPath: string | null;
     };
     table: {

package/dist/tools/navigation.js

@@ -385,7 +385,9 @@ function parseWatchUrl(watchUrl, campaignId) {
     if (!watchUrl) {
         return {
             urlPresent: false,
+            direct: false,
             signed: false,
+            autoLogin: false,
             redirectPath: null,
             warning: null,
         };
@@ -398,11 +400,15 @@ function parseWatchUrl(watchUrl, campaignId) {
                 url.searchParams.get("mode") === "codex" ||
                 url.searchParams.get("mode") === "watch");
         if (isDirectCampaignUrl) {
+            const autoLogin = Boolean(url.searchParams.get("token"));
             return {
                 urlPresent: true,
                 direct: true,
+                autoLogin,
                 redirectPath: `${url.pathname}?${url.searchParams.toString()}`.replace(/\?$/, ""),
-                warning: null,
+                warning: autoLogin
+                    ? null
+                    : "Watch URL is direct but missing token auto-login. Recover a fresh /campaign-builder/{campaignId}?mode={claude|codex}&token=... watch link before asking the user to open it.",
             };
         }
         const redirect = url.searchParams.get("redirect");
@@ -413,18 +419,20 @@ function parseWatchUrl(watchUrl, campaignId) {
         return {
             urlPresent: true,
             direct: false,
+            autoLogin: false,
             redirectPath: decodedRedirect,
             warning: isLegacySigned
-                ? "Watch URL still uses a tokenized /auth/continue handoff. Return the safe direct /campaign-builder/{campaignId}?mode={claude|codex} watch URL instead."
-                : "Watch URL is not a safe direct /campaign-builder/{campaignId}?mode={claude|codex} watch link.",
+                ? "Watch URL still uses a tokenized /auth/continue handoff. Return the direct /campaign-builder/{campaignId}?mode={claude|codex}&token=... watch URL instead."
+                : "Watch URL is not a direct /campaign-builder/{campaignId}?mode={claude|codex}&token=... watch link.",
         };
     }
     catch {
         return {
             urlPresent: true,
             direct: false,
+            autoLogin: false,
             redirectPath: null,
-            warning: "Watch URL is malformed; recover a fresh safe direct campaign-builder watch link before browser handoff.",
+            warning: "Watch URL is malformed; recover a fresh direct campaign-builder auto-login watch link before handing it to the user.",
         };
     }
 }
@@ -593,6 +601,7 @@ export function computeCampaignNavigationStateFromCampaign(campaign, options) {
         watchUrl: {
             urlPresent: watchUrlState.urlPresent,
             direct: watchUrlState.direct,
+            autoLogin: watchUrlState.autoLogin,
             redirectPath: watchUrlState.redirectPath,
         },
         table: {

package/dist/tools/readiness.d.ts

@@ -134,7 +134,8 @@ export declare function waitForCampaignTableReady(input: WaitForCampaignTableRea
         };
         watchUrl: {
             urlPresent: boolean;
-            direct: boolean | undefined;
+            direct: boolean;
+            autoLogin: boolean;
             redirectPath: string | null;
         };
         table: {
@@ -183,7 +184,8 @@ export declare function waitForCampaignTableReady(input: WaitForCampaignTableRea
         };
         watchUrl: {
             urlPresent: boolean;
-            direct: boolean | undefined;
+            direct: boolean;
+            autoLogin: boolean;
             redirectPath: string | null;
         };
         table: {
@@ -234,7 +236,8 @@ export declare function waitForCampaignTableReady(input: WaitForCampaignTableRea
         };
         watchUrl: {
             urlPresent: boolean;
-            direct: boolean | undefined;
+            direct: boolean;
+            autoLogin: boolean;
             redirectPath: string | null;
         };
         table: {

package/dist/tools/rubrics.js

@@ -204,7 +204,7 @@ export const rubricToolDefinitions = [
     },
     {
         name: "save_rubrics",
-        description: "Persist rubric criteria to the campaign. Pass leadScoringRubrics directly to save without drafting. Use update_campaign to enable ICP filtering and change steps.",
+        description: "Persist rubric criteria to the campaign. Pass leadScoringRubrics directly to save without drafting. Saving active rubrics enables ICP filtering on the campaign so the client can continue to Filter Leads.",
         inputSchema: {
             type: "object",
             properties: {
@@ -355,7 +355,7 @@ export const rubricToolDefinitions = [
                 },
                 minPassedCount: {
                     type: "number",
-                    description: "Optional pass floor for bounded create-campaign samples. When this floor is met and remaining target rows are resolved as failed/not processing, the tool returns ready:true with partial:true instead of forcing a timeout.",
+                    description: "Optional pass floor for bounded create-campaign samples. When this floor is met, the tool returns ready:true with partial:true instead of waiting for every target row to finish.",
                 },
                 timeoutMs: {
                     type: "number",
@@ -686,11 +686,13 @@ export async function waitForRubricResults(input) {
                 stats,
             };
         }
-        if (minPassFloorMet && noActiveProcessing) {
+        if (minPassFloorMet) {
             const percent = completed > 0 ? Math.round((passed / completed) * 100) : 0;
-            const reason = unresolvedRowsResolvedAsFailures
-                ? "min_passed_count_met_with_resolved_failures"
-                : "min_passed_count_met_no_active_processing";
+            const reason = !noActiveProcessing
+                ? "min_passed_count_met_with_active_processing"
+                : unresolvedRowsResolvedAsFailures
+                    ? "min_passed_count_met_with_resolved_failures"
+                    : "min_passed_count_met_no_active_processing";
             const rowSnapshot = includeRows
                 ? await getTableRowsMinimal(tableId, {
                     limit: effectiveTarget,

package/dist/tools/watch-url-security.js

@@ -6,9 +6,13 @@ function sanitizeWatchUrlValue(value) {
             if (redirect) {
                 const direct = new URL(decodeURIComponent(redirect), url.origin);
                 const workspaceId = url.searchParams.get("workspaceId");
+                const token = url.searchParams.get("token");
                 if (workspaceId && !direct.searchParams.has("workspaceId")) {
                     direct.searchParams.set("workspaceId", workspaceId);
                 }
+                if (token && !direct.searchParams.has("token")) {
+                    direct.searchParams.set("token", token);
+                }
                 return direct.toString();
             }
         }

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -134,6 +134,12 @@ claim they ran in parallel and do not surface install status to the customer. In
 chat, call the downstream copy stage `message generation`;
 `message-validation.md` is only an internal proof artifact.
 
+For campaign-attached Signal Discovery sampling, promote/select the exact posts
+with `select_promising_posts` before `fetch_post_engagers` so the user can see
+which posts are being sampled in the watched app. The watch guide should say
+that we are pulling sample engagers from these posts to confirm the ICP is
+actually engaging and the source is viable.
+
 After find-leads returns a lead source and the user approves it, use the same
 registry pattern for the two post-lead branches. The create-campaign-v2 subskill
 calls `get_post_find_leads_scout_registry`, then launches the returned
@@ -159,45 +165,42 @@ linked skill versions, runbooks, npm/package details, repo-local files, VPS or
 browser automation limitations, or local skill files in normal customer-facing
 copy.
 
-## Codex Watch Browser Handoff
+## Codex Watch Link Handoff
 
-When a campaign tool returns `watchUrl`, treat it as an active browser handoff,
-not only a URL to print. A valid handoff link must be a safe direct
-`/campaign-builder/{campaignId}?mode=claude` URL. `create_campaign.watchUrl`,
+When a campaign tool returns `watchUrl`, treat it as a user-opened app link, not
+as permission to drive the browser. A valid handoff link must be a direct
+`/campaign-builder/{campaignId}?mode=claude|codex` URL with the auth token and
+workspace routing needed for auto-login. `create_campaign.watchUrl`,
 `create_campaign({ campaignId }).watchUrl`, and `get_campaign.watchUrl` are all
-acceptable only when they return that direct campaign-builder shape, with
-`workspaceId` used only as a safe routing hint when needed.
-
-In Codex Desktop, when in-app browser control is available, open the returned watch link on the user's behalf. After opening it, inspect the browser-visible campaign state, then explain what the user is seeing before continuing with more campaign tools. Use customer language such as:
-
-```text
-I’ll open the campaign view and keep it in sync as I build.
-```
+acceptable only when they return that direct campaign-builder shape.
 
-If browser control is unavailable, provide the watch link without discussing the
-runtime limitation. In off-desktop Codex runs, make the direct watch link easy
-to copy/open, then continue with explicit customer-facing campaign progress and
-`get_campaign_navigation_state` orientation checks.
-Use this fallback shape:
+Never call browser-opening tools, shell `open`, Computer Use, or in-app browser
+automation just because a watch link exists. Print the link and tell the user to
+Command-Enter/click it when they want to watch in the app. Use this shape:
 
 ```text
 Watch link: {watchUrl}
 
-I’ll keep the campaign brief, lead source, and message-review steps explicit
-here as I build.
+Command-Enter or click that link to watch the campaign in Sellable. I’ll keep
+the brief, lead source, and message-review steps explicit here as I build.
 ```
 
-If opening the watch link lands on an auth, 404, permission, blank, or visible
-error state, report only what is visible, recover a fresh watch link once with
-`create_campaign({ campaignId })` or `get_campaign`, and try that link. Do not
-claim the browser was opened, inspected, or synchronized unless the visible
-browser state was actually observed. Do not claim the browser was opened unless
-it was opened and observed.
+The watch link should auto-login through the token in the URL. If the user says
+the link lands on auth, 404, permission, blank, or a visible error state, recover
+a fresh watch link once with `create_campaign({ campaignId })` or `get_campaign`
+and print that link. Do not claim the browser was opened, inspected, or
+synchronized.
 
 After every `update_campaign({ campaignId, currentStep })`, use
 `get_campaign_navigation_state` when available as a compact orientation check:
-match the browser-visible step to the saved campaign state, explain the current
-state in one sentence, and only then continue. Sender selection belongs at Settings after message approval and 10-row validation. After message validation, use Settings to help the user connect or select a LinkedIn sender. Explain Slack reply review before launch. After sender selection, attach the recommended sequence and move the watched UI to Send. Do not start the campaign or trigger a live send unless the user explicitly confirms that launch action outside UAT.
+match the saved campaign state to the expected watch-link step, explain the
+current state in one sentence, and only then continue. Sender selection belongs
+at Settings after message approval and 10-row validation. After message
+validation, use Settings to help the user connect or select a LinkedIn sender.
+Explain Slack reply review before launch. After sender selection, attach the
+recommended sequence and move the watched UI to Send. Do not start the campaign
+or trigger a live send unless the user explicitly confirms that launch action
+outside UAT.
 
 ## Names To Use
 

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

@@ -186,8 +186,10 @@ Optional debug/UAT draft directory, disabled in normal customer runs:
   `references/watch-guide-narration.md` for the compact screen contract. Do not
   send separate guide headline/body args. In Find Leads, the static stage label
   is not enough: name the active lane/provider, what search or sample you are
-  trying, and why it fits this campaign. Do not promise time estimates in guide
-  copy.
+  trying, and why it fits this campaign. When the source recommendation and
+  counts/sample quality are ready in chat, update the guide to tell the user to
+  review and approve the source in Codex/Claude instead of saying `I'll show`
+  the recommendation later. Do not promise time estimates in guide copy.
 - Every approval gate must include live campaign access after the readable inline
   content. Show a short `Watch link:` line with the campaign link when a
   campaign shell exists. In normal customer runs, do not show `Open artifact:`
@@ -580,6 +582,21 @@ workstreams`, `in parallel`, or `background` unless parallel branches were
   `attach_recommended_sequence`, `attach_sequence`, and `start_campaign`.
   `create_campaign`, `update_campaign`, and `save_rubrics` are allowed only when
   the active `flow.v2.json` step allows them.
+- When source approval moves into import, keep chat and watch narration in the
+  same moment. If chat says import is starting, send `watchNarration` with
+  `stage: "review-batch"`, current-tense copy such as `Importing the review
+batch`, and a no-launch safety note. Do not leave the guide saying
+  `source approved` or `I'll show the review-batch outcome` once import is
+  starting.
+- After Lead Fit Builder saves rubrics, move the watched browser to Filter
+  Leads before waiting for message work to finish. Persist
+  `enableICPFilters: true`, `currentStep: "apply-icp-rubric"`, and
+  `watchNarration.stage: "fit-message"` so the user can see fit filtering
+  happen while the first message sample finishes. After message approval,
+  persist `useMessagingTemplate: true` and keep `enableICPFilters: true`;
+  sample validation then runs the review-batch cascade, and the user should be
+  walked through fit results, generated message results, and
+  Settings/sender/sequence handoff.
 - During pre-import validation, do not call `check_rubric`; use the lead-filter
   artifacts and only use campaign-backed scoring after Step 13 imports the
   15-lead test batch.
@@ -788,7 +805,9 @@ Required behavior:
   `lead-review.md` focused on source evidence, not host-agent availability.
   - Branch A: LinkedIn Engagement / active LinkedIn posts (internal provider:
     Signals / `signal-discovery`). Search relevant keyword lanes, review
-    finalist posts, fetch top-post engagers, and estimate warm-fit volume.
+    finalist posts, promote the sampled posts with `select_promising_posts`
+    before fetching engagers when a campaign shell exists, fetch top-post
+    engagers, and estimate warm-fit volume.
   - Branch B: Sales Nav / title + company filters. Run preview filters, inspect
     preview rows, and estimate scalable-fit volume.
   - Branch C: Prospeo Contact / domains only when the campaign has a
@@ -1002,7 +1021,9 @@ lower confidence instead of presenting a precise estimate.
 
 For Signals, default to sampling a few promising posts first rather than trying
 to prove the entire source can scale before the user sees evidence. Pick 3-5
-fresh, high-density posts when available, sample engagers, show fit rate, then
+fresh, high-density posts when available. In campaign-attached watch runs,
+promote those posts with `select_promising_posts` before sampling so the user
+sees which posts are being tested. Then sample engagers, show fit rate, and
 state how many additional posts could be added/scraped if that first sample is
 good but volume is low.
 

package/skills/create-campaign-v2/core/flow.v2.json

@@ -330,11 +330,12 @@
             "campaignBrief"
           ],
           "watchUrlSource": "create_campaign.watchUrl",
-          "requiredWatchUrlShape": "direct /campaign-builder/{campaignId}?mode={claude|codex} watch URL",
+          "requiredWatchUrlShape": "direct /campaign-builder/{campaignId}?mode={claude|codex} watch URL with token auto-login and workspace routing",
           "codexBrowserHandoff": {
-            "openWhenAvailable": true,
-            "inspectBeforeContinuing": true,
-            "explainVisibleStateBeforeContinuing": true,
+            "openWhenAvailable": false,
+            "printWatchLinkOnly": true,
+            "tellUserCommandEnterOrClick": true,
+            "mustNotUseBrowserAutomation": true,
             "fallbackMustNotClaimInspection": true,
             "recoverFreshSignedLinkOnceOnOpenFailure": true
           },
@@ -540,7 +541,7 @@
             "uploadedDomains": "prospeo"
           },
           "when": "before_background_source_scouts",
-          "rule": "Choose the likely primary visible source lane from source intake, brief preference, or the best first lane the main thread will actually search. Send watchNarration with stage find-leads that says what search was tried or is being tried next, what sample is being checked, and why it helps this campaign. Do this before waiting on background scouts so watch mode never sits on only Pick Provider while source work happens elsewhere."
+          "rule": "Choose the likely primary visible source lane from source intake, brief preference, or the best first lane the main thread will actually search. Send watchNarration with stage find-leads that says what search was tried or is being tried next, what sample is being checked, and why it helps this campaign. For Signal Discovery sampling, promote/select the posts with select_promising_posts before fetch_post_engagers so the watched table shows the exact posts being sampled; the guide copy should say Codex is pulling sample engagers from these posts to confirm the ICP is actually engaging and the source is viable. Do this before waiting on background scouts so watch mode never sits on only Pick Provider while source work happens elsewhere."
         },
         {
           "action": "run_first_campaign_attached_source_search",
@@ -744,6 +745,7 @@
           "artifactLinkTiming": "before_next_step_or_revision_question",
           "doNotCompressToSummaryOnly": false,
           "doNotRenderArtifactLinksOnly": true,
+          "sourceRecommendationReadyWatchRule": "When the source recommendation decision card is ready in chat with counts and sample quality, update watchNarration to a find-leads chat-handoff frame. Use a headline like `Review the source in Codex`, body copy that says the browser is showing the evaluated source/results, and nextAction like `Approve in Codex`. Do not keep future-tense copy like `I'll show a source recommendation` after the decision is visible. Include a safety note that no leads import until the user approves the source.",
           "chatRenderRule": "Show a slim rendered-Markdown decision summary only, never a fenced code block. The first sentence must make the decision explicit: 'I recommend {primary source} using {exact filter/source recipe}. The runner-up is {source} because {reason}.' Use indexed sections and short bullets: recommendation, Primary source and filters, Runner-up sources, why it won, Quick numbers with one provider/source angle per bullet, raw volume, sampled fit count as n/N only (no percentages), estimated good-fit range after cleanup, activity/warmth basis, confidence note, 3-5 representative sample leads, and one tradeoff. Do not forecast connection acceptance rates, reply rates, meetings, pipeline, revenue, or ROI unless the user supplied verified benchmark data for this exact workspace/sender. If Signals was searched or considered, include two compact inline Markdown tables before the recommendation is treated as final: Signal keyword lanes with keyword lane, timeframe, posts found, and finalist posts reviewed; and LinkedIn posts sampled with post URL/title, author/topic, age, engagers, sampled engagers, good fits as n/N only, estimated usable prospects per post, and use/discard decision. Default to selecting a few promising Signals posts for the first sample instead of trying to prove full Signals scale up front; if the sample is good but volume is low, say how many more posts to add/scrape next. Do not skip or discard Signals based only on raw post count or vibes; show the post-level math first, or explicitly say no engagers could be fetched and lower confidence. Keep discarded paths, full sample rows, and lead-sample.json details in lead-review.md. Do not show plain filesystem paths unless links cannot be created."
         },
         {
@@ -760,6 +762,7 @@
             "selectedLeadListId stays the source list and workflowTableId is the campaign table"
           ],
           "watchNarrationRule": "Do not include time estimates. Say what review-batch work is happening and what the user will approve next.",
+          "sourceApprovedImportRule": "After source approval, if chat says import is starting, send review-batch watchNarration with current-tense import copy. Headline should be like `Importing the review batch`; body should say the browser is still showing the approved source leads while only the bounded 15-row review batch is imported. Do not use source-approved or future-tense outcome copy once import is starting.",
           "chatRenderRule": "Lead source is set. Next import and confirm only the first 15-row review batch into the campaign table. After workflowTableId exists, run the fit-filter and message-generation workstreams from the campaign table sample. If real parallel MCP/tool branches or host subagents were actually launched, say so; otherwise say the branches will run sequentially. Never claim parallelism unless parallel execution actually started."
         },
         {
@@ -790,6 +793,7 @@
             "leadSourceProvider",
             "providerSearchAssociation",
             "currentStep: primary provider step (signal-discovery, sales-nav, prospeo/contact-search, saved-lists, or leads)",
+            "watchNarration: find-leads source recommendation ready, or review-batch import starting when source approval already happened",
             "selectedLeadListId as source list id only for existing-list or supplied-list preview"
           ],
           "fallback": "Stop if campaignId is missing; the source must be attached to the existing CampaignOffer before import.",
@@ -870,7 +874,8 @@
           "onMissingCampaignAttachedSource": "stop_before_import_and_route_to_find_leads; source scouts must attach searches/selections with campaignOfferId before Step 13"
         },
         {
-          "action": "watch_mode_orient"
+          "action": "watch_mode_orient",
+          "watchNarrationRule": "Before import_leads or confirm_lead_list starts, align the guide with chat by setting review-batch watchNarration to current-tense import copy. Use a headline like `Importing the review batch`; explain that the browser may still show the approved source leads while Codex imports only the bounded 15-row review batch; include a no-launch safety note."
         },
         {
           "tool": "import_leads",
@@ -1039,17 +1044,17 @@
           "fallback": "If real parallel branches are unavailable or the named agents are absent, run filter-leads and then message-generation in the parent thread with product MCP tools/assets. Do not customer-surface agent install status, and do not claim background or parallel work in that fallback."
         },
         {
-          "action": "wait_for_post_lead_artifacts",
+          "action": "wait_for_lead_filter_artifact",
           "requiredArtifacts": [
-            "lead-filter.md",
-            "message-validation.md"
+            "lead-filter.md"
           ],
           "optionalArtifacts": [
             "rubric.json",
+            "message-validation.md",
             "message-prep.md",
             "message-candidate-drafts.md"
           ],
-          "reconciliationRule": "Before entering message-review, verify lead-filter.md and message-validation.md both came from the same brief.md, lead-review.md, and lead-sample.json. lead-filter.md gates the sample rows; lead-sample.json remains the message sample source."
+          "rule": "Do not wait for message-validation.md before saving rubrics and moving the watched browser to Filter Leads. Message work may still be running while the user watches fit filtering."
         },
         {
           "action": "save_filter_rubrics_to_campaign",
@@ -1069,6 +1074,39 @@
           ],
           "writesCampaignState": "leadScoringRubrics",
           "requiredBeforeCascade": true
+        },
+        {
+          "action": "advance_watch_to_filter_leads_after_rubrics_saved",
+          "tool": "update_campaign",
+          "requires": [
+            "campaignId",
+            "workflowTableId",
+            "leadScoringRubrics"
+          ],
+          "requiredValues": {
+            "currentStep": "apply-icp-rubric",
+            "enableICPFilters": true,
+            "watchNarration.stage": "fit-message"
+          },
+          "watchNarrationRule": "Headline should be like `Filtering the review batch`. Body should say the browser is on Filter Leads, Codex saved the fit rules, and the review rows are being checked while the first message sample finishes. Next should point to message review.",
+          "when": "after_save_rubrics_succeeds_before_waiting_for_message_validation",
+          "writesCampaignState": "currentStep:apply-icp-rubric"
+        },
+        {
+          "tool": "get_campaign_navigation_state",
+          "purpose": "confirm the watched UI moved to Filter Leads after rubrics saved",
+          "optional": true
+        },
+        {
+          "action": "wait_for_message_validation_artifact",
+          "requiredArtifacts": [
+            "message-validation.md"
+          ],
+          "optionalArtifacts": [
+            "message-prep.md",
+            "message-candidate-drafts.md"
+          ],
+          "reconciliationRule": "Before entering message-review, verify message-validation.md came from the same brief.md, lead-review.md, lead-sample.json, and saved lead-filter.md. lead-filter.md gates the sample rows; lead-sample.json remains the message sample source."
         }
       ],
       "requiredArtifacts": [
@@ -1090,6 +1128,8 @@
         "get_subskill_asset",
         "get_post_find_leads_scout_registry",
         "save_rubrics",
+        "update_campaign",
+        "get_campaign_navigation_state",
         "Task",
         "spawn_agent",
         "AskUserQuestion",
@@ -1106,7 +1146,6 @@
         "create_campaign",
         "import_leads",
         "confirm_lead_list",
-        "update_campaign",
         "queue_cells",
         "start_campaign",
         "check_rubric",
@@ -1114,7 +1153,7 @@
         "enrich_with_prospeo",
         "bulk_enrich_with_prospeo"
       ],
-      "watchRequired": false,
+      "watchRequired": true,
       "waitFor": [
         "post_lead_workstreams_ready",
         "revise_leads",
@@ -1496,6 +1535,8 @@
           ],
           "requiredValues": {
             "currentStep": "validate-sample",
+            "enableICPFilters": true,
+            "useMessagingTemplate": true,
             "watchNarration.stage": "review-ready"
           },
           "when": "after_update_campaign_brief_succeeds",
@@ -1939,7 +1980,7 @@
         },
         {
           "tool": "wait_for_campaign_table_ready",
-          "purpose": "wait_for_bounded_review_batch_cascade_to_drain"
+          "purpose": "wait_for_review_batch_cascade_to_start_returning_filter_results"
         },
         {
           "tool": "get_rows_minimal",
@@ -1954,11 +1995,12 @@
             "minPassedCount"
           ],
           "targetCountSource": "stats.totalRows_or_imported_batch_count",
-          "minPassedCountSource": "sample.minProjectedPass (3)",
+          "minPassedCountSource": "firstPassingRowForMessageStart (1)",
           "requiredValues": {
-            "includeRows": false
+            "includeRows": false,
+            "minPassedCount": 1
           },
-          "note": "The shell-first flow tests 15 leads first; always pass cohortSize explicitly instead of relying on default 25 behavior. Pass minPassedCount so a 15-row batch with resolved failures can advance when the 3-pass floor is already met.",
+          "note": "The shell-first flow tests 15 leads first; always pass cohortSize explicitly instead of relying on default 25 behavior. Pass minPassedCount=1 so the first passing filtered row unblocks Generate Message observation instead of waiting for every sample row to finish.",
           "readVia": "stats_only_tool_result",
           "extractFields": [
             "ready",
@@ -1975,7 +2017,7 @@
         {
           "action": "handle_partial_or_timeout_sample",
           "when": "wait_for_rubric_results.ready_false_or_reason_timeout",
-          "rule": "Do not repeat waits indefinitely. If active processing is visible, wait once more at most. Otherwise treat returned passRate/stats as a partial sample and stop before Settings with sample_revision_required when passed rows are below minProjectedPass or generated messages are incomplete.",
+          "rule": "Do not repeat waits indefinitely. If at least one row has passed, move to Step 15 to observe or queue Generate Message for passing rows even when other sample rows are still processing. If zero rows have passed and active processing is visible, wait once more at most. Otherwise treat returned passRate/stats as a partial sample and stop before Settings with sample_revision_required.",
           "customerStatus": "sample-needs-revision",
           "showFields": [
             "passRate.completed",
@@ -2024,6 +2066,7 @@
         "revision_round_persists_across_resume",
         "wait_for_rubric_results_never_retain_rows_payload_in_tail_context",
         "wait_for_rubric_results_targetCount_always_explicit",
+        "first_passing_row_unblocks_generate_message_observation",
         "timeout_never_repeats_without_customer_handoff",
         "timeout_or_underfloor_sample_never_advances_to_settings",
         "review_batch_cascade_waits_for_saved_rubrics_and_approved_template"

package/skills/create-campaign-v2/references/sample-validation-loop.md

@@ -9,7 +9,9 @@ on every revision round.
 We spend a bounded review batch (default 15 rows) to prove fit before the
 user spends credits on hundreds more leads. The sample loop has one job:
 answer the question "do we have enough real passing examples for the user to
-judge this campaign?"
+judge this campaign?" Message generation starts earlier: the first row that
+passes filters is enough to begin observing or queueing Generate Message for
+that passing row.
 
 If the answer is yes, proceed to Step 15 messaging for the review batch. If
 the answer is no, diagnose whether the brief is wrong or the list is wrong,
@@ -48,13 +50,16 @@ auto-revise leads.
 
 5. check_rubric(sample)
 
-6. wait_for_rubric_results(sample, targetCount = <cohortSize>)
+6. wait_for_rubric_results(sample, targetCount = <cohortSize>, minPassedCount = 1)
    - cohortSize = stats.totalRows of the enrichment batch, or the
      imported batch count
    - default targetCount=15 matches the default review batch, but pass the
      explicit batch count anyway so future larger expansion batches do not
      accidentally stop early
      (see §Known Tool Behaviors #3)
+   - minPassedCount=1 means one passing filtered row unblocks Step 15
+     Generate Message observation. Do not wait for all sample rows to finish
+     before messages start.
 
 7. call `wait_for_rubric_results` with `includeRows=false`; extract ONLY:
    - ready: boolean
@@ -71,11 +76,13 @@ auto-revise leads.
 8. if `ready=false` and `reason="timeout"`:
    - do NOT keep polling indefinitely
    - treat the returned passRate/stats as a partial sample
+   - if at least one row has passed filters, advance to Step 15 to observe or
+     queue Generate Message for currently passing rows
    - if active processing is visible (`processingCount > 0` or a similar
      running-cell stat), one additional wait is allowed
    - otherwise diagnose the partial sample now
-   - if passed rows are below `sample.minProjectedPass` or generated messages
-     are missing for passing rows, stop before Settings with:
+   - if zero rows have passed and there is no active processing, stop before
+     Settings with:
      `Status: sample-needs-revision`
    - show the concrete numbers: completed, passed, pending, pass percent, and
      message count when available
@@ -89,8 +96,9 @@ auto-revise leads.
    projectedPass      = round(passInSample / sampleSize * importLimit)
 
 10. branch:
-   if projectedPass >= minProjectedPass:
-       proceed to Step 15 (auto-execute-messaging) with this review batch
+   if passInSample >= 1:
+       proceed to Step 15 (auto-execute-messaging) with currently passing rows
+       so Generate Message can start without waiting for the full sample
    else:
        diagnose (see Brief-vs-List Diagnosis below)
        revisionRound += 1
@@ -166,11 +174,12 @@ and partial stats such as 13/15 scored, 2 passing, 2 messages generated. That is
 enough to diagnose an underperforming sample. Waiting again without active
 processing makes the experience feel frozen.
 
-Workaround: treat timeout stats as a partial sample. If the pass count is below
-the configured floor or message generation has not covered the passing rows,
-stop at `Status: sample-needs-revision` before Settings. Show the completed /
-passed / pending counts and ask whether to revise source, revise filter/rubric,
-or wait once only if active processing is still visible.
+Workaround: treat timeout stats as a partial sample. If at least one row has
+passed, move to Step 15 and observe or queue Generate Message for the passing
+rows. If zero rows have passed and no active processing is visible, stop at
+`Status: sample-needs-revision` before Settings. Show the completed / passed /
+pending counts and ask whether to revise source, revise filter/rubric, or wait
+once only if active processing is still visible.
 
 ## Projected Pass Math
 

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

@@ -67,9 +67,9 @@ Signal Discovery:
 ```json
 {
   "stage": "find-leads",
-  "headline": "Testing Signal Discovery",
-  "visibleState": "You are watching Signal Discovery search posts about Claude Code and GTM automation.",
-  "agentIntent": "Codex is sampling engagers to see if they match the founder/operator campaign brief.",
+  "headline": "Testing warm LinkedIn activity",
+  "visibleState": "The promoted posts are the ones being sampled now.",
+  "agentIntent": "Codex is pulling sample engagers from these posts to confirm the ICP is actually engaging and that this source is viable.",
   "nextAction": "Review batch"
 }
 ```
@@ -86,6 +86,24 @@ Search iteration:
 }
 ```
 
+Source recommendation ready:
+
+```json
+{
+  "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."
+}
+```
+
+When the source recommendation, counts, and sample-quality decision are ready in
+chat, update the guide to route the user back to Codex/Claude for approval. Do
+not keep future-tense copy such as `I'll show a source recommendation` once the
+decision card is visible.
+
 Review batch:
 
 ```json
@@ -98,6 +116,24 @@ Review batch:
 }
 ```
 
+Source approved and import starting:
+
+```json
+{
+  "stage": "review-batch",
+  "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."
+}
+```
+
+When chat says the source is approved and import is starting, the guide must use
+current-tense import copy. Do not leave the guide in source-approved or
+future-tense copy such as `I'll show the review-batch outcome`; that makes the
+browser guide describe a different moment than chat.
+
 Fit + message:
 
 ```json

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

@@ -11,12 +11,13 @@ gating, and handoff read campaign state first.
 
 ## Plumbing Reuse
 
-`create_campaign` already returns a safe direct campaign-builder `watchUrl` on
-the response (`CampaignDetail.watchUrl` in
-`mcp/sellable/src/tools/campaigns.ts`). V2 does NOT mint a new token, does NOT call
-a different route, and does NOT construct the URL locally. Capture whatever
-`watchUrl` the existing tool returns and surface it verbatim. The link must
-land on the campaign builder without exposing token secrets in the MCP result.
+`create_campaign` already returns a direct campaign-builder `watchUrl` on the
+response (`CampaignDetail.watchUrl` in `mcp/sellable/src/tools/campaigns.ts`).
+The URL includes the auth token and workspace routing needed for browser
+auto-login, then the app exchanges the token through `/auth/continue` and
+cleans it from the browser URL. V2 does NOT mint a new token, does NOT call a
+different route, and does NOT construct the URL locally. Capture whatever
+`watchUrl` the existing tool returns and surface it verbatim.
 
 ## Shell-First Link
 
@@ -39,6 +40,8 @@ No leads import and nothing sends yet.
 
 Watch link: {watchUrl}
 
+Command-Enter or click that link to watch it in Sellable.
+
 Cool, let's find leads.
 ```
 
@@ -93,7 +96,9 @@ cached or reconstructed URL.
 ## Hard Rules
 
 - Never fabricate or reconstruct the URL locally.
-- The watch link must be a safe direct campaign-builder URL.
+- The watch link must be a direct campaign-builder URL with token auto-login.
+- Do not call browser-opening tools, shell `open`, Computer Use, or in-app
+  browser automation; the user opens the link when they want to watch.
 - Missing `watchUrl` is an error, not a silent skip.
 - The first watch link must be shown only after the v1 brief is on the campaign.
 - A watch link is not approval to import, attach sequence, or start.

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

@@ -20,8 +20,8 @@ Every tail run MUST call these tools in this exact order. The tail is
 **review-batch cascade-driven**: you kick off Enrich Prospect only for
 the imported review batch, and the workflow engine chains DNC Check →
 ICP Score → Passes Rubric → Generate Message automatically. Your job is
-to START the bounded cascade, WAIT for it to drain, OBSERVE the results,
-and stop for review.
+to START the bounded cascade, WAIT until filter results land, OBSERVE message
+generation as soon as one row passes, and stop for review.
 Do NOT manually run rubric-check, enrich, or message-generation
 tools — the cascade already does them.
 
@@ -43,14 +43,16 @@ Post-import main thread
 
 Step 14 — kick bounded cascade + observe sample
   queue_cells(cellIds=<review-batch Enrich Prospect cells only>)  <-- starts bounded chain
-  wait_for_campaign_table_ready    # review-batch cascade drains here
+  wait_for_campaign_table_ready    # wait until review-batch cascade starts returning filter results
   get_rows_minimal                 # read passesRubric + message cell status per row
-  compute projectedPass
-  if OK: update_campaign(currentStep=auto-execute-messaging)
-  else:  diagnose brief-vs-list; if brief: update_campaign_brief + re-queue + wait
+  wait_for_rubric_results(minPassedCount=1, includeRows=false)
+  if at least one row passes: update_campaign(currentStep=auto-execute-messaging)
+  compute projectedPass for later reporting / revision decisions
+  if zero rows pass: diagnose brief-vs-list; if brief: update_campaign_brief + re-queue + wait
   (check_rubric / bulk_enrich_with_prospeo are NOT called here —
    cascade already did them. wait_for_rubric_results is OK as a
-   read-only observation helper if you need to block on completion.)
+   read-only observation helper if you need to block until the first
+   passing filtered row exists.)
 
 Step 15 — observe messaging
   get_rows_minimal                 # confirm passing rows have completed Generate Message cells
@@ -98,9 +100,12 @@ Message` column's http_request writes those cells via the cascade.
 - `wait_for_rubric_results` is read-only and OK to use as an
   observation helper when you need to block on rubric completion —
   it does not mutate cells. Prefer `get_rows_minimal` +
-  `wait_for_campaign_table_ready` for the primary cascade-drain
+  `wait_for_campaign_table_ready` for the primary cascade-observation
   path, but use `wait_for_rubric_results({ targetCount: cohortSize })`
-  when the table-level wait returns before rubric cells finish.
+  when the table-level wait returns before rubric cells finish. In
+  create-campaign-v2 Step 14, pass `minPassedCount: 1`; one passing
+  filtered row is enough to start observing Generate Message, even if
+  other sample rows are still processing.
 - `start_campaign` is FORBIDDEN in the autonomous tail. It belongs only
   in the Claude-greenlight path, AFTER the user signals "start". See
   `references/final-handoff-contract.md`.
@@ -275,9 +280,9 @@ 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
-persisted, Step 14 queues the review-batch Enrich Prospect cells, waits for the
-table cascade to drain, then reads the resulting ICP scores and Passes Rubric
-values. It does NOT call `check_rubric`, `bulk_enrich_with_prospeo`, or any
+persisted, Step 14 queues the review-batch Enrich Prospect cells, waits until
+filter results start landing, then moves to message observation as soon as one
+row passes. It does NOT call `check_rubric`, `bulk_enrich_with_prospeo`, or any
 other direct enrichment/scoring tool.
 
 Shape:
@@ -286,23 +291,23 @@ Shape:
 queue_cells({ tableId: workflowTableId, cellIds: reviewBatchEnrichCellIds })
 wait_for_campaign_table_ready({ tableId: workflowTableId })
 get_rows_minimal({ tableId: workflowTableId })
-wait_for_rubric_results({ tableId: workflowTableId, targetCount: cohortSize, minPassedCount: minProjectedPass, includeRows: false })
+wait_for_rubric_results({ tableId: workflowTableId, targetCount: cohortSize, minPassedCount: 1, includeRows: false })
 passInSample = count of first sampleSize review-batch rows with passesRubric === true
 projectedPass = round(passInSample / sampleSize * importLimit)
 
-if wait_for_rubric_results.ready === true and partial === true and reason === "min_passed_count_met_with_resolved_failures":
-    use the partial passRate/stats as a valid sample diagnostic
-    continue if projectedPass >= minProjectedPass and generated messages are present for the passing rows
+if wait_for_rubric_results.ready === true and passRate.passed >= 1:
+    advance to Step 15 to observe or queue Generate Message for currently passing rows
+    do not wait for every sample row to finish before message generation starts
 else if wait_for_rubric_results.ready === false and reason === "timeout":
     use the partial passRate/stats as the sample diagnostic
-    if active processing is visible:
+    if passRate.passed >= 1:
+        advance to Step 15 to observe/queue Generate Message for passing rows
+    else if active processing is visible:
         wait one more time at most
     else:
         stop before Settings with Status: sample-needs-revision
         show completed, passed, pending, pass percent, and message count when available
         ask whether to revise source, revise filter/rubric, or wait once only if still processing
-else if projectedPass >= minProjectedPass:
-    advance to Step 15
 else:
     diagnose brief-vs-list per sample-validation-loop.md
     - brief: autonomous update_campaign_brief, then re-kick cascade

package/skills/providers/signal-discovery.md

@@ -94,6 +94,8 @@ Use conservative logic:
 1. Start from recent strong-post inventory and sample quality, not raw total post count.
 2. If the lane looks promising, sample real engagers before claiming a reachable-lead estimate:
    - choose 1-2 promising posts
+   - in campaign-attached runs, call `select_promising_posts` first to promote
+     those posts in the watched Signal Discovery UI before sampling engagers
    - call `fetch_post_engagers`
    - fetch only a representative first sample, not a full scrape
    - default to `limit: 25` for one post or `limit: 20` per post when checking two posts
@@ -325,6 +327,11 @@ Select the best posts to scrape AND provide headline ICP criteria.
 Use `selectionTarget` and `recommendedPostIds` returned by `search_signals`
 (default selectionTarget is 3).
 
+For campaign-attached viability sampling, this is also the promote step: call it
+before `fetch_post_engagers` so the user sees the exact posts being sampled in
+the watched Signal Discovery table. Use `selectionMode: "replace"` for the first
+sample set unless the user explicitly wants to add to existing promoted posts.
+
 ```json
 select_promising_posts({
   "campaignOfferId": "cmp_xxx",