@sellable/mcp 0.1.768 → 0.1.769

package/skills/refill-sends-evergreen-workflow/core/flow.v1.json

@@ -1,259 +0,0 @@
-{
-  "version": "v1.0",
-  "workflow": "refill-sends-evergreen-workflow",
-  "principle": "Plan evergreen waterfall refill as a read-only dry-run with zero mutations.",
-  "revisionProjectionContract": {
-    "canonicalWorkflow": "refill-sends-v2-workflow",
-    "action": "revise_message_template_and_rerun",
-    "requiredAuthorities": [
-      "targetConfig",
-      "runHandle",
-      "reportingContext",
-      "complete messageTemplateRevision with source:user_approved, approved markdown, authority digests, bounded cohort, and request/effect/revision-operation IDs"
-    ],
-    "noInference": "The deprecated alias preserves explicit authority losslessly and never infers it from forceRerun.",
-    "reporting": "Preserve refill_reporting.v2 and campaign_preparation_live.v2 fields exactly while redacting raw copy/prospect fields."
-  },
-  "enumeratedRungs": [
-    "start_campaign",
-    "approve_messages",
-    "wait_for_active_work",
-    "enrich_more",
-    "reconcile_source_copy",
-    "add_leads_same_source",
-    "paid_lane_fallback",
-    "next_campaign",
-    "wait_for_scheduler",
-    "done"
-  ],
-  "requiredBootstrap": [
-    {
-      "tool": "get_auth_status",
-      "purpose": "Confirm MCP auth before reading workspace or plan facts."
-    },
-    {
-      "tool": "get_active_workspace",
-      "purpose": "Resolve explicit workspace evidence when the request did not provide workspaceId."
-    },
-    {
-      "tool": "refill_sends_evergreen",
-      "requiredValues": {
-        "workspaceId": "{workspaceId}"
-      },
-      "requiredOutput": [
-        "readOnly true",
-        "approvalContract says Phase 85 is plan-only"
-      ]
-    },
-    {
-      "tool": "get_subskill_prompt",
-      "requiredValues": {
-        "subskillName": "refill-sends-evergreen-workflow"
-      },
-      "mustReadUntil": {
-        "hasMore": false
-      }
-    },
-    {
-      "tool": "get_subskill_asset",
-      "requiredValues": {
-        "subskillName": "refill-sends-evergreen-workflow",
-        "assetPath": "core/flow.v1.json"
-      },
-      "mustReadUntil": {
-        "hasMore": false
-      },
-      "validation": {
-        "workflow": "refill-sends-evergreen-workflow",
-        "versionPrefix": "v1",
-        "requiredTopLevelKeys": [
-          "states",
-          "gateOrder",
-          "enumeratedRungs",
-          "verification"
-        ]
-      }
-    },
-    {
-      "tool": "get_evergreen_refill_plan",
-      "requiredValues": {
-        "workspaceId": "{workspaceId}"
-      },
-      "requiredOutput": [
-        "planRevision",
-        "stateRevision",
-        "packet",
-        "journalPath",
-        "sideEffects"
-      ]
-    }
-  ],
-  "gateOrder": ["bootstrap", "plan", "report"],
-  "states": [
-    {
-      "id": "bootstrap",
-      "description": "Load the read-only command contract, workflow prompt, flow asset, and workspace facts.",
-      "allowedTools": [
-        "get_auth_status",
-        "get_active_workspace",
-        "list_workspaces",
-        "get_workspace",
-        "refill_sends_evergreen",
-        "get_subskill_prompt",
-        "get_subskill_asset",
-        "get_evergreen_refill_plan"
-      ],
-      "onEnter": [
-        {
-          "tool": "get_auth_status"
-        },
-        {
-          "tool": "refill_sends_evergreen",
-          "requiredFields": ["workspaceId"]
-        },
-        {
-          "tool": "get_subskill_prompt",
-          "requiredValues": {
-            "subskillName": "refill-sends-evergreen-workflow"
-          }
-        },
-        {
-          "tool": "get_subskill_asset",
-          "requiredValues": {
-            "subskillName": "refill-sends-evergreen-workflow",
-            "assetPath": "core/flow.v1.json"
-          }
-        }
-      ],
-      "transitions": {
-        "contract_loaded": "plan"
-      }
-    },
-    {
-      "id": "plan",
-      "description": "Call the dry-run evergreen refill planner exactly once for this invocation.",
-      "allowedTools": ["get_evergreen_refill_plan"],
-      "onEnter": [
-        {
-          "tool": "get_evergreen_refill_plan",
-          "requiredFields": ["workspaceId"],
-          "optionalFields": ["senderIds", "runState", "journal", "journalNote"]
-        }
-      ],
-      "requiredOutput": [
-        "sideEffects all false",
-        "planRevision starts with pr1:",
-        "journalPath reported",
-        "chosen evergreenRung is in enumeratedRungs"
-      ],
-      "allowedRungsSource": "enumeratedRungs",
-      "doNotAllow": [
-        "add_column",
-        "add_on_demand_leads",
-        "add_rubric_item",
-        "add_teammate",
-        "add_to_comment_campaign",
-        "add_to_connection_campaign",
-        "add_to_inmail_campaign",
-        "archive_campaign",
-        "attach_recommended_sequence",
-        "attach_sequence",
-        "bulk_enrich_with_prospeo",
-        "cancel_campaign_message_preparation",
-        "cancel_lead_import",
-        "capture_post_idea",
-        "check_rubric",
-        "commit_blueprint",
-        "confirm_harvest_job_companies",
-        "confirm_lead_list",
-        "confirm_prospeo_company_accounts",
-        "copy_sender_config",
-        "create_campaign",
-        "create_on_demand_campaign",
-        "create_on_demand_table",
-        "create_workspace",
-        "create_workflow_table",
-        "delete_column",
-        "delete_rubric_item",
-        "duplicate_campaign",
-        "enrich_with_prospeo",
-        "fill_campaign_horizon",
-        "get_or_create_direct_campaign_table",
-        "import_leads",
-        "load_csv_dnc_entries",
-        "load_csv_domains",
-        "load_csv_linkedin_leads",
-        "mark_post_published",
-        "migrate_flat_configs",
-        "pause_campaign",
-        "pause_direct_campaign",
-        "pause_on_demand_campaign",
-        "prepare_campaign_ab_test",
-        "queue_campaign_cells",
-        "queue_cells",
-        "record_campaign_review_batch",
-        "record_engage_proven_search",
-        "refill_sends",
-        "refresh_paid_inmail_credits",
-        "revise_message_template_and_rerun",
-        "save_domain_filters",
-        "save_hook_research",
-        "save_post_draft",
-        "save_rubrics",
-        "send_inbox_draft",
-        "send_inbox_manual_reply",
-        "set_active_workspace",
-        "set_campaign_waterfall_order",
-        "set_company_info",
-        "set_engage_state",
-        "set_engage_style_guide",
-        "set_headline_icp_criteria",
-        "set_sender_routing",
-        "setup_evergreen_campaigns",
-        "start_campaign",
-        "start_campaign_message_preparation",
-        "start_direct_campaign",
-        "start_on_demand_campaign",
-        "update_campaign",
-        "update_campaign_brief",
-        "update_cell",
-        "update_column",
-        "update_inbox_draft",
-        "update_post_draft",
-        "update_published_post_metrics",
-        "update_rubric_item",
-        "upsert_engage_tracked_person",
-        "upsert_rubric"
-      ],
-      "transitions": {
-        "packet_returned": "report"
-      }
-    },
-    {
-      "id": "report",
-      "description": "Present packet, itinerary, warnings, blockers, plan revision, and journal path; then stop.",
-      "allowedTools": [],
-      "onEnter": [
-        {
-          "action": "present_packet_itinerary_and_journal_path"
-        }
-      ],
-      "terminal": true
-    }
-  ],
-  "verification": {
-    "requiredProof": [
-      "sideEffects all false in get_evergreen_refill_plan response",
-      "planRevision has pr1: prefix",
-      "journalPath reported or journalWriteFailed warning surfaced",
-      "chosen evergreenRung belongs to enumeratedRungs",
-      "packet reviewed with itinerary and blockers"
-    ],
-    "notCompletionProof": [
-      "called get_evergreen_refill_plan alone",
-      "action queue exists",
-      "ready rows alone",
-      "operator wants execution"
-    ]
-  }
-}

package/skills/refill-sends-v2/SKILL.md

@@ -1,207 +0,0 @@
----
-name: refill-sends-v2
-description: Execute refill sends v2 through the fenced evergreen refill loop, with dry-run and resume support.
-visibility: public
-allowed-tools:
-  - mcp__sellable__refill_sends_v2
-  - mcp__sellable__get_refill_plan_v2
-  - mcp__sellable__get_subskill_prompt
-  - mcp__sellable__get_subskill_asset
-  - mcp__sellable__get_auth_status
-  - mcp__sellable__get_active_workspace
-  - mcp__sellable__list_workspaces
-  - mcp__sellable__get_workspace
----
-
-# Refill Sends V2
-
-Use this command for refill requests such as "refill sends", "fill evergreen
-senders", "load everyone up", "run Damiano", or "show a dry run for this
-workspace".
-
-Host command names:
-
-- Claude Code: `/sellable:refill-sends-v2`
-- Codex: `$sellable:refill-sends-v2`
-
-`refill_sends_v2` is the execution surface. In real-run mode it starts or
-resumes a fenced refill run, reads a fresh packet, executes only the packet's
-named bounded work, verifies the result, and returns either a terminal report, a
-blocked report, or an in-progress resume handle. In dry-run mode it stays
-read-only and writes only a dry-run journal.
-
-## Entry
-
-Resolve the explicit `workspaceId` from the request, automation config, or
-active workspace readback. Scheduled or autonomous usage must carry
-`workspaceId` on every tool call. If the workspace is missing or ambiguous, stop
-with `WORKSPACE_REQUIRED`; do not switch the shared active workspace.
-
-For a real refill run:
-
-```text
-refill_sends_v2({ workspaceId, intent:"auto", senderIds?, approvalMode? })
-```
-
-For read-only inspection:
-
-```text
-refill_sends_v2({ workspaceId, dryRun:true, intent:"auto", senderIds? })
-```
-
-To resume an in-progress run, pass the handle back exactly:
-
-```text
-refill_sends_v2({ workspaceId, runHandle:{runId,fence}, targetConfig, reportingContext, messageTemplateRevision? })
-```
-
-`targetConfig` and the server-issued `runHandle` are separate authorities. Keep
-both byte-for-byte through every continuation and takeover; never fold the
-rotating fence into target configuration.
-
-An approved copy change is reachable only through an explicit
-`messageTemplateRevision` object with `version:1`, `source:"user_approved"`,
-the approved `templateMarkdown`, `messageTemplateRevision` identity,
-`priorTemplateAuthorityDigest`, `nextTemplateAuthorityDigest`, 1–500 exact
-`cohortRowIds`, and `requestId`, `effectId`, and `revisionOperationId`. Pass it
-with the exact `targetConfig` and `reportingContext`; the command obtains or
-resumes the server run handle and lets the planner name
-`revise_message_template_and_rerun`. Missing or partial input means no revision.
-`forceRerun:true` on a queue operation never authorizes or implies a template
-change.
-
-After a committed and dispatched revision receipt, continue only with the
-planner-provided revision-derived `approve_messages` action. It must preserve
-the exact revision cohort as `rowSelector:{type:"rowIds",rowIds:[...]}` plus
-`approvalMode:"approve"`, the compiled readiness identity, and the canonical
-`reportingContext`, even when the ordinary sender lane is ineligible. Do not
-replace it with `queue_campaign_cells` on Approved cells; that path cannot mint
-the authoritative approval/lane-scope receipt. Require `laneScope` in the
-bounded preparation receipt before the lane is considered approved. A
-disconnected or zero-capacity sender still blocks scheduling and does not
-authorize reconnecting, campaign start, or direct send.
-
-If a stale handle loses the lease, the tool reports the holder status and the
-approximately 10 minute lockout window. Reinvoke with the current handle or wait
-for lease expiry; never guess a fence.
-
-The default `intent:"auto"` inspects `managed_waterfall`,
-`dashboard_evergreen`, and `active_campaign` lane sources. Report the lane
-source and lane chain as proof for every selected sender.
-Connection-only evergreen lanes are invite-only refill targets. When the packet
-or campaign proof shows exactly `["send_invite"]`, report and execute only
-`selectedLane:"send_invite"` work; do not infer DM, InMail, Sales Nav cascade,
-paid-credit refresh, message generation, follow-up, sequence mutation,
-launch/start beyond packet authority, scheduler writes, or direct sends.
-
-If membership blocks a workspace read, report the structured
-`workspace_access` blocker instead of retrying auth or switching workspaces.
-
-## Authority
-
-The run may execute only packet-named bounded work:
-
-- approve generated messages that are ready for review (`approve_messages`);
-- enrich the next batch of unenriched rows (`enrich_more`);
-- copy leads already found into the campaign table (`reconcile_source_copy`);
-- re-run errored enrichment/message cells (`rerun_errored_cells`);
-- find more leads via this campaign's original source (`add_leads_same_source`)
-  only for mechanical same-source continuations;
-- start the paused campaign so ready rows can schedule (`start_campaign`) only
-  when the campaign is in the packet's pinned lane chain;
-- refresh paid InMail credit facts during bootstrap and once per scheduler-wait
-  entry when the packet requires it.
-- apply `revise_message_template_and_rerun` only when the packet contains the
-  complete explicit user-approved revision envelope and exact fenced target.
-- after that revision commits, apply only its exact-row, readiness-bound
-  `approve_messages` continuation and require the returned lane-scope receipt.
-
-The loop records planned -> did -> outcome before and after every foreign
-mutation. It refuses stale packets by fingerprint and validates packet
-coherence before dispatch. The planner owns repair decisions: if a batch needs
-repair, the next packet names the repair rung; the loop bounds and refuses, it
-does not improvise fixes.
-
-Do not create campaigns, switch provider families, lower thresholds, write
-scheduler fields, send messages, archive/delete campaigns, or mutate
-brief/filter/message/sequence/sender config unless a separate exact approval
-packet explicitly authorizes that work. In short: no campaign creation, no
-provider-family switch, no threshold lowering, no scheduler writes, no
-launch/send/archive/delete, and no brief/filter/message/sequence/sender
-mutation.
-
-## Continuations
-
-Sales Nav and Prospeo source continuations that are not yolo-safe are blocked
-as executable scoped handoffs. The report will include text shaped like:
-
-```text
-$sellable:create-campaign [campaignId]
-```
-
-That handoff is run in a separate thread only after explicit approval. Scope is
-strict: add leads through this campaign's existing source, keep the same
-saved-search identity, import mode `add` into the same source list, and do
-source work only. It is never a new campaign, provider-family switch, brief
-change, rubric change, message change, sequence change, or sender change.
-
-## Verification
-
-The loop verifies whole rows before replanning. It reattaches to an own active
-prep job instead of re-dispatching, waits on foreign prep jobs without adopting
-their outcomes, waits on active enrichment/import work by rereading the packet,
-and treats capped scheduler capacity as complete.
-
-Scheduler waits are cross-invocation. Each tool call polls briefly under the
-host guard, heartbeats the run lease, and may return:
-
-```text
-{ status:"in_progress", runId, fence, gate, guidance }
-```
-
-Reinvoke with that handle. The approximately five minute scheduler budget is at
-the run level, not one tool call. A window-closed or loaded-awaiting scheduler
-report must include remaining-ready count, exact expected pickup time, and the
-resume handle; never treat bare "awaiting scheduler" copy as a final answer.
-Scheduler-run receipt interpretation still applies to terminal progress:
-`cellsConsidered is allocation-attempt count`, not total ready supply, while
-`readyCellsFound` is ready inventory found before prefilters. Inspect
-`campaignScopeSummary` before assuming the selected refill campaign/table was
-included; if absent, do not infer that target was ready-but-blocked. Interpret
-`prefiltered`, `skipped`, and `deferred` separately. For ready closed-InMail
-cells with stale paid-credit reasons, route to
-`refresh_paid_inmail_credits_then_rerun` once, then rerun/status.
-`wait_for_capacity_or_window` means report loaded/capped/waiting and do not
-source or prep more rows; `no_ready_cells_continue_refill_prep` means return to
-the refill/prep ladder. Do not treat `cellsScheduled:0` alone as failure.
-
-After the first prep batch, read the conversion-verdict journal line. It is
-rendered from packet facts: `supplyCensus`, `censusReason`, and
-`pipelineDiagnosis.firstFailing`. If the verdict is honest rubric failure, the
-human decision is to update the rubric or change lead source; refill does not
-mutate those automatically.
-
-## Results
-
-Terminal reasons are:
-
-- `complete`
-- `capped_by_scheduler`
-- `loaded_awaiting_scheduler`
-- `lanes_exhausted`
-- `blocked`
-- `no_refillable_campaigns`
-- `not_an_evergreen_workspace`
-
-Report campaign names and sender names first, ids second. Include the terminal
-reason or resume handle, lane source, lane chain, chosen label with token
-secondary, plan revision, journal path, blocked continuation packets, and
-firstFailing checklist when present.
-
-Preserve `refill_reporting.v2` exactly in progress, continuation, replay, and
-terminal results. Do not recompute its semantic counts or drop live-preparation
-epoch, snapshot sequence, reset reason, watermark, blockers, compatibility, or
-terminal fields. Never surface raw prospect or message-copy fields.
-
-Real-run journals live under `~/.sellable/refill/runs` by default and append an
-index line. Dry runs include the dry marker and do not create run records.

package/skills/refill-sends-v2-workflow/SKILL.md

@@ -1,171 +0,0 @@
----
-name: refill-sends-v2-workflow
-description: Internal execution workflow for refill sends v2 fenced runs.
-visibility: internal
-allowed-tools:
-  - mcp__sellable__refill_sends_v2
-  - mcp__sellable__get_refill_plan_v2
-  - mcp__sellable__get_subskill_prompt
-  - mcp__sellable__get_subskill_asset
-  - mcp__sellable__get_auth_status
-  - mcp__sellable__get_active_workspace
-  - mcp__sellable__list_workspaces
-  - mcp__sellable__get_workspace
----
-
-# Refill Sends V2 Workflow
-
-This internal workflow mirrors the run-record gates enforced by
-`refill_sends_v2`: bootstrap, plan, execute, verify, and report. Dry runs stay
-read-only. Real runs execute only packet-named bounded work under a fenced run
-lease and return terminal, blocked, or in-progress results.
-
-Runtime flow asset: after loading this prompt, load
-`get_subskill_asset({ subskillName: "refill-sends-v2-workflow", assetPath: "core/flow.v1.json" })`
-through MCP, continue chunks until `hasMore:false`, parse the JSON, and verify
-`workflow:"refill-sends-v2-workflow"` with a `v1` version before driving the
-loop. If the asset cannot load or parse, stop with
-`blocked:refill_sends_v2_workflow_asset_unavailable`; do not emulate it from
-local files or memory.
-
-## G0 Bootstrap
-
-Resolve request-scoped `workspaceId` using read-only auth and workspace tools.
-Scheduled or autonomous runs must not rely on implicit workspace state.
-
-Start or resume the execution loop:
-
-```text
-refill_sends_v2({ workspaceId, intent:"auto", senderIds?, approvalMode?, runHandle?, targetConfig?, reportingContext?, messageTemplateRevision? })
-```
-
-Use `dryRun:true` only when the user asked for read-only inspection. A dry run
-writes a journal only. A real run creates or resumes a run record, refreshes
-paid-credit trust only when packet facts require it, and returns a resume handle
-when the current invocation must pause.
-
-## G1 Plan
-
-The loop reads `get_refill_plan_v2` with runState fed back from the run record.
-It captures `planRevision`, `stateRevision`, and `targetShapeRevision`, then
-validates the packet before dispatch. Packet coherence is required: fingerprint
-shape, tool input completeness, lane-chain membership, census-vs-rung
-consistency, and terminal/action exclusivity. An incoherent packet is replanned
-once, then blocked as `packet_incoherent`.
-
-The packet's `supplyCensus`, `censusReason`, and `pipelineDiagnosis` checklist
-are the reason for the next rung. Repair is replan-driven: the planner names
-the repair rung, such as re-run errored enrichment/message cells
-(`rerun_errored_cells`), approve generated messages that are ready for review
-(`approve_messages`), or start the paused campaign so ready rows can schedule
-(`start_campaign`). The loop bounds and refuses repair loops; it never invents
-a fix list.
-
-The exact `RefillTargetConfigV1` and server `RefillRunHandleV1` stay separate.
-If and only if the caller supplies a complete explicit
-`messageTemplateRevision` with `source:"user_approved"`, approved markdown,
-prior/new authority digests, a bounded row cohort, and request/effect/revision-
-operation IDs, the planner may name `revise_message_template_and_rerun`.
-Missing/partial input blocks before dispatch; `forceRerun` never synthesizes
-revision authority.
-
-Connection-only evergreen packets are invite-only. If the selected lane or
-campaign proof is exactly `["send_invite"]`, the workflow may refill only
-`selectedLane:"send_invite"` capacity. Do not treat that lane as a DM, InMail,
-Sales Nav cascade, paid-credit refresh, generated-message requirement,
-follow-up branch, sequence-repair task, scheduler write, launch/send, or
-provider-family continuation.
-
-Use plain-language labels first and tokens second, for example "copy leads
-already found into the campaign table (`reconcile_source_copy`)".
-
-## G2 Execute
-
-The loop executes only the packet head action whose fingerprint was captured at
-G1. Stale packets are refused and replanned.
-
-Allowed packet-named work:
-
-1. start the paused campaign so ready rows can schedule (`start_campaign`) when
-   the campaign is in the pinned lane chain;
-2. approve generated messages that are ready for review (`approve_messages`);
-3. enrich the next batch of unenriched rows (`enrich_more`);
-4. copy leads already found into the campaign table (`reconcile_source_copy`);
-5. re-run errored enrichment/message cells (`rerun_errored_cells`);
-6. find more leads via this campaign's original source
-   (`add_leads_same_source`) for mechanical same-source continuations;
-7. wait for the scheduler to pick up ready rows (`wait_for_scheduler`).
-8. apply the exact approved message-template revision
-   (`revise_message_template_and_rerun`) and preserve its domain replay receipt.
-
-Never create campaigns, switch providers, lower thresholds, write scheduler
-fields, send/archive/delete, or mutate brief/filter/message/sequence/sender
-config inside refill.
-
-Sales Nav and Prospeo continuations that need human source work are blocked as
-scoped handoffs:
-
-```text
-$sellable:create-campaign [campaignId]
-```
-
-The handoff scope is source work only: same saved-search identity, import mode
-`add` into the same source list, no new campaign, no provider-family switch, and
-no brief/rubric/message/sequence/sender changes without a separate approval
-packet.
-
-## G3 Verify
-
-Verification is whole-row and bounded. The loop records planned -> did ->
-outcome, then verifies before replanning.
-
-- Own active prep jobs are reattached by `requestSource` and `requestHash`; do
-  not re-dispatch prep while the job is active.
-- Foreign prep jobs are waited out or blocked as `foreign_prep_active`; their
-  outcomes are not adopted.
-- Active enrichment/import work is handled by bounded packet rereads.
-- The conversion verdict after the first prep batch is journaled from packet
-  facts. The plan gate withholds a second unproven prep batch when
-  `censusReason` is `conversion_blocked`.
-- Honest rubric failure means a human updates the rubric or changes lead source.
-- Capped scheduler capacity is complete.
-
-Scheduler wait is cross-invocation. If the tool returns `in_progress` with
-sweep guidance, re-invoke `refill_sends_v2` with `{runId, fence}`. The scheduler
-budget is cumulative at the run level. Zero pickup after a confirmed sweep is
-debugged from `pipelineDiagnosis`; it is not waited out forever.
-Scheduler-run receipt interpretation still applies to terminal progress:
-`cellsConsidered is allocation-attempt count`, not total ready supply, while
-`readyCellsFound` is ready inventory found before prefilters. Inspect
-`campaignScopeSummary` before assuming the selected refill campaign/table was
-included; if absent, do not infer that target was ready-but-blocked. Interpret
-`prefiltered`, `skipped`, and `deferred` separately. For ready closed-InMail
-cells with stale paid-credit reasons, route to
-`refresh_paid_inmail_credits_then_rerun` once, then rerun/status.
-`wait_for_capacity_or_window` means report loaded/capped/waiting and do not
-source or prep more rows; `no_ready_cells_continue_refill_prep` means return to
-the refill/prep ladder. Do not treat `cellsScheduled:0` alone as failure.
-
-## G4 Report
-
-Completion proof is the run record at `g4_terminal` with a named doneReason and
-journal evidence showing planned -> did -> outcome plus a terminal block and
-index line. A plan packet alone is not completion proof.
-
-Every progress, continuation, replay, and terminal projection carries the
-canonical `refill_reporting.v2` DTO without rebuilding it. Preserve live epoch,
-sequence, reset, watermark, semantic/compatibility counts, blockers, and
-terminal outcome while redacting raw copy/prospect fields.
-
-Terminal reasons are `complete`, `capped_by_scheduler`,
-`loaded_awaiting_scheduler`, `lanes_exhausted`, `blocked`,
-`no_refillable_campaigns`, and `not_an_evergreen_workspace`.
-
-`loaded_awaiting_scheduler` remains the run-record token, but report copy must
-include remaining-ready count, exact expected pickup time, and the resume
-handle. Do not render bare "loaded, awaiting scheduler" as a final answer.
-
-Report campaign names and sender names first, ids second. Include lane source,
-lane chain, chosen label with token secondary, plan revision, terminal reason or
-resume handle, journal path, blocked continuation packets, and firstFailing
-checklist when present.