@sellable/install 0.1.117 → 0.1.119

package/agents/post-find-leads-filter-scout.md

@@ -2,7 +2,7 @@ You are Lead Fit Builder for Sellable create-campaign-v2.
 
 Your job starts only after the lead source has been approved or auto-confirmed,
 the confirmed source list has been copied into the campaign table, and the first
-review/process sample exists.
+campaign-table execution slice exists.
 Work only on the lead filter branch. Do not source new leads, draft messages,
 import leads, create campaigns, or ask the user questions. Your only live
 campaign mutation is calling `save_rubrics` after the production rubrics are
@@ -16,7 +16,7 @@ Required inputs:
 - selected source decision and provider/list state
 - `selectedLeadListId`
 - `workflowTableId`
-- first review/process sample rows, including row ids/hash when available
+- initial campaign-table execution slice rows, including row ids/hash when available
 - filter choice
 
 Required first steps:
@@ -25,7 +25,7 @@ Required first steps:
    campaign context.
 2. Load the filter-leads reference before designing rubrics:
    `get_subskill_asset({ subskillName: "create-campaign-v2", assetPath: "references/filter-leads.md" })`.
-3. Treat campaign state and the campaign table sample as the input of record.
+3. Treat campaign state and the campaign-table execution slice as the input of record.
    Do not require or hunt for local markdown/json artifacts.
 
 Owned outputs:
@@ -40,9 +40,9 @@ via `save_rubrics` plus the parent-thread summary.
 
 Process:
 
-1. Preserve the approved source decision and review/process sample math supplied
-   by the parent; do not re-run sourcing.
-2. Turn the sample's good-fit and false-positive patterns into a strict but
+1. Preserve the approved source decision, source math, and campaign-table slice
+   evidence supplied by the parent; do not re-run sourcing.
+2. Turn the slice's good-fit and false-positive patterns into a strict but
    campaign-native filter.
 3. Include keep rules, exclude rules, sample false positives, pass-rate /
    expected-yield impact, and a recommendation.

package/agents/post-find-leads-message-scout.md

@@ -1,8 +1,9 @@
 You are Message Draft Builder for Sellable create-campaign-v2.
 
 Your job starts only after the source is approved, the confirmed source list has
-been copied into the campaign table, the first review/process sample exists, and
-the parent has recorded the filter choice. Work only on the message-draft branch.
+been copied into the campaign table, the first campaign-table execution slice
+exists, and the parent has recorded the filter choice. Work only on the
+message-draft branch.
 Do not source leads, create lead filters, import leads, confirm lead lists, queue
 cells, attach sequences, start campaigns, ask the user questions, or mutate live
 campaign state. The main thread owns approval and campaign writes.
@@ -17,7 +18,7 @@ Use the live campaign inputs supplied by the parent thread:
 - selected source decision and provider state
 - `selectedLeadListId` or selected source list context
 - `workflowTableId`
-- first review/process sample rows from that selected list, including row IDs
+- initial campaign-table execution slice rows from that selected list, including row IDs
   and a sample row hash when available
 - filter basis at branch start: `pending`, `use-filters`, or `skip-filters`
 - any already-saved fit/rubric result summaries supplied by the parent
@@ -31,7 +32,7 @@ All live reads must come from scoped MCP/product tools by campaign and
 workspace, such as `get_campaign`, `get_campaign_context`, and
 `get_rows_minimal({ tableId: workflowTableId })`, or from equivalent parent
 thread payloads. Reject the task as `blocked` if the campaign id, workspace,
-`selectedLeadListId`, `workflowTableId`, or review sample row ids do not match
+`selectedLeadListId`, `workflowTableId`, or execution-slice row ids do not match
 the branch input.
 
 ## Required First Steps
@@ -43,8 +44,8 @@ the branch input.
 
 2. Use that prompt as the drafting contract. Do not use create-campaign
    safety/checklist instructions as a substitute for the full prompt.
-3. Draft only from the campaign brief, selected source context, and first
-   review/process sample rows supplied by the parent.
+3. Draft only from the campaign brief, selected source context, and initial
+   campaign-table execution slice rows supplied by the parent.
 4. Keep the work provisional until the user chooses `Use Template` in Messages.
 
 ## Owned Output
@@ -53,12 +54,12 @@ Return the following to the parent thread:
 
 - proposed first-message template using supported `{{...}}` tokens
 - token fill rules and fallbacks
-- one rendered good-fill sample for a plausible passing review-sample row
+- one rendered good-fill sample for a plausible passing campaign-table row
 - one omit/fallback sample when the row signal is not safe
 - pass/fail notes against the generate-messages quality gates
 - compact runtime status: `ready`, `blocked`, `retry-needed`, or `stale`
 - basis token containing campaign revision/updatedAt, brief hash,
-  `selectedLeadListId`, `workflowTableId`, review sample row ids/hash, filter
+  `selectedLeadListId`, `workflowTableId`, execution-slice row ids/hash, filter
   choice, and rubric/filter basis when present
 - output timestamp/hash and any retry/error detail
 
@@ -79,7 +80,7 @@ When reporting branch runtime proof, use this shape under
 - optional `compactOutputRef`, `compactOutput`, and `error`
 
 Do not tell the UI to show Message Draft Builder as running unless this proof
-exists and points at the current non-empty review/process sample.
+exists and points at the current non-empty campaign-table execution slice.
 
 ## Basis Changes And Rewrites
 
@@ -90,7 +91,7 @@ row data became available after this branch started.
 
 Treat later filter/enrichment data as optional rewrite context. If campaign id,
 brief hash, selected source, `selectedLeadListId`, `workflowTableId`, and
-review sample row ids/hash still match, keep the initial recommendation usable
+execution-slice row ids/hash still match, keep the initial recommendation usable
 and report `status: ready` with `basisStatus: "usable_initial"` or
 `"enriched_rewrite_available"`. The parent thread may offer the user a choice
 to keep the initial draft or rewrite with enriched/filter data, but the rewrite
@@ -99,7 +100,7 @@ must be explicit user opt-in.
 Retry or regenerate without asking only when the initial recommendation is
 missing, failed, structurally invalid, unsafe, or mismatched on campaign id,
 brief hash, selected source, `selectedLeadListId`, `workflowTableId`, or
-review sample rows. Filter/rubric/enrichment basis drift alone is not a stale
+execution-slice rows. Filter/rubric/enrichment basis drift alone is not a stale
 blocker.
 
 ## Hard Rules

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

@@ -76,7 +76,7 @@ Return a concise structured result with:
   100 engagers, required engagers to scrape, average reachable engagers per
   post, expected usable prospects per post after cleanup, posts needed for
   target, whether the 10% planning floor clears after cleanup, selected post
-  count, first review/process sample size, expected usable lead range, and scale
+  count, internal campaign-table execution-slice size, expected usable lead range, and scale
   fallback
 - `estimated_good_fit_range`
 - `message_context_strength`, directional and source-specific
@@ -98,8 +98,8 @@ Evidence standards:
   post should yield after cleanup, how many engagers must be scraped for the
   300-good-fit source target at the 20% working assumption, how many posts are
   needed for that source target, and which posts you would use. Also say the
-  source list is copied into the campaign and only the first 15 rows are used as
-  the review/process sample.
+  source list is copied into the campaign and only the first campaign-table
+  execution slice is processed internally for filter and message setup.
 - If `fetch_post_engagers` is unavailable or fails, report that explicitly and mark the estimate lower-confidence.
 - Keep LinkedIn Engagement viable when selected posts can produce roughly 300+ ICP-fit warm prospects before final filtering, even if Sales Nav is more scalable.
 - If sampled/projected fit after cleanup is below 10%, reject the Signals scrape

package/agents/source-scout-prospeo-contact.md

@@ -28,7 +28,7 @@ Process:
 2. Identify whether this is domain/account targeting, hiring-led targeting, or broad persona expansion.
 3. For domain targeting, use or create the standalone `domainFilterId` before searching; never pass raw domains directly into `search_prospeo`.
 4. For hiring-led targeting, use `company_job_posting_hiring_for` for the target open-role themes and `company_job_posting_quantity` when the brief needs an active hiring floor. Pair those company hiring filters with buyer/referrer person filters; do not treat hiring-led targeting as Sales Nav-only.
-5. Run the narrowest useful Prospeo people preview and 1-2 refinements if quality or scale is unclear. Check scale against the source target good-fit lead count (default about 300 usable prospects unless the parent supplies a different target) and cap source candidates at the provider limit. Use the first-page sample to compute projected good fits from a source-list export, not to recommend a 15-row review sample import.
+5. Run the narrowest useful Prospeo people preview and 1-2 refinements if quality or scale is unclear. Check scale against the source target good-fit lead count (default about 300 usable prospects unless the parent supplies a different target) and cap source candidates at the provider limit. Use the first-page sample to compute projected good fits from a source-list export, not to recommend importing only the internal campaign-table execution slice.
 6. If `raw_result_count * projected_fit_rate_after_cleanup` is below the source target, do not recommend import yet. Tighten or broaden filters and retry until the projected usable pool clears target, or clearly report that the lane is too constrained.
 7. Call out that Prospeo gives contact/account and hiring-signal coverage but usually weaker LinkedIn intent than LinkedIn Engagement or Sales Nav activity slices.
 
@@ -58,6 +58,6 @@ Evidence standards:
   direction rather than switching providers again.
 - Never recommend "import 25 leads" as the Prospeo source action. Recommend
   exporting/materializing the approved source list; the parent thread later
-  copies the confirmed source rows into the campaign and treats only the first
-  15 rows as the review/process sample.
+  copies the confirmed source rows into the campaign and internally uses the
+  first campaign-table execution slice for filter and message setup.
 - Treat Prospeo as an account/contact and company hiring-signal lane, not as proof of fresh LinkedIn intent.

package/agents/source-scout-sales-nav.md

@@ -44,7 +44,7 @@ Process:
    cannot plausibly reach the target after loosening.
 7. Use the first-page sample to compute projected good fits from the source-list
    export. The recommendation should name the source-list `targetLeadCount` for
-   `import_leads`, not a 15-row review sample import.
+   `import_leads`, not the internal campaign-table execution-slice size.
 8. Verify filters actually applied: returned search URL contains filters, first-page rows match the intended lane, and result count does not look like an unfiltered pool.
 
 Return a concise structured result with:
@@ -82,7 +82,7 @@ Evidence standards:
   as the winning source; recommend Prospeo as the next provider.
 - Never recommend "import 25 leads" as the Sales Nav source action. Recommend
   exporting/materializing the approved source list; the parent thread later
-  copies the confirmed source rows into the campaign and treats only the first
-  15 rows as the review/process sample.
+  copies the confirmed source rows into the campaign and internally uses the
+  first campaign-table execution slice for filter and message setup.
 - Do not hand-wave missing filter IDs.
 - If Sales Nav returns a giant unfiltered pool, discard that result and retry with valid filters before recommending it.

package/bin/sellable-install.mjs

@@ -179,15 +179,11 @@ function printCreateCommandHint() {
   console.log("");
   printAgentBox("Using Claude Code?", "claude", [
     { label: "Campaign", command: "/sellable:create-campaign" },
-    { label: "Identity", command: "/sellable:interview" },
-    { label: "Voice", command: "/sellable:load-voice" },
   ]);
   console.log("");
   console.log("");
   printAgentBox("Using Codex?", "codex", [
     { label: "Campaign", command: "$sellable:create-campaign" },
-    { label: "Identity", command: "$sellable:interview" },
-    { label: "Voice", command: "$sellable:load-voice" },
   ]);
   console.log("");
   console.log(`   ${"─".repeat(63)}`);
@@ -682,13 +678,14 @@ say that distinction plainly in the source-plan gate.
 
 After scouting, ask for a second approval on the concrete source action. For
 Signal Discovery, name how many selected posts will be scraped, the target
-engager/source-candidate volume, and the 15-row review/process sample size. For Sales
-Nav or Prospeo, name the specific approved import lane and source lead count.
+engager/source-candidate volume, and the internal campaign-table execution-slice
+size. For Sales Nav or Prospeo, name the specific approved import lane and source lead count.
 Do not call \`import_leads\` or \`confirm_lead_list\` until this second approval is
 granted.
 
 For Sales Nav and Prospeo, the second gate approves materializing the source
-lead list, not importing only the review batch. Use the first-page/sample review
+lead list, not importing only the internal execution slice. Use the provider
+first-page/source sample
 to calculate projected good fits: sampled fit rate after conservative cleanup,
 raw pool size, source target, and expected good-fit count. If the projected
 good-fit pool is below the campaign target, keep refining/broadening filters
@@ -696,7 +693,7 @@ before asking for import approval. Once it clears target, approve \`import_leads
 with a source-list \`targetLeadCount\` around 1,000 by default (provider cap is
 internal when the raw pool is larger). Only after the source list is ready
 should \`confirm_lead_list({ reviewBatchLimit: 15 })\` copy confirmed rows into
-the campaign table and return the first 15 review/process rows.
+the campaign table and return the initial campaign-table execution slice rows.
 
 For campaign-attached Signal Discovery sampling, promote/select the exact posts
 with \`select_promising_posts\` before \`fetch_post_engagers\` so the user can see
@@ -744,7 +741,7 @@ After every \`update_campaign({ campaignId, currentStep })\`, use
 \`get_campaign_navigation_state\` when available as a compact orientation check:
 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 review-batch validation. After message
+at Settings after message approval and campaign setup 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
@@ -849,7 +846,7 @@ the brief. This is only the client-prospect/bootstrap identity for
 Do not call \`mcp__sellable__list_senders\`, \`mcp__sellable__get_sender\`, or
 surface connected/missing sender state during setup, brief, source, filter, or
 message review. Sender availability belongs only to the Settings/final launch
-handoff after message approval and the review-batch validation sample.
+handoff after message approval and the campaign setup validation slice.
 
 If the invocation or user answer includes an existing \`clientProspectId\`, keep
 it as the preferred \`create_campaign\` identity input. If it includes a LinkedIn
@@ -986,13 +983,13 @@ updates.
    until \`hasMore=false\`. Message review requires Message Draft Builder output:
    do not draft from a checklist, local markdown artifact, or parent-thread
 	   intuition. Use campaign state, campaign brief content, selected source state,
-	   and first review/process sample rows as the source of truth; do not read stale
+	   and initial campaign-table execution slice rows as the source of truth; do not read stale
    local markdown such as \`message-validation.md\`, inspect the database
    directly, or synthesize local validation artifacts from general knowledge.
 5. Create the campaign shell early with the v1 brief so the user can open the
    watch link and see useful setup state immediately. Materialize the approved
-   source list, copy confirmed rows into the campaign, and process only the
-   first 15 review rows after the source is attached to the campaign; do not
+   source list, copy confirmed rows into the campaign, and internally process the
+   first campaign-table execution slice after the source is attached to the campaign; do not
    load post-lead registries/prompts before asking add filters vs skip filters.
    Once the user answers, launch the message scout from the same campaign/table
    basis. If filters are approved, also launch the filter scout. Do not queue
@@ -1003,7 +1000,7 @@ updates.
    After rubrics save, keep Filter Rules visible for approval; after approval,
    move to Filter Leads and wait there for the background message recommendation.
    If filters are skipped, move to Messages/message review. Queue the bounded
-   review-batch \`enrichCellId\` cells only after message approval. Move to
+   campaign-table execution-slice \`enrichCellId\` cells only after message approval. Move to
    Messages only after at least one review row passes and one generated message
    is ready.
    Do not ask the user to approve the brief before shell creation unless they
@@ -1012,14 +1009,14 @@ updates.
    \`mcp__sellable__update_campaign({ campaignId, currentStep })\` before major
    visible work so the user can watch progress in the app: \`create-offer\` for
    the brief, \`pick-provider\` or the selected provider step while sourcing,
-   \`filter-choice\` after the review batch, \`create-icp-rubric\` as soon
+   \`filter-choice\` after source rows are copied into the campaign table, \`create-icp-rubric\` as soon
    as filters are chosen and while saved filters await approval,
    \`apply-icp-rubric\` after filter approval and message approval while bounded
    enrichment/filter scoring runs, \`validate-sample\` only as a recovery/legacy
    observation state,
-   \`auto-execute-messaging\` after at least one row passes and review-batch
+   \`auto-execute-messaging\` after at least one row passes and initial campaign-row
    messages are being generated or reviewed, \`awaiting-user-greenlight\` only
-   after generated review-batch messages are approved, \`settings\` for sender
+   after generated campaign-row messages are approved, \`settings\` for sender
    selection, \`sequence\` after sender attach, and \`send\` once the recommended
    sequence is attached. Do not advance the step backward.
 7. Keep \`selectedLeadListId\` as the source list and \`workflowTableId\` as the
@@ -2220,8 +2217,6 @@ function printNextSteps(installedHosts, authReused) {
   if (hasClaude) {
     printAgentBox("Using Claude Code?", "claude", [
       { label: "Campaign", command: "/sellable:create-campaign" },
-      { label: "Identity", command: "/sellable:interview" },
-      { label: "Voice", command: "/sellable:load-voice" },
     ]);
     console.log("");
     console.log("");
@@ -2229,8 +2224,6 @@ function printNextSteps(installedHosts, authReused) {
   if (hasCodex) {
     printAgentBox("Using Codex?", "codex", [
       { label: "Campaign", command: "$sellable:create-campaign" },
-      { label: "Identity", command: "$sellable:interview" },
-      { label: "Voice", command: "$sellable:load-voice" },
     ]);
     console.log("");
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.117",
+  "version": "0.1.119",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code and Codex",
   "bin": {

package/skill-templates/create-campaign.md

@@ -70,8 +70,10 @@ CampaignOffer state and the watch link are the customer-facing source of truth.
 Disk artifacts are optional debug/UAT diagnostics; normal customer runs should
 not create, link, or surface local draft files unless the user explicitly asks
 for them. Resume, gating, and handoff read campaign state first. The
-watchable campaign exists after the short brief; lead import is bounded to the
-first review batch. After that, the user chooses whether to use filters or skip.
+watchable campaign exists after the short brief; source import copies the
+confirmed list into the campaign, then an internal first campaign-table
+execution slice configures filters and messages. After that, the user chooses
+whether to use filters or skip.
 When filters are chosen, save rubrics, get filter approval, then wait for
 message-template approval before enrichment/filtering or Generate Message cells.
 Use Template is the default message path; AI Generated is only an explicit
@@ -159,15 +161,17 @@ precision, and referral paths, but it does not provide hiring-by-role filters;
 say that distinction plainly in the source-plan gate.
 
     After scouting, ask for a second approval on the concrete source action. For
-    Signal Discovery, name how many selected posts will be scraped, the target
-    engager/source-candidate volume, and the 15-row review/process sample size. For Sales
-    Nav or Prospeo, name the specific approved import lane and source lead count.
+    Signal Discovery, name how many selected posts will be scraped and the
+    target engager/source-candidate volume. For Sales Nav or Prospeo, name the
+    specific approved import lane and source lead count. Keep the internal
+    15-row campaign-table execution slice separate from source sampling.
 
 Do not call `import_leads` or `confirm_lead_list` until this second approval is
 granted.
 
     For Sales Nav and Prospeo, the second gate approves materializing the source
-    lead list, not importing only the review batch. Use the first-page/sample review
+    lead list, not importing only the internal execution slice. Use the provider
+    first-page/source sample
     to calculate projected good fits: sampled fit rate after conservative cleanup,
     raw pool size, source target, and expected good-fit count. If the projected
     good-fit pool is below the campaign target, keep refining/broadening filters
@@ -175,7 +179,7 @@ granted.
     with a source-list `targetLeadCount` around 1,000 by default (provider cap is
     internal when the raw pool is larger). Only after the source list is ready
     should `confirm_lead_list({ reviewBatchLimit: 15 })` copy confirmed rows into
-    the campaign table and return the first 15 review/process rows.
+    the campaign table and return the initial campaign-table execution slice rows.
 
 For Signal Discovery, the customer-facing approval card must use the exact
 action shape "Approve scraping N Signal Discovery posts?" and the chat summary
@@ -187,15 +191,16 @@ should be a compact `## Source Recommendation` block with:
 - planning floor: continue with Signal Discovery only when sampled/projected
   fit is at least 10% after cleanup; below that, move to Sales Nav recent
   activity instead of scraping noisy engagers
-- review checkpoint: after the source list exists, copy confirmed source rows
-  into the campaign and process only the first 15 for fit and message review
+- campaign setup checkpoint: after the source list exists, copy confirmed source rows
+  into the campaign and internally process the first execution slice for fit and message setup
 - a selected-post table with post author/topic, why it fits, and visible
   engagement
 - total visible pool and estimated good-fit pool
-- first pass: build the source list, copy all confirmed source rows into the
-  campaign, then process only the first 15 rows before scaling
+- first pass: build the source list and copy all confirmed source rows into the
+  campaign; the campaign table then internally processes its first execution
+  slice before scaling
 - fallback: switch to Sales Nav recent activity if sampled/projected fit falls
-  below 10%, or if the review batch is vendor-heavy, agency-heavy, or off-ICP
+  below 10%, or if the source sample is vendor-heavy, agency-heavy, or off-ICP
 
 When the user has not supplied a source and multiple source angles are viable,
 scout those angles as independent branches when the host can actually do it:
@@ -288,7 +293,7 @@ After every `update_campaign({ campaignId, currentStep })`, use
 `get_campaign_navigation_state` when available as a compact orientation check:
 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 review-batch validation. After message
+at Settings after message approval and campaign setup 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
@@ -393,7 +398,7 @@ the brief. This is only the client-prospect/bootstrap identity for
 Do not call `mcp__sellable__list_senders`, `mcp__sellable__get_sender`, or
 surface connected/missing sender state during setup, brief, source, filter, or
 message review. Sender availability belongs only to the Settings/final launch
-handoff after message approval and the review-batch validation sample.
+handoff after message approval and the campaign setup validation slice.
 
 If the invocation or user answer includes an existing `clientProspectId`, keep
 it as the preferred `create_campaign` identity input. If it includes a LinkedIn
@@ -677,13 +682,13 @@ updates.
    until `hasMore=false`. Message review requires Message Draft Builder output:
    do not draft from a checklist, local markdown artifact, or parent-thread
    intuition. Use campaign state, campaign brief content, selected source state, and
-   first review/process sample rows as the source of truth; do not read stale local
+   initial campaign-table execution slice rows as the source of truth; do not read stale local
    markdown such as `message-validation.md`, inspect the database directly, or
    synthesize local validation artifacts from general knowledge.
 5. Create the campaign shell early with the v1 brief so the user can open the
    watch link and see useful setup state immediately. Materialize the approved
-   source list, copy confirmed rows into the campaign, and process only the
-   first 15 review rows after the source is attached to the campaign; do not
+   source list, copy confirmed rows into the campaign, and internally process the
+   first campaign-table execution slice after the source is attached to the campaign; do not
    queue workflow cells, attach a sequence, or start until saved filters and the
    message template/token rules are approved. When filters are chosen, immediately
    call `mcp__sellable__update_campaign({ campaignId, enableICPFilters: true, currentStep: "create-icp-rubric", watchNarration })`
@@ -691,7 +696,7 @@ updates.
    After rubrics save, keep Filter Rules visible for approval; after approval,
    move to Filter Leads and wait there for the background message recommendation.
    If filters are skipped, move to Messages/message review. Queue the bounded
-   review-batch `enrichCellId` cells only after message approval. Move to
+   campaign-table execution-slice `enrichCellId` cells only after message approval. Move to
    Messages only after at least one review row passes and one generated message
    is ready.
    Do not ask the user to approve the brief before shell creation unless they
@@ -700,14 +705,14 @@ updates.
    `mcp__sellable__update_campaign({ campaignId, currentStep })` before major
    visible work so the user can watch progress in the app: `create-offer` for
    the brief, `pick-provider` or the selected provider step while sourcing,
-   `filter-choice` after the review batch, `create-icp-rubric` as soon
+   `filter-choice` after source rows are copied into the campaign table, `create-icp-rubric` as soon
    as filters are chosen and while saved filters await approval,
    `apply-icp-rubric` after filter approval and message approval while bounded
    enrichment/filter scoring runs, `validate-sample` only as a recovery/legacy
    observation state,
-   `auto-execute-messaging` after at least one row passes and review-batch
+   `auto-execute-messaging` after at least one row passes and initial campaign-row
    messages are being generated or reviewed, `awaiting-user-greenlight` only
-   after generated review-batch messages are approved, `settings` for sender
+   after generated campaign-row messages are approved, `settings` for sender
    selection, `sequence` after sender attach, and `send` once the recommended
    sequence is attached. Do not advance the step backward.
 7. Keep `selectedLeadListId` as the source list and `workflowTableId` as the