@sellable/mcp 0.1.111 → 0.1.113

package/dist/tools/campaigns.d.ts

@@ -9,6 +9,7 @@ declare const LEAD_SOURCE_PROVIDERS: {
 };
 type LeadSourceProvider = (typeof LEAD_SOURCE_PROVIDERS)[keyof typeof LEAD_SOURCE_PROVIDERS];
 export declare function buildWatchUrl(config: Pick<ReturnType<typeof getConfig>, "apiUrl" | "token" | "activeWorkspaceId" | "workspaceId">, path: string): string;
+export declare function getCampaignBuilderWatchModeParam(): "claude" | "codex";
 export interface Campaign {
     id: string;
     name: string;
@@ -124,6 +125,7 @@ export interface CreateCampaignInput {
     campaignBrief?: string;
     messageGenerationMode?: "template" | "ai-generated";
     currentStep?: string | null;
+    watchNarration?: unknown;
     leadSourceType?: string | null;
     leadSourceProvider?: LeadSourceProvider | "apollo" | null;
     selectedLeadListId?: string | null;
@@ -137,6 +139,7 @@ export interface UpdateCampaignInput {
     leadSourceProvider?: LeadSourceProvider | "apollo" | null;
     selectedLeadListId?: string | null;
     currentStep?: string | null;
+    watchNarration?: unknown;
     interactionMode?: InteractionMode;
     enableICPFilters?: boolean | null;
     useMessagingTemplate?: boolean | null;
@@ -165,6 +168,7 @@ export declare const campaignToolDefinitions: ({
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
             currentStep?: undefined;
+            watchNarration?: undefined;
             leadSourceType?: undefined;
             leadSourceProvider?: undefined;
             selectedLeadListId?: undefined;
@@ -200,6 +204,7 @@ export declare const campaignToolDefinitions: ({
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
             currentStep?: undefined;
+            watchNarration?: undefined;
             leadSourceType?: undefined;
             leadSourceProvider?: undefined;
             selectedLeadListId?: undefined;
@@ -278,6 +283,7 @@ export declare const campaignToolDefinitions: ({
             campaignBrief?: undefined;
             messageGenerationMode?: undefined;
             currentStep?: undefined;
+            watchNarration?: undefined;
             leadSourceType?: undefined;
             leadSourceProvider?: undefined;
             selectedLeadListId?: undefined;
@@ -330,6 +336,41 @@ export declare const campaignToolDefinitions: ({
                 type: string[];
                 description: string;
             };
+            watchNarration: {
+                type: string;
+                description: string;
+                properties: {
+                    stage: {
+                        type: string;
+                        enum: string[];
+                    };
+                    headline: {
+                        type: string;
+                    };
+                    visibleState: {
+                        type: string;
+                    };
+                    agentIntent: {
+                        type: string;
+                    };
+                    nextAction: {
+                        type: string[];
+                    };
+                    safety: {
+                        type: string[];
+                    };
+                    progressLabel: {
+                        type: string[];
+                    };
+                    blockedReason: {
+                        type: string[];
+                    };
+                    workerStatuses: {
+                        type: string;
+                    };
+                };
+                required: string[];
+            };
             leadSourceType: {
                 type: string[];
                 description: string;
@@ -399,6 +440,41 @@ export declare const campaignToolDefinitions: ({
                 type: string[];
                 description: string;
             };
+            watchNarration: {
+                type: string;
+                description: string;
+                properties: {
+                    stage: {
+                        type: string;
+                        enum: string[];
+                    };
+                    headline: {
+                        type: string;
+                    };
+                    visibleState: {
+                        type: string;
+                    };
+                    agentIntent: {
+                        type: string;
+                    };
+                    nextAction: {
+                        type: string[];
+                    };
+                    safety: {
+                        type: string[];
+                    };
+                    progressLabel: {
+                        type: string[];
+                    };
+                    blockedReason: {
+                        type: string[];
+                    };
+                    workerStatuses: {
+                        type: string;
+                    };
+                };
+                required: string[];
+            };
             interactionMode: {
                 type: string;
                 enum: string[];
@@ -466,6 +542,7 @@ export declare const campaignToolDefinitions: ({
             offerPositioning?: undefined;
             messageGenerationMode?: undefined;
             currentStep?: undefined;
+            watchNarration?: undefined;
             leadSourceType?: undefined;
             leadSourceProvider?: undefined;
             selectedLeadListId?: undefined;

package/dist/tools/campaigns.js

@@ -27,6 +27,15 @@ export function buildWatchUrl(config, path) {
     }
     return url.toString();
 }
+export function getCampaignBuilderWatchModeParam() {
+    const explicit = process.env.SELLABLE_WATCH_MODE_DRIVER?.trim().toLowerCase();
+    if (explicit === "claude" || explicit === "codex")
+        return explicit;
+    return process.env.CODEX_HOME ? "codex" : "claude";
+}
+function buildCampaignBuilderWatchPath(campaignId) {
+    return `/campaign-builder/${campaignId}?mode=${getCampaignBuilderWatchModeParam()}`;
+}
 function isLinkedInProfileUrl(input) {
     try {
         const url = new URL(input);
@@ -176,6 +185,31 @@ export const campaignToolDefinitions = [
                     type: ["string", "null"],
                     description: "Workflow step ID (headless or UI step ID such as filter-rules)",
                 },
+                watchNarration: {
+                    type: "object",
+                    description: "Single structured watch-guide narration object to send with currentStep changes. Include stage, headline, visibleState, agentIntent, and nextAction so the browser guide mirrors Codex progress.",
+                    properties: {
+                        stage: {
+                            type: "string",
+                            enum: [
+                                "brief-review",
+                                "find-leads",
+                                "review-batch",
+                                "fit-message",
+                                "review-ready",
+                            ],
+                        },
+                        headline: { type: "string" },
+                        visibleState: { type: "string" },
+                        agentIntent: { type: "string" },
+                        nextAction: { type: ["string", "null"] },
+                        safety: { type: ["string", "null"] },
+                        progressLabel: { type: ["string", "null"] },
+                        blockedReason: { type: ["string", "null"] },
+                        workerStatuses: { type: "object" },
+                    },
+                    required: ["stage", "headline", "visibleState", "agentIntent"],
+                },
                 leadSourceType: {
                     type: ["string", "null"],
                     description: "Lead source type (existing | new)",
@@ -244,10 +278,35 @@ export const campaignToolDefinitions = [
                     type: ["string", "null"],
                     description: "Headless workflow step ID",
                 },
+                watchNarration: {
+                    type: "object",
+                    description: "Single structured watch-guide narration object to send with currentStep changes. Include stage, headline, visibleState, agentIntent, and nextAction so the browser guide mirrors Codex progress. Do not send separate guideHeadline/guideBody fields.",
+                    properties: {
+                        stage: {
+                            type: "string",
+                            enum: [
+                                "brief-review",
+                                "find-leads",
+                                "review-batch",
+                                "fit-message",
+                                "review-ready",
+                            ],
+                        },
+                        headline: { type: "string" },
+                        visibleState: { type: "string" },
+                        agentIntent: { type: "string" },
+                        nextAction: { type: ["string", "null"] },
+                        safety: { type: ["string", "null"] },
+                        progressLabel: { type: ["string", "null"] },
+                        blockedReason: { type: ["string", "null"] },
+                        workerStatuses: { type: "object" },
+                    },
+                    required: ["stage", "headline", "visibleState", "agentIntent"],
+                },
                 interactionMode: {
                     type: "string",
                     enum: ["step-by-step", "autonomous", "ask-when-needed"],
-                    description: "Execution style for lead sourcing steps (step-by-step | autonomous | ask-when-needed).",
+                    description: "Execution style for Find Leads steps (step-by-step | autonomous | ask-when-needed).",
                 },
                 enableICPFilters: {
                     type: ["boolean", "null"],
@@ -335,7 +394,7 @@ export async function getCampaign(campaignId) {
         api.get(`/api/v3/mcp/campaigns/${campaignId}`),
         fetchCampaignRubrics(campaignId).catch(() => null),
     ]);
-    const watchUrl = buildWatchUrl(config, `/campaign-builder/${campaignId}?mode=claude`);
+    const watchUrl = buildWatchUrl(config, buildCampaignBuilderWatchPath(campaignId));
     // Merge rubrics into campaignOffer
     const rubrics = (rubricsResult?.rubrics || []).map((r) => ({
         id: r.id || "",
@@ -590,7 +649,7 @@ export async function createCampaign(input) {
     // Idempotent resume path
     if (input.campaignId) {
         const existing = await api.get(`/api/v2/campaign-offers/${input.campaignId}`);
-        const watchUrl = buildWatchUrl(config, `/campaign-builder/${existing.id}?mode=claude`);
+        const watchUrl = buildWatchUrl(config, buildCampaignBuilderWatchPath(existing.id));
         const hasCreateFields = input.name ||
             input.clientProspectId ||
             input.offerPositioning !== undefined ||
@@ -708,7 +767,7 @@ export async function createCampaign(input) {
         },
     };
     const result = await api.post(`/api/v2/campaign-offers`, formattedInput);
-    const watchUrl = buildWatchUrl(config, `/campaign-builder/${result.id}?mode=claude`);
+    const watchUrl = buildWatchUrl(config, buildCampaignBuilderWatchPath(result.id));
     // Serialize to only essential fields for context efficiency
     return {
         id: result.id,

package/dist/tools/navigation.js

@@ -415,8 +415,8 @@ function parseWatchUrl(watchUrl, campaignId) {
             direct: false,
             redirectPath: decodedRedirect,
             warning: isLegacySigned
-                ? "Watch URL still uses a tokenized /auth/continue handoff. Return the safe direct /campaign-builder/{campaignId}?mode=claude watch URL instead."
-                : "Watch URL is not a safe direct /campaign-builder/{campaignId}?mode=claude watch link.",
+                ? "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.",
         };
     }
     catch {

package/dist/tools/rubrics.js

@@ -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/package.json

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

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

@@ -165,7 +165,7 @@ Optional debug/UAT draft directory, disabled in normal customer runs:
   ask in chat only when the run is explicitly a non-interactive smoke/rehearsal.
 
 - Customer-facing progress updates must use product language. Say "quick
-  setup choices", "campaign brief", "lead sourcing", and "approval" instead of
+  setup choices", "campaign brief", "Find Leads", and "approval" instead of
   `request_user_input`, Default mode, MCP namespaces, plugin caches, prompt
   loading, runbooks, local skill files, skill versions, npm/package details,
   repo-local files, VPS/off-desktop/browser automation limitations, or
@@ -181,6 +181,15 @@ Optional debug/UAT draft directory, disabled in normal customer runs:
   or safe launch. Do not say "persist", "local draft folder", "artifact",
   "mkdir", "campaign thesis", or "same approved campaign thesis" in
   customer-facing progress copy.
+- Watch guide copy must use the single `watchNarration` object whenever you set
+  `currentStep` or report visible progress in a watched run. Read
+  `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. 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:`
@@ -401,7 +410,7 @@ Optional debug/UAT draft directory, disabled in normal customer runs:
   `RevOps`, `outbound systems`, or `pipeline architecture` unless they are
   translated into what the user can understand.
 
-  After rendering that brief, ask for brief approval before lead sourcing in
+  After rendering that brief, ask for brief approval before Find Leads in
   hosted net-new runs. The user-facing choice should be approve/revise language,
   not "looks good".
   Approval options should refer to what the user just read, e.g. `Approve this
@@ -422,16 +431,15 @@ brief`, `Revise target`, `Revise offer/proof`, and `Other / custom`.
 
   The approval question can be based on the rendered brief in chat and the live
   campaign brief. Do not wait for file-write chrome before asking for approval.
-  Before lead sourcing, call `update_campaign({ campaignId, campaignBrief,
-  currentStep: "pick-provider" })` after approval so the watch link moves out of
-  Plan while the main thread compares source paths.
+  Before Find Leads, call `update_campaign({ campaignId, campaignBrief,
+  currentStep: "pick-provider", watchNarration: { ... } })` after approval so
+  the watch link moves out of Plan while the main thread compares source paths.
 
 - After the brief is approved, show the next progress line:
   `Cool. Now I'm going to find people who are both a good fit and active enough
 to be worth a LinkedIn test. I'll compare source paths by expected volume,
 sampled ICP fit, activity/warmth signal, cleanup risk, and tradeoffs. This
-usually takes ~3-5 min, and I'll show you the source decision + sample before
-anything goes live.`
+will end with a source decision + sample before anything goes live.`
 - In watch mode, do not leave the user sitting on only `pick-provider` while
   source scouts run. Move the campaign to the likely primary source lane
   (`signal-discovery`, `sales-nav`, or `prospeo`) before background source
@@ -447,9 +455,8 @@ message we should test.`
 - During long post-intake work, show concise progress checkpoints before the
   next expensive stage: source being checked, source switch/tradeoff if any,
   lead sample usable, filter/message drafting, and message-review rule loading.
-  Each checkpoint should include a rough remaining time when useful. If a step
-  exceeds its estimate by roughly a minute or more, acknowledge it lightly once
-  and explain why the extra care helps the campaign. Example:
+  Each checkpoint should say what changed, what is being checked next, and why
+  that matters for the campaign. Do not invent remaining-time estimates. Example:
 
   ```text
   This is taking a little longer than I expected, sorry. I’m being careful here
@@ -575,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.
@@ -623,7 +645,7 @@ workstreams`, `in parallel`, or `background` unless parallel branches were
 There are four customer-visible gates in the net-new hosted flow:
 
 - `brief-review` asks whether to approve the rendered campaign brief before
-  lead sourcing starts. Do not skip this by inferring approval from setup
+  Find Leads starts. Do not skip this by inferring approval from setup
   answers.
 - `lead-review` / source decision asks whether to approve the selected source
   path and sample before moving into filter/message work. Do not skip this by

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

@@ -1,12 +1,12 @@
 {
   "version": "v2",
   "workflow": "create-campaign-v2",
-  "principle": "CampaignOffer state and the watch link are canonical from the first brief onward. Disk artifacts are optional debug/UAT diagnostics, not the normal customer surface. Resume, gating, and handoff read campaign state first. Start from user intake, create a watchable campaign shell with a v1 brief, update currentStep before major visible work, attach source/search state to that CampaignOffer, import the bounded review batch before post-import fit/message scouts, save rubrics and an approved message template, then queue the 15-row cascade and hand off to settings/sequence/start.",
+  "principle": "CampaignOffer state and the watch link are canonical from the first brief onward. Disk artifacts are optional debug/UAT diagnostics, not the normal customer surface. Resume, gating, and handoff read campaign state first. Start from user intake, create a watchable campaign shell with a v1 brief, update currentStep and watchNarration before major visible work, attach source/search state to that CampaignOffer, import the bounded review batch before post-import fit/message scouts, save rubrics and an approved message template, then queue the 15-row cascade and hand off to settings/sequence/start.",
   "artifactPolicy": {
     "normalCustomerPath": "Use CampaignOffer state, MCP responses, provider search state, and campaign table rows. Do not create, read, link, or surface local draft files unless debug/UAT mode is explicit or the user asks for them.",
     "debugArtifactsAreOptional": true,
     "requiredArtifactsApplyWhen": "legacy resume, fixture validation, or explicit debug/UAT mode only",
-    "customerFacingAccess": "Watch link and live campaign currentStep"
+    "customerFacingAccess": "Watch link, live campaign currentStep, and concise watchNarration"
   },
   "commitGateChoices": [
     "approve",
@@ -225,9 +225,6 @@
             "watch the draft campaign as it fills in",
             "no leads import and nothing sends yet"
           ],
-          "timeEstimates": {
-            "campaignBrief": "~1-2 min"
-          },
           "forbiddenWording": [
             "brief.md",
             "lead-review.md",
@@ -279,10 +276,12 @@
             "name",
             "campaignBrief",
             "clientProspectId or senderLinkedinUrl",
-            "currentStep"
+            "currentStep",
+            "watchNarration"
           ],
           "requiredValues": {
-            "currentStep": "create-offer"
+            "currentStep": "create-offer",
+            "watchNarration.stage": "brief-review"
           },
           "briefMode": "v1 campaign brief shown to the user; not an empty placeholder",
           "capture": [
@@ -306,7 +305,8 @@
             "campaignId",
             "watchUrl",
             "campaignBrief",
-            "currentStep:create-offer"
+            "currentStep:create-offer",
+            "watchNarration: brief-review with approve-the-brief guidance"
           ]
         },
         {
@@ -330,7 +330,7 @@
             "campaignBrief"
           ],
           "watchUrlSource": "create_campaign.watchUrl",
-          "requiredWatchUrlShape": "direct /campaign-builder/{campaignId}?mode=claude watch URL",
+          "requiredWatchUrlShape": "direct /campaign-builder/{campaignId}?mode={claude|codex} watch URL",
           "codexBrowserHandoff": {
             "openWhenAvailable": true,
             "inspectBeforeContinuing": true,
@@ -444,7 +444,7 @@
           ],
           "debugOrUatOnly": true,
           "requiredBeforeTransition": false,
-          "reconcileRule": "If debug/UAT artifacts are enabled, verify the sidecar persisted the same brief shown in chat. Normal customer lead sourcing reads CampaignOffer.campaignBrief, not brief.md.",
+          "reconcileRule": "If debug/UAT artifacts are enabled, verify the sidecar persisted the same brief shown in chat. Normal customer Find Leads work reads CampaignOffer.campaignBrief, not brief.md.",
           "chatRenderRule": "Do not block the brief approval question or find-leads transition on this step. Only mention artifact persistence if debug/UAT mode fails or the user asks."
         },
         {
@@ -457,7 +457,8 @@
           "when": "after_user_brief_confirmed_or_auto_continue",
           "fields": [
             "campaignBrief",
-            "currentStep:pick-provider"
+            "currentStep:pick-provider",
+            "watchNarration: find-leads with the first provider/lane being tested"
           ],
           "fallback": "If campaignId is missing from CampaignOffer state, stop; shell-first flow requires an existing campaign before sourcing leads.",
           "readsCampaignStateFirst": true,
@@ -512,20 +513,23 @@
           "tool": "update_campaign",
           "requiredFields": [
             "campaignId",
-            "currentStep"
+            "currentStep",
+            "watchNarration"
           ],
           "requiredValues": {
-            "currentStep": "pick-provider"
+            "currentStep": "pick-provider",
+            "watchNarration.stage": "find-leads"
           },
           "when": "before_source_scouts_or_provider_search",
-          "chatRenderRule": "Move the campaign watch view to Find Contacts before the main thread starts comparing source paths. Do not mention MCP or local artifacts."
+          "chatRenderRule": "Move the campaign watch view to Find Leads before the main thread starts comparing source paths. The watchNarration headline/body must name the likely provider or lane being tested and why it fits this campaign. Do not mention MCP or local artifacts."
         },
         {
           "action": "advance_watch_to_initial_source_lane",
           "tool": "update_campaign",
           "requiredFields": [
             "campaignId",
-            "currentStep"
+            "currentStep",
+            "watchNarration"
           ],
           "currentStepByPrimaryLane": {
             "signals": "signal-discovery",
@@ -536,7 +540,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. 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. 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",
@@ -565,7 +569,7 @@
             "source decision + sample",
             "no import or enrichment yet"
           ],
-          "timeEstimate": "~3-5 min"
+          "watchNarrationRule": "Do not include time estimates. Use current, campaign-specific search reasoning instead."
         },
         {
           "action": "read_optional_source_intake",
@@ -740,6 +744,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."
         },
         {
@@ -755,7 +760,8 @@
             "import the first 15-row review batch before fit/message work",
             "selectedLeadListId stays the source list and workflowTableId is the campaign table"
           ],
-          "timeEstimate": "~2-3 min",
+          "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."
         },
         {
@@ -786,6 +792,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.",
@@ -866,7 +873,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",
@@ -929,10 +937,12 @@
           "tool": "update_campaign",
           "requiredFields": [
             "campaignId",
-            "currentStep"
+            "currentStep",
+            "watchNarration"
           ],
           "requiredValues": {
-            "currentStep": "filter-choice"
+            "currentStep": "filter-choice",
+            "watchNarration.stage": "fit-message"
           }
         }
       ],
@@ -1033,17 +1043,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",
@@ -1063,6 +1073,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": [
@@ -1084,6 +1127,8 @@
         "get_subskill_asset",
         "get_post_find_leads_scout_registry",
         "save_rubrics",
+        "update_campaign",
+        "get_campaign_navigation_state",
         "Task",
         "spawn_agent",
         "AskUserQuestion",
@@ -1100,7 +1145,6 @@
         "create_campaign",
         "import_leads",
         "confirm_lead_list",
-        "update_campaign",
         "queue_cells",
         "start_campaign",
         "check_rubric",
@@ -1108,7 +1152,7 @@
         "enrich_with_prospeo",
         "bulk_enrich_with_prospeo"
       ],
-      "watchRequired": false,
+      "watchRequired": true,
       "waitFor": [
         "post_lead_workstreams_ready",
         "revise_leads",
@@ -1489,7 +1533,10 @@
             "message-review-decision.md"
           ],
           "requiredValues": {
-            "currentStep": "validate-sample"
+            "currentStep": "validate-sample",
+            "enableICPFilters": true,
+            "useMessagingTemplate": true,
+            "watchNarration.stage": "review-ready"
           },
           "when": "after_update_campaign_brief_succeeds",
           "requiredBeforeCascade": true,
@@ -1846,7 +1893,7 @@
             "Campaign created",
             "approved brief",
             "Open this to watch",
-            "lead sourcing",
+            "Find Leads",
             "rubric scoring",
             "messaging populate live",
             "Watch link:"
@@ -1932,7 +1979,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",
@@ -1947,11 +1994,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",
@@ -1968,7 +2016,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",
@@ -2017,6 +2065,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"
@@ -2118,10 +2167,12 @@
           "tool": "update_campaign",
           "requiredFields": [
             "campaignId",
-            "currentStep"
+            "currentStep",
+            "watchNarration"
           ],
           "requiredValues": {
-            "currentStep": "awaiting-user-greenlight"
+            "currentStep": "awaiting-user-greenlight",
+            "watchNarration.stage": "review-ready"
           }
         }
       ],
@@ -2188,7 +2239,7 @@
         },
         {
           "action": "surface_sender_and_slack_handoff",
-          "settingsUrlPattern": "/campaign-builder/{campaignId}/settings?mode=claude",
+          "settingsUrlPattern": "/campaign-builder/{campaignId}/settings?mode={claude|codex}",
           "requiredVisibleContent": [
             "connect or select a LinkedIn sender",
             "Slack reply review",

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

@@ -0,0 +1,177 @@
+# Watch Guide Narration
+
+Use one `watchNarration` object whenever you set `currentStep` or report visible
+progress in a watched create-campaign run. Do not add separate guide headline or
+body args.
+
+## Render
+
+```text
+Building campaign with {Claude Code or Codex}               [Exit watch mode]
+[progress bar]  {stage label} · Step {n} of 5
+
+{headline}
+{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`.
+
+## Copy Rules
+
+- One primary user action per frame.
+- Headline under 8 words.
+- Body is 1-2 short sentences total.
+- Say where the user acts: usually `in Claude Code`, `in Codex`, or `in chat`,
+  matching the host that created the watch URL.
+- `Find Leads` is only the static progress label. The copy must name the active
+  lane/provider and campaign strategy: Signal Discovery, Sales Nav, Prospeo,
+  Apollo, or existing list.
+- During search iteration, say what you tried, what you are trying next, what
+  sample you are checking, and why that helps this campaign.
+- Avoid internal terms: MCP, tool, currentStep, workflow table, scout, debug.
+- Do not invent time estimates.
+
+## Stages
+
+| stage          | UI label      | Next          |
+| -------------- | ------------- | ------------- |
+| `brief-review` | Brief review  | Find Leads    |
+| `find-leads`   | Find Leads    | Review batch  |
+| `review-batch` | Review batch  | Fit + message |
+| `fit-message`  | Fit + message | Review ready  |
+| `review-ready` | Review ready  | Validation    |
+
+## Examples
+
+Brief review:
+
+```json
+{
+  "stage": "brief-review",
+  "headline": "Approve the brief in Codex",
+  "visibleState": "This page is a live preview of the campaign brief.",
+  "agentIntent": "Ask for changes in chat if anything looks off.",
+  "nextAction": "Find Leads"
+}
+```
+
+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.",
+  "nextAction": "Review batch"
+}
+```
+
+Search iteration:
+
+```json
+{
+  "stage": "find-leads",
+  "headline": "Tightening the search",
+  "visibleState": "The first Signal Discovery search was broad, so Codex is trying a narrower Claude Code founder lane.",
+  "agentIntent": "It is sampling a few engagers before importing so the review batch stays on-brief.",
+  "nextAction": "Review batch"
+}
+```
+
+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
+{
+  "stage": "review-batch",
+  "headline": "Preparing your review batch",
+  "visibleState": "This page shows the leads Codex selected for review.",
+  "agentIntent": "Codex is preparing the first campaign batch from those leads.",
+  "nextAction": "Fit + message"
+}
+```
+
+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
+{
+  "stage": "fit-message",
+  "headline": "Building fit and message",
+  "visibleState": "Codex is preparing the campaign's fit rules and first message sample.",
+  "agentIntent": "It is checking who should receive this campaign and what the first offer should say.",
+  "nextAction": "Review ready",
+  "workerStatuses": {
+    "leadFitBuilder": "running",
+    "messageDraftBuilder": "running"
+  }
+}
+```
+
+Review ready:
+
+```json
+{
+  "stage": "review-ready",
+  "headline": "Review fit and message",
+  "visibleState": "The fit rules and message sample are ready.",
+  "agentIntent": "Approve them or ask for changes in chat.",
+  "nextAction": "Validation",
+  "safety": "Codex will only continue after you approve."
+}
+```
+
+Blocked/recovering:
+
+```json
+{
+  "stage": "review-batch",
+  "headline": "Fixing the review batch",
+  "visibleState": "The browser is not showing the campaign batch yet.",
+  "agentIntent": "Codex is reconnecting the campaign state before moving forward.",
+  "nextAction": "Fit + message",
+  "blockedReason": "Campaign batch is not ready yet."
+}
+```

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

@@ -45,7 +45,7 @@ Cool, let's find leads.
 Atomic-mint legacy orientation:
 
 ```text
-Open this to watch lead sourcing, rubric scoring, and messaging populate live.
+Open this to watch Find Leads, rubric scoring, and messaging populate live.
 ```
 
 The exact wording may be adapted for tone, but the copy must make three things

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