@sellable/mcp 0.1.153 → 0.1.155

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

@@ -1,7 +1,7 @@
 {
   "version": "v2.1-compact",
   "workflow": "create-campaign-v2",
-  "principle": "CampaignOffer state and watch link are canonical. Create the watched shell, approve source, materialize and confirm the source list, process the first 15 review rows, save rubrics for approval, approve the message template, then run the bounded filter/message cascade before Settings, sequence, and explicit start.",
+  "principle": "CampaignOffer state and watch link are canonical. Create the watched shell, approve source, materialize and confirm the source list, internally process the first campaign-table execution slice, save rubrics for approval, approve the message template, then run the bounded filter/message cascade before Settings, sequence, and explicit start.",
   "normalCustomerPath": "Use campaign state, MCP responses, and concise watchNarration. Do not create, read, link, or surface local draft files.",
   "legacyCompatibility": {
     "validationSubskill": "create-campaign-v2-validation",
@@ -22,6 +22,7 @@
     "campaignBrief",
     "currentStep",
     "watchNarration",
+    "interactionMode",
     "providerSearchAssociation",
     "selectedLeadListId",
     "workflowTableId",
@@ -78,6 +79,40 @@
     "Do not call start_campaign until the user explicitly confirms launch.",
     "Do not use local files as durable state in normal customer runs."
   ],
+  "yoloMode": {
+    "triggerPhrases": [
+      "yolo",
+      "--yolo",
+      "mode=yolo",
+      "autopilot",
+      "use best guesses",
+      "use best estimates",
+      "answer for me",
+      "just run it"
+    ],
+    "identityRequestOnlyWhenMissing": true,
+    "operatorDirectionsRule": "Treat freeform directions supplied at invocation or later as durable operator directions; newest conflicting direction wins.",
+    "setInteractionModeAfterCampaignCreate": "autonomous",
+    "autoSelectsPreLaunchChoices": [
+      "campaign focus",
+      "brief approval",
+      "source scouting plan",
+      "source review/import approval",
+      "filters vs skip filters",
+      "filter rubric approval",
+      "message template approval when recommendation is approve-message",
+      "generated message review when quality floor passes",
+      "sender selection when exactly one connected sender is safe"
+    ],
+    "mustPauseFor": [
+      "missing campaign identity",
+      "missing credentials or required data",
+      "ambiguous choice with no reasonable estimate",
+      "source/message/filter quality floor failure",
+      "final live launch confirmation"
+    ],
+    "neverAutoStart": true
+  },
   "steps": [
     {
       "id": "bootstrap",
@@ -156,7 +191,23 @@
           "uses": "request_user_input",
           "singleChoice": true,
           "requiredOption": "Other / custom",
-          "neverCollectOpenTextWithStructuredQuestion": true
+          "neverCollectOpenTextWithStructuredQuestion": true,
+          "skipIf": "yolo_mode with any reasonable best-estimate focus"
+        },
+        {
+          "action": "infer_strategy_packet_in_yolo_mode",
+          "when": "yolo_mode",
+          "skipStructuredSetupQuestions": true,
+          "inferFields": [
+            "buyer segment",
+            "offer/CTA",
+            "proof to use or avoid",
+            "lead source",
+            "filter choice",
+            "message direction"
+          ],
+          "sourceOfTruth": "identity/company lookup plus operator directions",
+          "mustStateAssumptionsInBrief": true
         },
         {
           "action": "create_watchable_campaign_shell_with_v1_brief",
@@ -231,7 +282,8 @@
         {
           "action": "ask_brief_choice",
           "uses": "request_user_input",
-          "choices": ["Approve brief", "Revise brief", "Pause here"]
+          "choices": ["Approve brief", "Revise brief", "Pause here"],
+          "skipIf": "yolo_mode; auto_continue after rendering assumptions unless brief quality floor fails"
         }
       ],
       "requiredCampaignState": [
@@ -283,7 +335,12 @@
             "fallback lane if the first lane is weak",
             "what approval authorizes"
           ],
-          "approvalAuthorizes": "source scouting/search only; no import/send"
+          "approvalAuthorizes": "source scouting/search only; no import/send",
+          "yoloMode": {
+            "autoApproveRecommendedLane": true,
+            "mustShowAssumedChoice": true,
+            "pauseIfConfidenceLow": true
+          }
         },
         "defaultWhenSourceUnspecified": [
           "signal-discovery",
@@ -325,7 +382,7 @@
           "action": "show_pre_scout_source_recommendation",
           "uses": "request_user_input",
           "oneShot": true,
-          "skipIf": "approved or leadSourceProvider",
+          "skipIf": "approved or leadSourceProvider or yolo_mode auto-selected source_lane_approved",
           "requiredBeforeTools": [
             "get_provider_prompt",
             "search_signals",
@@ -437,7 +494,7 @@
             "specific source action awaiting approval",
             "for Signal Discovery: compact Source Recommendation with target, raw-engager math, selected-post table, review checkpoint, estimated fit, and fallback",
             "for Signal Discovery: selected post count and target engager/source-candidate volume",
-            "15-row review/process sample size",
+            "internal campaign-table execution slice size, clearly separate from source sampling",
             "runner-up and why it lost",
             "raw volume",
             "sampled people",
@@ -470,7 +527,8 @@
             ],
             "requiredNextActionAfterApproval": "ack once; call import_leads immediately",
             "signalDiscoveryNextTool": "import_leads({ provider: \"signal-discovery\", targetEngagerCount, maxPostsToScrape, confirmed: true })"
-          }
+          },
+          "autoSelectIf": "yolo_mode and projected usable pool clears the source quality floor"
         }
       ],
       "requiredCampaignState": [
@@ -615,7 +673,8 @@
         {
           "action": "ask_filter_choice",
           "uses": "request_user_input",
-          "choices": ["Use filters", "Skip filters", "Revise source"]
+          "choices": ["Use filters", "Skip filters", "Revise source"],
+          "autoSelectIf": "yolo_mode; choose filters unless source is tightly curated or user directed otherwise"
         }
       ],
       "hardRules": [
@@ -729,7 +788,8 @@
           "action": "ask_filter_rubric_review_choice",
           "uses": "request_user_input",
           "choices": ["Approve filters", "Revise filters", "Pause"],
-          "purpose": "let the user read saved rubrics before Filter Leads or enrichment"
+          "purpose": "let the user read saved rubrics before Filter Leads or enrichment",
+          "autoSelectIf": "yolo_mode and rubrics are production-shaped"
         }
       ],
       "requiredCampaignState": [
@@ -809,7 +869,8 @@
         {
           "action": "ask_filter_rubric_review_choice",
           "uses": "request_user_input",
-          "choices": ["Approve filters", "Revise filters", "Pause"]
+          "choices": ["Approve filters", "Revise filters", "Pause"],
+          "autoSelectIf": "yolo_mode and rubrics are production-shaped"
         }
       ],
       "requiredCampaignState": ["campaignId", "workflowTableId"],
@@ -862,7 +923,7 @@
             "run background post-find-leads-message-scout when available",
             "get_subskill_prompt({ subskillName: \"generate-messages\", offset, limit }) until hasMore=false"
           ],
-          "stateSource": "campaignBrief, source, selectedLeadListId, workflowTableId, review-batch row ids/hash",
+          "stateSource": "campaignBrief, source, selectedLeadListId, workflowTableId, execution-slice row ids/hash",
           "outputState": "messageDraftRecommendation"
         }
       ],
@@ -884,7 +945,7 @@
         "Run post-find-leads-message-scout when available; otherwise parent fallback must load get_subskill_prompt({ subskillName: \"generate-messages\" }) from live state.",
         "brief.md, lead-review.md, and lead-sample.json are optional debug context only.",
         "messageDraftRecommendation returns templateRecommendation, tokenFillRules, renderedSample, concerns, status, basisToken, outputAt, outputHash, and error/retry detail.",
-        "If campaign/source/table/review-batch basis does not match, classify the output stale or blocked."
+        "If campaign/source/table/execution-slice basis does not match, classify the output stale or blocked."
       ],
       "doNotAllow": [
         "create_campaign",
@@ -947,7 +1008,8 @@
         {
           "action": "ask_message_review_choice",
           "uses": "request_user_input",
-          "choices": ["approve-message", "revise-messaging"]
+          "choices": ["approve-message", "revise-messaging"],
+          "autoSelectIf": "yolo_mode and Recommendation is approve-message; revise autonomously when Recommendation is revise-messaging"
         },
         {
           "action": "sync_approved_message_set_to_campaign_brief",
@@ -990,7 +1052,7 @@
     },
     {
       "id": "validate-sample",
-      "label": "Validate first review/process sample",
+      "label": "Validate campaign-table execution slice",
       "currentStepValue": "apply-icp-rubric",
       "reference": "references/sample-validation-loop.md",
       "visibleStepRule": "Filter Leads is reached only after saved-filter approval. On approve-message, save the template, refresh apply-icp-rubric narration, then queue bounded Enrich Prospect cells.",
@@ -1006,7 +1068,7 @@
         },
         {
           "tool": "queue_cells",
-          "purpose": "queue ICP/enrichment cells for the first 15 review/process rows only",
+          "purpose": "queue ICP/enrichment cells for the internal campaign-table execution slice only",
           "requiredFields": [
             "workflowTableId",
             "reviewBatchRowIds",
@@ -1086,7 +1148,7 @@
     },
     {
       "id": "auto-execute-messaging",
-      "label": "Generate review-batch messages",
+      "label": "Generate initial campaign-row messages",
       "currentStepValue": "auto-execute-messaging",
       "references": [
         "references/parallel-critique-protocol.md",
@@ -1163,7 +1225,8 @@
             "Revise filters",
             "Revise message template",
             "Pause here"
-          ]
+          ],
+          "autoSelectIf": "yolo_mode and the first passing generated message clears the quality floor"
         }
       ],
       "allowedTools": [
@@ -1238,7 +1301,8 @@
             "Use this connected sender",
             "Connect a different sender in Settings",
             "Pause here"
-          ]
+          ],
+          "autoSelectIf": "yolo_mode and exactly one safe connected sender is available"
         },
         {
           "action": "attach_selected_sender",
@@ -1266,7 +1330,8 @@
           "uses": "request_user_input",
           "singleChoice": true,
           "choices": ["Start campaign", "Review campaign first", "Pause here"],
-          "onUserStart": "claude-greenlight"
+          "onUserStart": "claude-greenlight",
+          "neverAutoSelectInYolo": true
         }
       ],
       "allowedTools": [

package/skills/create-campaign-v2/core/policy.md

@@ -71,7 +71,7 @@ Revision choices route back to the exact upstream stage:
 
 ## 6) Post-Message Tail
 
-After message approval, queue only the first review/process sample cells needed to move
+After message approval, queue only the initial campaign-table execution-slice cells needed to move
 the watched app through enrichment, ICP filtering, and approved-template message
 generation. Keep the tail observable through watch narration.
 

package/skills/create-campaign-v2/references/approval-gate-framing.md

@@ -49,8 +49,8 @@ gate; route back to message generation.
 the user intentionally supplied a source. If present, the approval packet must
 summarize the source type, input mode, supplied profile/domain/list count,
 sampled count, what will be materialized after approval, and that only the
-review batch will be enriched/messaged before greenlight.
-Use the phrase "only the review batch" plainly enough that the operator
+initial campaign rows will be enriched/messaged before greenlight.
+Use the phrase "only the initial campaign rows" plainly enough that the operator
 understands approval is not permission to process the full supplied source.
 
 If any required artifact is missing, do NOT show the gate. Route back to the

package/skills/create-campaign-v2/references/filter-leads.md

@@ -21,7 +21,7 @@ Use only live campaign inputs supplied by the parent thread or scoped MCP tools:
 - campaign brief content
 - approved source decision and selected lead list/source state
 - `workflowTableId`
-- first review/process sample rows, including row ids/hash when available
+- initial campaign-table execution slice rows, including row ids/hash when available
 - user's filter choice and any explicit exclusions or tradeoffs
 
 The filter may inspect campaign-table rows through scoped tools such as
@@ -112,7 +112,7 @@ prospect can afford this specific offer at this specific price point. Use a
 reasonable public proxy such as funding, headcount, revenue band, team maturity,
 current tool spend, practice size, location count, consumer purchasing power,
 job-to-be-done intensity, or buyer budget ownership. If no reliable proxy exists
-in the review batch or normal enrichment path, return `confirm-with-user` and
+in the initial campaign rows or normal enrichment path, return `confirm-with-user` and
 ask the parent to get the budget proxy before message approval.
 
 ## Table-Stakes Gates
@@ -141,7 +141,7 @@ the gate is irrelevant for this campaign:
 ## Competitor / Vendor Exclusion
 
 Every confirmed filter should include a competitor / vendor / wrong-side
-exclusion unless the brief and review batch make it clearly irrelevant.
+exclusion unless the brief and campaign rows make it clearly irrelevant.
 
 Use this test:
 
@@ -149,11 +149,11 @@ Use this test:
   or marketplace participant appear on the same comparison page as the client?
 - Would they compete for the same customer budget, sell into the same buyer
   workflow, or sit on the wrong side of the marketplace?
-- Did the review batch show adjacent companies that the customer would likely
+- Did the campaign rows show adjacent companies that the customer would likely
   reject only after seeing the list?
 
 If yes, add an explicit exclude rule. Include named competitors from the brief,
-review batch, or user context when available, plus the general category
+campaign rows, or user context when available, plus the general category
 exclusion so new lookalike competitors are also blocked.
 
 ## Marketplace Safety
@@ -170,14 +170,14 @@ Examples:
 - Supply-side acquisition campaign: exclude demand-side buyers or employers when
   they are not the outbound target.
 
-If more than roughly 20% of the review batch appears to be the forbidden side,
+If more than roughly 20% of the initial campaign rows appear to be the forbidden side,
 classify it as a list/source problem and return `revise-find-leads`; do not
 hide that problem behind narrow rubrics.
 
 ## Suppression And Relationship Safety
 
 Do not put DNC or one-off relationship-safety notes into production rubrics
-unless the review batch shows that the pattern will leak at meaningful volume
+unless the campaign rows show that the pattern will leak at meaningful volume
 and normal DNC/domain suppression will not catch it. Former employers, existing
 customers, investors, partner lists, and one-off do-not-contact domains usually
 belong in the recommendation as DNC/suppression instructions outside the rubric JSON.
@@ -231,19 +231,19 @@ Recommended grouping:
 
 For each proposed rule:
 
-1. Inspect matching and failing review-batch rows.
+1. Inspect matching and failing campaign rows.
 2. Decide whether the rule removes real noise or blocks real buyers.
 3. Mark the rule as necessary, loosen, or remove.
 4. Estimate the resulting pass rate and yield impact.
 
 Repeated false positives should become explicit exclude rules whenever the same
-pattern appears more than once in the review batch. Preview-card missingness is
+pattern appears more than once in the campaign rows. Preview-card missingness is
 not a hard production exclusion unless the same missing evidence will remain
 missing after normal enrichment/public research.
 
 ## Source Contradictions
 
-If review-batch evidence contradicts the approved source thesis, do not rewrite
+If campaign-row evidence contradicts the approved source thesis, do not rewrite
 the campaign brief silently. Return one of these instead:
 
 - `confirm-with-user` when a viable alternative source or filter tradeoff needs
@@ -319,7 +319,7 @@ authority, account fit, capacity, geography, and exclusions.
 - Do not save rubrics for `confirm-with-user` or `revise-find-leads`.
 - Do not loosen the filter just to preserve volume.
 - Do not make the filter so narrow that it contradicts the approved source
-  unless review-batch evidence clearly requires it.
+  unless campaign-row evidence clearly requires it.
 
 ## Prohibited During Normal Create-Campaign
 

package/skills/create-campaign-v2/references/final-handoff-contract.md

@@ -18,7 +18,7 @@ CampaignOffer state and the watch link are canonical. Disk artifacts are
 optional debug/UAT diagnostics, and normal customer runs should not expose local
 draft files. Resume, gating, and handoff read campaign state first. At this
 point, `workflowTableId` is the campaign table, while `selectedLeadListId`
-remains the source list that produced the review batch.
+remains the source list that produced the campaign rows.
 
 ## Step 16 Setup
 
@@ -64,7 +64,7 @@ currentStep: "sequence" })` to attach the sender via the v3 senders route and
 The final handoff must answer five customer questions in plain language:
 
 - where to inspect the campaign (`watchUrl`)
-- what is ready now (brief, filters/rubrics, review-batch leads, messages, and
+- what is ready now (brief, filters/rubrics, campaign rows, messages, and
   sequence after a sender is attached)
 - whether the next UI step is Settings, Sequence, or Send
 - why the selected LinkedIn sender and Slack reply review matter before launch
@@ -77,8 +77,8 @@ When `lead-source-intake.json` exists, also answer:
 - which source was materialized (`supplied-linkedin-profiles`,
   `supplied-domains`, or `existing-lead-list`)
 - how many rows/accounts were supplied
-- how many rows were imported into the first review batch
-- that only the first review batch was enriched and messaged before
+- how many rows were imported into the initial campaign setup slice
+- that only the initial campaign rows were enriched and messaged before
   greenlight, not the full supplied list
 - for `existing-lead-list`, that the source list was reused, not recreated
 

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

@@ -7,13 +7,13 @@ on every revision round.
 ## Principle
 
 We spend a bounded review/process sample (default 15 rows) to prove fit before
-the user spends credits on the rest of the confirmed source list. The sample loop has one job:
+the user spends credits on the rest of the confirmed source list. The setup loop has one job:
 answer the question "do we have enough real passing examples for the user to
 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 sample. If
+If the answer is yes, proceed to Step 15 messaging for the initial campaign rows. If
 the answer is no, diagnose whether the brief is wrong or the list is wrong,
 and either revise brief autonomously OR escalate to the user — never
 auto-revise leads.
@@ -25,7 +25,7 @@ auto-revise leads.
   not a visible route)
 - Approved message template/token rules exist in the campaign brief before any
   enrichment or scoring cells are queued
-- Confirmed campaign rows from Step 13, with first review/process sample from
+- Confirmed campaign rows from Step 13, with the internal execution slice from
   `reviewBatchRowIds` (size: `importLimit`, default 15)
 - Config from `auto-execute.yaml`: `sample.sampleSize`,
   `sample.minProjectedPass`, `sample.maxRevisionRounds`
@@ -57,9 +57,9 @@ auto-revise leads.
    scoring from the queued Enrich Prospect cells
 
 6. wait_for_rubric_results(sample, targetCount = <cohortSize>, minPassedCount = 1)
-   - cohortSize = stats.totalRows of the enrichment batch, or the review sample
+   - cohortSize = stats.totalRows of the enrichment batch, or the execution slice
      count
-   - default targetCount=15 matches the default review sample, but pass the
+   - default targetCount=15 matches the default execution slice, but pass the
      explicit batch count anyway so future larger expansion batches do not
      accidentally stop early
      (see §Known Tool Behaviors #3)
@@ -179,7 +179,7 @@ company, enrichCellId, enrichStatus) over the default shape.
 
 ### 5. `wait_for_rubric_results` can timeout with enough signal to decide
 
-Observed: a 15-row review sample may return `ready=false`, `reason="timeout"`,
+Observed: a 15-row internal execution slice may return `ready=false`, `reason="timeout"`,
 and partial stats such as 12/15 scored, 4 passing, 4 messages generated. That is
 enough to diagnose an underperforming sample. Waiting again without active
 processing makes the experience feel frozen.
@@ -211,8 +211,8 @@ Worked examples with defaults (sampleSize=15, importLimit=15):
 | 15           | 15            | Yes                                               |
 
 When non-default importLimit/sampleSize are configured, the math scales
-the same way. In the default review-batch mode, the sample size equals the
-import limit, so the projection is the actual review-batch pass count.
+the same way. In the default internal-slice mode, the slice size equals the
+import limit, so the projection is the actual pass count.
 
 ## Brief-vs-List Diagnosis
 

package/skills/create-campaign-v2/references/step-13-import-leads.md

@@ -55,7 +55,7 @@ Supported branches:
   `import_leads({ campaignOfferId })` for Signal Discovery unless selected posts
   already exist on the campaign. Provider import materializes the source lead
   list from the approved source-capacity plan; it is not the same target as the
-  default 15-row campaign review/process sample.
+  default internal campaign-table execution slice.
 - **Supplied LinkedIn profile CSV** — confirm `load_csv_linkedin_leads` only
   after the user approves that supplied-list source. Batch/materialize the
   uploaded CSV into a Sellable lead-list table. Persist the returned
@@ -74,7 +74,7 @@ Supported branches:
   its `domainFilterId`, run a campaign-associated Prospeo people search with
   `campaignOfferId`, provider prompt preflight, and `domainFilterId`, then
   materialize the source list from that search before copying the confirmed
-  list into the campaign table and processing the first 15 rows.
+  list into the campaign table and processing the first internal execution slice.
 
 ## Campaign-Attached Source Contract
 
@@ -114,7 +114,7 @@ import_leads({
 
 Provider is inherited from the selected source decision (not re-selected here)
 and should already be saved on the campaign before import. For Sales Nav and
-Prospeo, `<sourceCandidateTarget>` is not the 15-row review/process sample. It is
+Prospeo, `<sourceCandidateTarget>` is not the internal campaign-table execution slice. It is
 the source-list export/materialization count from the approved source math. Aim
 for about 1,000 source contacts by default and use the provider cap internally
 when the raw pool is larger. If projected good fits remain below the target,
@@ -133,11 +133,11 @@ count. The planning floor is 10% projected fit after cleanup; if Signal
 Discovery falls below that floor during the pre-scrape sample, revise the source
 plan before importing. After an approved scrape starts, do not discard a nonempty
 completed source list just because it lands below the source-candidate target:
-confirm/copy the completed list for the first review sample, then add more posts
-or switch provider if the sample quality or scale is not enough. The subsequent
+confirm/copy the completed list for campaign setup, then add more posts
+or switch provider if the source quality or scale is not enough. The subsequent
 `confirm_lead_list` call uses `reviewBatchLimit: 15`. It copies the confirmed
 source rows into the campaign table and returns only the first 15 rows as the
-review/process sample.
+internal campaign-table execution slice.
 
 Harvest-specific interpretation: Signal Discovery post comments and reactions
 are paged from Harvest at about 100 records per page, with production caps of
@@ -145,12 +145,12 @@ are paged from Harvest at about 100 records per page, with production caps of
 headline-passing candidates after that scrape. Therefore `71 source rows` means
 71 candidates passed headline/list filtering and were inserted; it does not
 mean the post scrape stopped after 71 raw engagers. Treat raw visible engagement,
-raw fetched pages, inserted source rows, and the 15-row review/process sample as
+raw fetched pages, inserted source rows, and the internal campaign-table execution slice as
 separate numbers.
 
 For supplied direct lists, `confirm_lead_list` should receive
 `reviewBatchLimit: 15` so the campaign table can hold the confirmed list while
-the first 15 rows drive the initial approval flow.
+the first 15 rows drive the internal setup flow.
 
 ## `mode=add` Two-Step Handshake
 
@@ -241,7 +241,7 @@ cannot scale further without a new source lane.
 - `import_leads` is allowed immediately after the concrete source-action
   approval. It materializes the source list and then `confirm_lead_list` copies
   the confirmed source rows into the campaign table while returning only the
-  first 15 rows for the initial review/process sample. Enrichment and fit
+  first 15 rows for the internal campaign-table execution slice. Enrichment and fit
   scoring wait for saved rubrics/run conditions; message cells wait for the
   approved message set.
 - Step 13 MUST reuse an approved source already attached with `campaignOfferId`

package/skills/create-campaign-v2/references/step-15-re-cascade.md

@@ -10,7 +10,7 @@ to `awaiting-user-greenlight`, and on every resume into Step 15.
 ## Principle
 
 Generate Message cells are cascade-scoped. If Step 14's rubric flips rows from
-pending → passed AFTER Step 15 first observes messages for the review batch, the
+pending → passed AFTER Step 15 first observes messages for the initial campaign rows, the
 new rows can sit pending with no message. That must not block the first review
 handoff. Step 15 opens review as soon as one passing generated message exists;
 late-passed rows can be re-cascaded after explicit user continuation or resume.
@@ -24,7 +24,7 @@ flat at 257. The new rows never got messages.
 Re-cascade runs whenever ALL of the following are true:
 
 1. The user has already approved the first generated message or explicitly asked
-   to continue processing more review-batch rows.
+   to continue processing more campaign rows.
 2. A subsequent check of rubric state shows rows that were pending at
    first message-generation pass are now passed.
 3. Those newly-passed rows do NOT yet have generated messages

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

@@ -49,13 +49,13 @@ states.
 
 ## 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    |
+| stage          | UI label       | Next           |
+| -------------- | -------------- | -------------- |
+| `brief-review` | Brief review   | Find Leads     |
+| `find-leads`   | Find Leads     | Campaign setup |
+| `review-batch` | Campaign setup | Fit + message  |
+| `fit-message`  | Fit + message  | Review ready   |
+| `review-ready` | Review ready   | Validation     |
 
 ## Examples
 
@@ -138,7 +138,7 @@ Search iteration:
   "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 scraping so the first review sample stays on-brief.",
+  "agentIntent": "It is sampling a few engagers before scraping so the source quality stays on-brief.",
   "nextAction": "Review source math"
 }
 ```
@@ -165,9 +165,9 @@ Review/process sample:
 ```json
 {
   "stage": "review-batch",
-  "headline": "Preparing your first sample",
-  "visibleState": "This page shows the confirmed source leads. Codex will process the first 15 for review.",
-  "agentIntent": "Codex is preparing the first campaign sample from those leads.",
+  "headline": "Preparing campaign setup",
+  "visibleState": "This page shows the confirmed source leads. Codex will process the initial campaign rows for setup.",
+  "agentIntent": "Codex is preparing filters and messages from those leads.",
   "nextAction": "Fit + message"
 }
 ```
@@ -179,8 +179,8 @@ Source approved and import starting:
   "stage": "review-batch",
   "headline": "Copying source leads",
   "visibleState": "The browser is still showing the approved LinkedIn Engagement source candidates.",
-  "agentIntent": "Codex is copying the confirmed source into the campaign and will process only the first 15 for review.",
-  "nextAction": "Review sample ready"
+  "agentIntent": "Codex is copying the confirmed source into the campaign and will process only the internal execution slice for setup.",
+  "nextAction": "Campaign setup ready"
 }
 ```
 
@@ -282,8 +282,8 @@ Blocked/recovering:
 ```json
 {
   "stage": "review-batch",
-  "headline": "Fixing the review batch",
-  "visibleState": "The browser is not showing the campaign batch yet.",
+  "headline": "Fixing campaign setup",
+  "visibleState": "The browser is not showing campaign rows yet.",
   "agentIntent": "Codex is reconnecting the campaign state before moving forward.",
   "nextAction": "Fit + message",
   "blockedReason": "Campaign batch is not ready yet."