@oxygen-agent/cli 1.1011.98 → 1.1011.322

package/dist/index.js

@@ -8,12 +8,13 @@ import { stdin as input, stdout as output } from "node:process";
 import { fileURLToPath, pathToFileURL } from "node:url";
 import { Command, CommanderError, Option } from "commander";
 import { registerUgcCommands } from "./ugc-commands.js";
+import { registerConnectorsCommands } from "./connectors-commands.js";
 import { registerKnowledgeRepositoryCommands } from "./knowledge-repository-commands.js";
 import { registerVisualCommands } from "./visual-commands.js";
 import { renderPrimaryProviderBoard } from "./admin-primary-providers-render.js";
 import { registerFunctionsCommands } from "./functions-commands.js";
 import { STREAMED_FILE_IMPORT_MIN_BYTES, putImportFileStream, rowsForStreamedImportTarget, scanStreamedImportFile, shouldStreamFileImport, } from "./streamed-file-import.js";
-import { applyOxygenHelp, enableCommandSuggestions, unknownCommandHint, unknownOptionHint } from "./help.js";
+import { applyOxygenHelp, argvRequestsJson, commanderUsageFailure, enableCommandSuggestions, unknownCommandHint, unknownOptionHint, withoutHelpForUnknownCommand, } from "./help.js";
 import { buildCommandManifest, getCommandManifestEntry, searchCommandManifest, suggestCommandNames, } from "./command-manifest.js";
 import { AGENCY_DIRECTORY_REGIONS, AGENCY_DIRECTORY_SERVICES, COLLAB_GATE_KINDS, COLLAB_GATE_PROSE, COLLAB_SUBJECT_KINDS, COLLAB_SUBJECT_KINDS_PROSE, COLLAB_SUBJECT_LABELS, COLLAB_SUBJECT_PROSE, GATE_KIND_SUBJECTS, describeWorkflowStatusChange, formatCellForDisplay, formatCopilotPlanDuration, formatCopilotPlanSeconds, formatPublicBudgetScopes, SUBJECT_PATH_FORMS_PROSE, formatSubjectPath, exitCodeForOxygenError, parseSubjectPath, parseSubjectRef, parseWorkflowStatusChange, chunk, isVersionGreater, isVersionLess, KNOWLEDGE_BOOTSTRAP_MAX_CREDITS, MAX_CLI_JSON_BODY_BYTES, MAX_MCP_TOOL_NAME_LENGTH, normalizeCopilotPlanStepStatus, OXYGEN_CAPABILITY_ROUTES, OXYGEN_VERSION, OxygenError, getCapabilityRouteMatch, inferUserCapabilityRoute, parseKnowledgePageMarkdown, PLAN_LIMITS, serializeCapabilityRoute, sleep, success, TAG_KINDS_PROSE, toFailure, workflowMcpToolName, } from "@oxygen/shared";
 import { PURCHASABLE_PLAN_KEYS, planVolumeBonusPercent, resolveBasePricingPlan } from "@oxygen/shared/billing";
@@ -21,6 +22,7 @@ import { TAG_COLORS } from "@oxygen/shared/select-options";
 import { PUBLIC_WEBHOOK_INGRESS_PER_TARGET_PER_MINUTE } from "@oxygen/shared/plan-band";
 import { AI_COLUMN_CREDITS, AI_COLUMN_WEB_SEARCH_TYPICAL_CREDITS } from "@oxygen/shared/pricing-sheet";
 import { LINKEDIN_SENDER_LIMIT_DEFAULTS, LINKEDIN_SENDER_LIMIT_MAXIMUMS, } from "@oxygen/shared/linkedin-sequences";
+import { SEQUENCE_LIFECYCLES, sequenceDisplayStatus } from "@oxygen/shared/sequence-lifecycle";
 import { operationPath } from "@oxygen/shared/contracts/operations";
 import { SENDER_LIMITS_SET_OPERATION } from "@oxygen/shared/contracts/sender-limits";
 import { addContractFlags } from "./contract-flags.js";
@@ -38,7 +40,7 @@ import { ensureFreshCliForApiUrl, requestOxygen } from "./http-client.js";
 import { acquireMirrorLock, clearConflictFiles, deletePageFile, emptyMirrorState, findMirrorSlugByPageId, isFileDirty, listConflictFiles, listLocalMirrors, localPageSha256, markMirrorStale, mirrorExists, pageFilePath, planMirrorPush, purgeMirror, resetMirrorForFullResync, quarantineDirtyFile, readMirrorState, releaseMirrorLock, resolveDefaultConfigDir, resolveMirrorDir, writeGeneratedIndexFile, writeGeneratedLogFile, writeMirrorState, writePageFile, } from "./knowledge-mirror.js";
 import { waitForCliRun } from "./run-wait.js";
 import { assertModeFlagsExclusive, parseKeyValuePairs, parseJsonObject, readJsonObjectOption, readNonNegativeInt, readPositiveInt, readRecordString, resolveLiveDryRunMode, } from "./cli-values.js";
-import { formatAiPromptPreviewNotice, formatColumnReferenceNotices, } from "./column-run-notices.js";
+import { formatAiPromptPreviewNotice, formatColumnReferenceNotices, formatEnrichmentInputMappingNotice, formatProviderLaneNotices, } from "./column-run-notices.js";
 import { runLocalCustomHttpColumn } from "./local-custom-http-column.js";
 import { formatSearchAiFilterTotalsNotice } from "./search-ai-filter-notice.js";
 import { formatInboxNeedsReplyNotice } from "./inbox-needs-reply-notice.js";
@@ -867,6 +869,13 @@ function writeManagedProviderAvailabilityNotice(data) {
     if (!payload)
         return;
     const availability = asPayloadRecord(payload.provider_availability);
+    // `columns run --dry-run` and `enrich-column preview` name their lanes: one
+    // line per lane that cannot run, led by the verdict (OXP-1.14.12).
+    if (availability && Array.isArray(availability.lanes)) {
+        for (const line of formatProviderLaneNotices(availability))
+            process.stderr.write(`${line}\n`);
+        return;
+    }
     if (availability) {
         const providers = asPayloadRecord(availability.providers) ?? {};
         for (const [provider, entry] of Object.entries(providers)) {
@@ -1159,7 +1168,7 @@ function writeAiPromptPreviewNotice(data) {
         process.stderr.write(`${notice}\n`);
 }
 function writeColumnReferenceNotices(data) {
-    for (const notice of formatColumnReferenceNotices(data)) {
+    for (const notice of [...formatColumnReferenceNotices(data), ...formatEnrichmentInputMappingNotice(data)]) {
         process.stderr.write(`${notice}\n`);
     }
 }
@@ -2360,10 +2369,32 @@ function buildPublishingPostCreateBody(options) {
         body.ugc_participation_id = ugcParticipationId;
     }
     const xContent = buildPublishingXContent(options, { forMerge: false });
-    if (content || xContent)
-        body.content = { ...(content ?? {}), ...(xContent ?? {}) };
+    const firstComment = readPublishingFirstComment(options);
+    if (content || xContent || firstComment) {
+        body.content = { ...(content ?? {}), ...(xContent ?? {}), ...(firstComment ? { first_comment: firstComment } : {}) };
+    }
     return body;
 }
+/**
+ * `--first-comment` / `--clear-first-comment`: the comment to set, null to remove
+ * it (update only), or undefined when neither flag was passed. The API refuses a
+ * first comment on a provider that cannot post one (publishing_first_comment_unsupported),
+ * judging the post's stored provider too, so the CLI does not keep its own list.
+ */
+function readPublishingFirstComment(options) {
+    if (options.firstComment !== undefined && options.clearFirstComment) {
+        throw new OxygenError("invalid_request", "Choose --first-comment or --clear-first-comment, not both.", { exitCode: 2 });
+    }
+    if (options.clearFirstComment)
+        return null;
+    if (options.firstComment === undefined)
+        return undefined;
+    const text = options.firstComment.trim();
+    if (!text) {
+        throw new OxygenError("invalid_request", "--first-comment needs the comment text. To remove a post's first comment, use --clear-first-comment on `publishing posts update`.", { exitCode: 2 });
+    }
+    return text;
+}
 /**
  * The X flags as content keys (see the API's X content contract). On update they
  * become a `content_merge` so the rest of the stored content is kept; there
@@ -2471,8 +2502,17 @@ function buildPublishingPostUpdateBody(options) {
         body.content = content;
     const merge = readOption(options.contentMergeJson);
     const xContent = buildPublishingXContent(options, { forMerge: true });
-    if (merge || xContent)
-        body.content_merge = { ...(merge ? parseJsonObject(merge) : {}), ...(xContent ?? {}) };
+    // A merge key, so the post's media and other content survive the change.
+    const firstComment = readPublishingFirstComment(options);
+    if (merge || xContent || firstComment !== undefined) {
+        body.content_merge = {
+            ...(merge ? parseJsonObject(merge) : {}),
+            ...(xContent ?? {}),
+            // Clearing also nulls the legacy camelCase key the worker still falls back to.
+            ...(firstComment === null ? { first_comment: null, firstComment: null } : {}),
+            ...(typeof firstComment === "string" ? { first_comment: firstComment } : {}),
+        };
+    }
     if (options.confirmNotPublished)
         body.confirm_not_published = true;
     return body;
@@ -3826,9 +3866,10 @@ export function createProgram() {
     }));
     program
         .command("status")
-        .description("Compare the local Oxygen CLI version against the active profile's deployed Oxygen API. "
+        .description("Compare the local Oxygen CLI version against the active profile's deployed Oxygen API. Read-only, 0 credits. "
         + "`compatible` is the field that matters: false means commands are refused until the CLI updates. "
-        + "`in_sync` and `skew` only report version distance; a CLI ahead of the API is normal.")
+        + "`in_sync` and `skew` compare reported versions. A CLI may be ahead during a rollout; "
+        + "if the difference persists, share the status SHA with support.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
         await handleAsyncAction("status", options, async () => {
@@ -3878,14 +3919,14 @@ export function createProgram() {
         await handleOrgsListAction(options);
     }))
         .addCommand(new Command("use")
-        .description("Select the active organization for this CLI profile.")
+        .description("Select the active organization for this CLI profile. Apps connected with OAuth (ChatGPT, Claude…) keep their own default workspace: `oxygen connectors`.")
         .argument("<organization>", "Organization id, Clerk org id, or slug returned by orgs list.")
         .option("--json", "Print a JSON envelope.")
         .action(async (organization, options) => {
         await handleOrgUseAction(organization, options, "orgs use");
     }))
         .addCommand(new Command("select")
-        .description("Alias for orgs use.")
+        .description("Alias for orgs use: this CLI profile only. For ChatGPT, Claude or another connected app, use `oxygen connectors set`.")
         .argument("<organization>", "Organization id, Clerk org id, or slug returned by orgs list.")
         .option("--json", "Print a JSON envelope.")
         .action(async (organization, options) => {
@@ -4364,7 +4405,7 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         .command("db")
         .description("Tenant database commands.")
         .addCommand(new Command("status")
-        .description("Show the current database provider and status. Hosting is included in your plan; Neon IDs on a PostgreSQL row are historical lineage. Staff can pass global --org to inspect another org.")
+        .description("Read-only, 0 credits: show the current database host and status, including historical Neon IDs, recorded region labels, and plan-included hosting; staff can pass global --org.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
         await handleAsyncAction("db status", options, () => requestOxygen("/api/cli/db/status"));
@@ -4499,7 +4540,7 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         });
     }))
         .addCommand(new Command("cost-policy")
-        .description("Show the historical Neon cost-policy record. PostgreSQL hosting has no Neon endpoint controls.")
+        .description("Read-only, 0 credits. Show the retired Neon cost-policy status. Its managed field describes the policy, not database hosting; PostgreSQL has no per-workspace sleep control.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
         await handleAsyncAction("db cost-policy", options, () => requestOxygen("/api/cli/db/cost-policy"));
@@ -4714,7 +4755,7 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
     }))
         .addCommand(new Command("create")
         .description("Create a personal Publishing post. Use --ugc-participation-id to save it into one program as an unapproved draft; otherwise it defaults to scheduled and publishes only after approval.")
-        .requiredOption("--publish-at <iso>", "ISO date-time when the post should publish, e.g. 2026-09-15T10:00:00+02:00. A bare local time with no offset is stored as UTC, never converted into --timezone, so pass an offset or Z to fix the instant; --timezone only changes how it displays.")
+        .requiredOption("--publish-at <iso>", "When the post publishes, e.g. 2026-10-06T09:00:00+02:00. With Z or an offset it is that exact instant; without one (2026-10-06T09:00) it is wall-clock time in --timezone.")
         .option("--provider <provider>", "Publishing provider: linkedin, x, instagram, tiktok, facebook, or youtube. Defaults to linkedin. LinkedIn publishes through --sender; every other provider publishes through a connected account (--provider-connection), which the worker needs before it can deliver.")
         .option("--channel <channel>", "Publishing channel override. Defaults to provider.")
         .option("--sender <sender_account_id>", "LinkedIn sender account id. Required for LinkedIn before the worker can publish.")
@@ -4723,8 +4764,9 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         .option("--text <text>", "Post text. On LinkedIn, tag a person with @<public-identifier> and a company page with @<handle> from its linkedin.com/company/<handle> URL.")
         .option("--text-file <path>", "Read post text from a local file.")
         .option("--content-json <json>", "Structured content. Use media_asset_ids for Oxygen uploads. LinkedIn attachments require [{content:<base64>,content_type:<MIME>,filename:<name>}]; content.mentions is rejected, so put verified @<public-identifier> values in --text. X options have their own flags (--thread-post, --poll-option, --reply-settings, --alt-text, --photo-tag); raw X API keys can still ride in composio.arguments.")
+        .option("--first-comment <text>", "Comment OXYGEN posts right after the post, e.g. the link (LinkedIn, X, Instagram, YouTube). Wins over first_comment in --content-json.")
         .option("--composio-action <slug>", "Override the Composio action slug for this scheduled post.")
-        .option("--timezone <tz>", "Display timezone for the scheduled date. Defaults to the LinkedIn sender's own timezone when --sender is set, else UTC.")
+        .option("--timezone <tz>", "IANA zone (Europe/Berlin) the post is shown in and a --publish-at without an offset is read in. Defaults to the LinkedIn sender's own timezone when --sender is set, else UTC.")
         .option("--status <status>", "draft or scheduled. Defaults to scheduled. A draft sits outside the queue until `publishing posts approve` schedules and arms it in one step; scheduled is queued for its publish time and still waits for approval.")
         .option("--draft", "Create as a draft instead of scheduled.")
         .option("--ugc-participation-id <id>", "Also enroll this personal post in one active creator participation. It is always saved as an unapproved draft; omit --approved.")
@@ -4746,14 +4788,14 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         }));
     }))
         .addCommand(new Command("get")
-        .description("Get one scheduled post with resolved media previews, its LinkedIn video cover, and attempt history. For an X post, publish_plan lists every post that will be sent, in order, with media, alt text, poll and reply settings (free); for a LinkedIn post that tags a company page, it shows the text sent, each company tag as its page id, once `publishing posts approve` has resolved the tags (before approval it is absent). Open web_url to preview the post as it will look on LinkedIn or X.")
+        .description("Get one scheduled post with the sender account it publishes from (id, name, profile URL), resolved media previews, its LinkedIn video cover, and attempt history. For an X post, publish_plan lists every post that will be sent, in order, with media, alt text, poll and reply settings (free); for a LinkedIn post that tags a company page, it shows the text sent, each company tag as its page id, once `publishing posts approve` has resolved the tags (before approval it is absent). Open web_url to preview the post as it will look on LinkedIn or X.")
         .argument("<post_id>", "Scheduled post id.")
         .option("--json", "Print a JSON envelope.")
         .action(async (postId, options) => {
         await handleAsyncAction("publishing posts get", options, () => requestOxygen(`/api/cli/publishing/posts/${encodeURIComponent(postId)}`));
     }))
         .addCommand(new Command("update")
-        .description("Update an editable draft, scheduled, or failed post.")
+        .description("Update an editable draft, scheduled, or failed post. Changing its text or content, the first comment included, revokes approval on an approved post: approve it again.")
         .argument("<post_id>", "Scheduled post id.")
         .option("--provider <provider>", "Publishing provider: linkedin, x, instagram, tiktok, facebook, or youtube.")
         .option("--channel <channel>", "Publishing channel override.")
@@ -4763,9 +4805,11 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         .option("--text <text>", "Post text. On LinkedIn, tag a person with @<public-identifier> and a company page with @<handle> from its linkedin.com/company/<handle> URL.")
         .option("--text-file <path>", "Read post text from a local file.")
         .option("--content-json <json>", "Structured content. Use media_asset_ids for Oxygen uploads. LinkedIn attachments require [{content:<base64>,content_type:<MIME>,filename:<name>}]; content.mentions is rejected, so put verified @<public-identifier> values in --text. This replaces the existing content object; use --content-merge-json or the X flags to change single keys.")
+        .option("--first-comment <text>", "Set the comment OXYGEN posts right after the post, keeping the rest of its content. Revokes approval on an approved post.")
+        .option("--clear-first-comment", "Remove the first comment. Revokes approval on an approved post.")
         .option("--composio-action <slug>", "Override the Composio action slug for this scheduled post.")
-        .option("--publish-at <iso>", "ISO date-time when the post should publish.")
-        .option("--timezone <tz>", "Display timezone for the scheduled date.")
+        .option("--publish-at <iso>", "When the post publishes. With Z or an offset it is that exact instant; without one it is wall-clock time in --timezone, else the post's own timezone.")
+        .option("--timezone <tz>", "IANA zone the post is shown in and a --publish-at without an offset is read in. Unchanged when omitted.")
         .option("--status <status>", "draft or scheduled.")
         .option("--thread-post <text>", "X: text of the next post in a thread (posts 2, 3, ... in order). Repeatable.", collectRepeatable, [])
         .option("--thread-media <position=media_id>", "X: attach an uploaded media id to thread post N (2 or later), e.g. 2=<media_id>. Repeatable.", collectRepeatable, [])
@@ -4950,11 +4994,11 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         .description("Accept a draft variant into the publish queue. The post is created needs-approval — approve it separately before it can publish.")
         .argument("<draft_id>", "Post draft id.")
         .option("--variant <i>", "Which variant to accept (0-based). Defaults to 0.")
-        .option("--publish-at <iso>", "ISO date-time to schedule the post for. Defaults to now (still needs approval).")
+        .option("--publish-at <iso>", "ISO date-time to schedule the post for; without an offset it is wall-clock time in --timezone. Defaults to now (still needs approval).")
         .option("--channel <channel>", "Channel override. Defaults to the draft's first target channel.")
         .option("--sender <sender_account_id>", "LinkedIn sender account id.")
         .option("--provider-connection <connection_id>", "Oxygen integration connection id for Composio-backed providers.")
-        .option("--timezone <tz>", "Display timezone for the scheduled date.")
+        .option("--timezone <tz>", "IANA zone the post is shown in and a --publish-at without an offset is read in. Defaults to UTC.")
         .option("--json", "Print a JSON envelope.")
         .action(async (draftId, options) => {
         await handleAsyncAction("publishing drafts accept", options, () => requestOxygen(`/api/cli/publishing/drafts/${encodeURIComponent(draftId)}/accept`, {
@@ -5223,7 +5267,7 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         .addHelpText("after", "\nExamples (stored snapshots, 0 credits, no provider call):\n  oxygen publishing analytics summary --channel linkedin --range 30d --sort impressions --json\n  oxygen publishing analytics timeseries --channel linkedin --range 30d --tz Europe/Berlin --json\n\nTotals, leader and trends combine every posting account; `accounts` lists them and `--account <key>` counts only the ones you name. `top_posts[].account` names each post's author.\nWhy a metric is null: every null carries a reason in `null_reasons`:\n  not_exposed_by_provider   the rail OXYGEN currently reads through never returns it (`capabilities.metrics.<metric>.reason` names the limit)\n  not_synced_yet            no background snapshot has landed yet\n  not_returned_by_provider  snapshots exist but the provider left it out (LinkedIn shows impressions only to the post's author)\nSee also: the oxygen-linkedin-marketing product skill (`oxygen skills install`) for reading LinkedIn performance.\n"))
         .addCommand(new Command("import")
         .description("Bulk-load scheduled posts from a .csv or .json file. Dry-run by DEFAULT: it parses, lints, and reports invalid rows while writing nothing. Pass --approved to actually write. Imported posts land as drafts that still need approval — import never approves and never publishes. A row whose idempotency_key was already used is skipped, so re-importing the same file cannot duplicate the queue.")
-        .requiredOption("--file <path>", "Path to a .csv (header row) or .json file ([rows] or { rows: [...] }).")
+        .requiredOption("--file <path>", "Path to a .csv (header row) or .json file ([rows] or { rows: [...] }). Columns: content_text, publish_at, and optionally sender_account_id, provider, timezone, title, first_comment, tags, idempotency_key. A publish_at without Z or an offset is wall-clock time in the row's timezone, else its sender's, else UTC.")
         .option("--dry-run", "Parse, lint, and report without writing. Default.")
         .option("--approved", "Write the parsed rows into the queue as needs-approval drafts.")
         .option("--tags <tags>", "Comma-separated workspace tags for every imported post.")
@@ -5392,9 +5436,10 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
     }))
         .addCommand(new Command("list")
         .description("List the dashboards saved in this workspace.")
+        .option("--tag <tag>", "Only dashboards carrying this workspace tag.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
-        await handleAsyncAction("dashboards list", options, () => requestOxygen("/api/cli/dashboards"));
+        await handleAsyncAction("dashboards list", options, () => requestOxygen(`/api/cli/dashboards${options.tag ? `?tag=${encodeURIComponent(options.tag)}` : ""}`));
     }))
         .addCommand(new Command("create")
         .description("Create a saved dashboard. It starts with one empty tab; add widgets to it with `dashboards widgets add`.")
@@ -6402,7 +6447,7 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
     })));
     program
         .command("signals")
-        .description("The Signals primitive: the typed GTM intent-event stream — record signals, list the raw event feed, inspect the type registry, and read the ranked leads-to-contact-today queue. Who to contact first today: signals leads-today.")
+        .description("The Signals primitive: record intent events, read the event feed and type registry, and rank leads with signals leads-today. Tag a registered type with `oxygen tags attach signal_type <type> --tags <labels>`.")
         .addCommand(new Command("list")
         .description("List the raw GTM signal-event feed newest-first (website_visit / profile_view / post_reaction / new_follower), each resolved onto the person it attached to. Read-only.")
         .option("--types <types>", "Comma-separated signal types to include. Defaults to all four.")
@@ -6413,10 +6458,11 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         await handleAsyncAction("signals list", options, () => requestOxygen(buildSignalsListPath(options)));
     }))
         .addCommand(new Command("registry")
-        .description("Show the signal-type registry: each registered type with its intent weight and capture status (all four registered types are live end-to-end — website_visit via the RB2B webhook, the engagement family via the engagement→signal bridge). Read-only.")
+        .description("Show registered signal types with intent weight, capture status, and workspace tags. Tag a type with `oxygen tags attach signal_type <type> --tags <labels>`. Read-only.")
+        .option("--tag <tag>", "Only signal types carrying this workspace tag; use tags attach to set it.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
-        await handleAsyncAction("signals registry", options, () => requestOxygen("/api/cli/signals/registry"));
+        await handleAsyncAction("signals registry", options, () => requestOxygen(`/api/cli/signals/registry${options.tag ? `?tag=${encodeURIComponent(options.tag)}` : ""}`));
     }))
         .addCommand(new Command("record")
         .description("Record one inbound GTM signal (website_visit, profile_view, post_engager, new_follower). Internal write — free, no approval. Idempotent on --external-event-id.")
@@ -8537,11 +8583,11 @@ Examples:
     }))
         .addCommand(knowledgeBootstrapCommand)
         .addCommand(new Command("synthesize")
-        .description("Synthesize knowledge from workspace evidence (one low-cost AI call): campaign learnings from auto-filed outreach outcomes, or a voice guide from sent messages. Previews by default; --approved writes the result.")
-        .option("--kind <kind>", "What to synthesize: campaign_learnings (default) or voice.", "campaign_learnings")
+        .description("Synthesize knowledge from workspace evidence (one low-cost AI call, priced as one low-reasoning AI column cell): campaign learnings from auto-filed outreach outcomes, or your writing voice (a voice guide) learned from your sent LinkedIn and WhatsApp messages. Every run spends credits, the preview included, unless fewer than 3 sent messages exist (insufficient_source_messages, nothing charged); without --approved nothing is saved. To keep the guide a preview showed, pass its body back with --approved --body (no new AI call); --approved alone synthesizes and charges again. A pinned voice guide is the canonical voice at once and grounds message, reply, sequence and post drafts and AI columns.")
+        .option("--kind <kind>", "What to synthesize: campaign_learnings (default) or voice (your writing voice from sent LinkedIn and WhatsApp messages).", "campaign_learnings")
         .option("--sequence <sequence_id>", "Scope campaign learnings to one sequence's learnings page. Omit for the org-wide [[outreach-learnings]] page.")
         .option("--approved", "Write the synthesized result (learnings page revision / pinned voice guide) instead of previewing.")
-        .option("--body <markdown>", "With --approved: save this edited body verbatim instead of re-synthesizing.")
+        .option("--body <markdown>", "With --approved: save this body verbatim (the guide a preview showed, or your edit) with no new AI call.")
         .option("--title <title>", "Optional title for a newly created page/asset.")
         .option("--limit <n>", "Voice only: how many recent sent messages to learn from (max 200).")
         .option("--json", "Print a JSON envelope.")
@@ -8624,9 +8670,66 @@ Examples:
         .action(async (options) => {
         await handleAsyncAction("knowledge purge", options, () => runKnowledgeMirrorPurge());
     }));
+    program
+        .command("ads")
+        .description("Saved Ads intelligence searches. Saving or tagging a query costs nothing; run its platform and query through the matching adyntel.* tool with the normal preview and credit gate.")
+        .addCommand(new Command("searches")
+        .description("Save reusable Ads queries for 0 credits. Saving never runs a provider search. Example: oxygen ads searches save --name 'Competitor ads' --platform facebook_ads --company-domain acme.com --tags competitor-watch.")
+        .addCommand(new Command("list")
+        .description("List saved Ads search definitions, optionally filtered by tag.")
+        .option("--tag <label>", "Only saved searches carrying this tag.")
+        .option("--json", "Print a JSON envelope.")
+        .action(async (options) => {
+        await handleAsyncAction("ads searches list", options, () => requestOxygen(`/api/cli/ads/searches${options.tag ? `?tag=${encodeURIComponent(options.tag)}` : ""}`));
+    }))
+        .addCommand(new Command("get")
+        .description("Read one saved Ads search definition without running it.")
+        .argument("<id>")
+        .option("--json", "Print a JSON envelope.")
+        .action(async (id, options) => {
+        await handleAsyncAction("ads searches get", options, () => requestOxygen(`/api/cli/ads/searches/${encodeURIComponent(id)}`));
+    }))
+        .addCommand(new Command("save")
+        .alias("create")
+        .description("Save a named Ads search query for 0 credits; no provider call.")
+        .requiredOption("--name <name>", "Name for the saved search.")
+        .requiredOption("--platform <platform>", "Domain: facebook_ads, google_ads, linkedin_ads (use --company-domain). Keyword: facebook_ad_search, linkedin_keyword_search, tiktok_search (use --keyword).")
+        .option("--company-domain <domain>", "Required for facebook_ads, google_ads, and linkedin_ads; e.g. acme.com.")
+        .option("--keyword <keyword>", "Required for facebook_ad_search, linkedin_keyword_search, and tiktok_search.")
+        .option("--country-code <code>", "Optional two-letter country code, e.g. US.")
+        .option("--tags <labels>", "Comma-separated workspace tags.")
+        .option("--json", "Print a JSON envelope.")
+        .action(async (options) => {
+        await handleAsyncAction("ads searches save", options, () => requestOxygen("/api/cli/ads/searches", { method: "POST", body: {
+                name: options.name, platform: options.platform, company_domain: options.companyDomain,
+                keyword: options.keyword, country_code: options.countryCode, tags: splitCommaList(options.tags),
+            } }));
+    }))
+        .addCommand(new Command("update")
+        .description("Replace a saved search's name or query; keep its tags. No provider call.")
+        .argument("<id>")
+        .requiredOption("--name <name>", "Name for the saved search.")
+        .requiredOption("--platform <platform>", "Domain: facebook_ads, google_ads, linkedin_ads (use --company-domain). Keyword: facebook_ad_search, linkedin_keyword_search, tiktok_search (use --keyword).")
+        .option("--company-domain <domain>", "Required for facebook_ads, google_ads, and linkedin_ads; e.g. acme.com.")
+        .option("--keyword <keyword>", "Required for facebook_ad_search, linkedin_keyword_search, and tiktok_search.")
+        .option("--country-code <code>", "Optional two-letter country code, e.g. US.")
+        .option("--json", "Print a JSON envelope.")
+        .action(async (id, options) => {
+        await handleAsyncAction("ads searches update", options, () => requestOxygen(`/api/cli/ads/searches/${encodeURIComponent(id)}`, { method: "PATCH", body: {
+                name: options.name, platform: options.platform, company_domain: options.companyDomain,
+                keyword: options.keyword, country_code: options.countryCode,
+            } }));
+    }))
+        .addCommand(new Command("delete")
+        .description("Archive a saved search; hide it from lists and tag footprints.")
+        .argument("<id>")
+        .option("--json", "Print a JSON envelope.")
+        .action(async (id, options) => {
+        await handleAsyncAction("ads searches delete", options, () => requestOxygen(`/api/cli/ads/searches/${encodeURIComponent(id)}`, { method: "DELETE" }));
+    })));
     program
         .command("tags")
-        .description(`Workspace tags: one vocabulary across ${TAG_KINDS_PROSE}. Tags normalize to lowercase (trimmed, deduped, max 50 per item; any characters — nothing is slugified, so "Q3 Outbound" becomes "q3 outbound"). ATTACH tags on the owning surface — each of those groups has its own \`tag\` subcommand (e.g. \`oxygen inbox tag\`, \`oxygen tables tag\`, \`oxygen domains tag\`) — then \`tags get <tag>\` returns every carrier with deep-links. CURATE the vocabulary here: \`tags create\` declares a tag (with a description, color, and pin) before anything carries it, \`tags update\` re-annotates one, and \`tags rename\`/\`merge\`/\`delete\` reshape it everywhere at once. Tags are free, inert metadata: attaching or removing one costs 0 credits, makes no provider call, and changes no sending, routing, or warm-up behaviour.`)
+        .description(`Workspace tags: one vocabulary across ${TAG_KINDS_PROSE}. Tags normalize to lowercase (trimmed, deduped, max 50 per item; any characters — nothing is slugified, so "Q3 Outbound" becomes "q3 outbound"). ATTACH with a carrier's own tag command (e.g. \`oxygen inbox tag\`, \`oxygen tables tag\`) or use \`oxygen tags attach <kind> <ref> --tags <labels>\` for Signal types, saved Dashboards, runtime Agents, and saved Ads searches. Then \`tags get <tag>\` returns every carrier with deep-links. CURATE the vocabulary here: \`tags create\` declares a tag (with a description, color, and pin) before anything carries it, \`tags update\` re-annotates one, and \`tags rename\`/\`merge\`/\`delete\` reshape it everywhere at once. Tags are free, inert metadata: attaching or removing one costs 0 credits, makes no provider call, and changes no sending, routing, or warm-up behaviour.`)
         .addCommand(new Command("list")
         .description("List every workspace tag with per-primitive counts, most-used first.")
         .option("--json", "Print a JSON envelope.")
@@ -8634,7 +8737,7 @@ Examples:
         await handleAsyncAction("tags list", options, () => requestOxygen("/api/cli/tags"));
     }))
         .addCommand(new Command("get")
-        .description(`Everything carrying one tag — ${TAG_KINDS_PROSE} — each with its deep-link.`)
+        .description(`Everything carrying one tag — ${TAG_KINDS_PROSE} — each with its deep-link. In the result, ad_search_collection means a saved Ads search.`)
         .argument("<tag>", "The tag (case-insensitive).")
         .option("--json", "Print a JSON envelope.")
         .action(async (tag, options) => {
@@ -8710,6 +8813,24 @@ Examples:
             method: "POST",
             body: { action: "delete", tags, ...(options.apply ? { apply: true } : {}) },
         }));
+    }))
+        .addCommand(new Command("attach")
+        .description("Replace tags on a Signal type, saved Dashboard, runtime Agent, or saved Ads search. [] clears the item; no provider call is made.")
+        .argument("<kind>", "signal_type, dashboard, agent, or ad_search_collection")
+        .argument("<ref>", "Signal type key, dashboard id/slug, Agent slug, or saved Ads search id")
+        .requiredOption("--tags <labels>", "Comma-separated complete tag list; an empty string clears it.")
+        .option("--json", "Print a JSON envelope.")
+        .action(async (kind, ref, options) => {
+        const body = { tags: splitCommaList(options.tags) };
+        await handleAsyncAction("tags attach", options, () => {
+            switch (kind) {
+                case "signal_type": return requestOxygen(`/api/cli/signals/registry/${encodeURIComponent(ref)}/tags`, { method: "POST", body });
+                case "dashboard": return requestOxygen(`/api/cli/dashboards/${encodeURIComponent(ref)}/tags`, { method: "POST", body });
+                case "agent": return requestOxygen(`/api/cli/agent/${encodeURIComponent(ref)}/tags`, { method: "POST", body });
+                case "ad_search_collection": return requestOxygen(`/api/cli/ads/searches/${encodeURIComponent(ref)}/tags`, { method: "POST", body });
+                default: throw new Error("kind must be signal_type, dashboard, agent, or ad_search_collection");
+            }
+        });
     }));
     program
         .command("comments")
@@ -9391,17 +9512,18 @@ Examples:
         .command("columns")
         .description("Workspace table column commands. Price first: `tools search --for-table <table>` lists every enrichment this table's columns support with its credit cost per row (0 credits). Ready-made templates (pricing pages, job posts, event pages, 10-Ks, website facts, market questions, text extraction, plus free 0-credit cleanups — company names, job titles, email type, text to list; person questions over an enriched LinkedIn profile and person appearances; company research questions — founders, parent company, funding, cloud provider, offers demos, industry, NAICS, HQ and footprint, LinkedIn/Crunchbase/careers page lookups): `columns catalog`, then `columns add <table> --prompt-key <key> --input <name>=<column>`. Column choice and provider routing guide: the oxygen-gtm skill's enriching-and-researching.md (`oxygen skills install`). With --json parse stdout only: the envelope is stdout, and the spend and cost notes (`estimated N credits for a live run`) are stderr, so merging the streams breaks the JSON.")
         .addCommand(new Command("add")
-        .description("Add a nullable column to a workspace table. Writes the definition only — this never runs the column and never spends credits; use `columns run` for that, with --dry-run first to see the cost. For a page, posting or filing the row already links to, or a company fact Oxygen already knows how to research (founders, parent company, funding, cloud provider, offers demos, industry, NAICS, HQ, a LinkedIn or Crunchbase page), pick a template from `columns catalog` (--prompt-key) instead of writing a prompt; or read a URL column with --kind research --research-url. The guide is the oxygen-gtm skill's enriching-and-researching.md. A formula column needs no run at all: it evaluates on read from its current inputs, so `tables query` shows its values immediately.")
+        .description("Add a nullable column to a workspace table. Writes the definition only — this never runs the column and never spends credits; use `columns run` for that, with --dry-run first to see the cost. For a page, posting or filing the row already links to, or a company fact Oxygen already knows how to research (founders, parent company, funding, cloud provider, offers demos, industry, NAICS, HQ, a LinkedIn or Crunchbase page), pick a template from `columns catalog` (--prompt-key) instead of writing a prompt; or read a URL column with --kind research --research-url. The guide is the oxygen-gtm skill's enriching-and-researching.md. For ICP fit, use Classify Score: `columns add <table> --label 'ICP fit' --score 'low,medium,high' --prompt 'Assess {{company_name}}: {{description}}, {{employees}} employees' --grounding workspace` (0.075 credits/row). A formula column needs no run at all: it evaluates on read from its current inputs, so `tables query` shows its values immediately.")
         .argument("<table>", "Table id or slug.")
-        .option("--preset <preset>", "Add a pre-built column bundle instead of one column, which is what --prompt-key adds: a preset writes SEVERAL columns at once and needs no --input on a table whose identity column it can find, while --prompt-key adds one template column and binds each input you name. Presets: `person_enrich` (one LinkedIn profile lookup — Blitz first, the LinkedIn Scraper only when Blitz has no match — then first/last/full name, current company and its LinkedIn URL, job title, start date, education, school, headline, bio, location and followers as free stored fields that fill when the lookup runs; the person templates in `columns catalog --category people` all read its payload column), `company_enrich` (one company lookup from a domain or LinkedIn URL — Blitz first, the LinkedIn Scraper only when Blitz has no match, about 1 credit a company — keeping the whole profile in its JSON column plus name, domain, LinkedIn URL, headcount, industry, description, founded year and HQ country as free stored fields; no field choices; binds to the person preset's current_company_linkedin_url automatically), `company_tech_stack` (the technologies a company runs, from its website and hiring), or `domain_check` (1 credit/row for a live/redirect/parked/not_found/dead verdict on every domain, cached 30 days, plus a free label column to filter on). For a single cleaned or classified column, use a template from `columns catalog` instead — that is one column, not a bundle. Name the input column with --input: `url` for person_enrich, `domain` and/or `linkedin_url` for the company presets. Any column works whatever it is called; without --input Oxygen guesses from column names. Creating the columns is free; run them afterwards, --dry-run first.")
+        .option("--preset <preset>", "Add a pre-built column bundle instead of one column, which is what --prompt-key adds: a preset writes SEVERAL columns at once and needs no --input on a table whose identity column it can find, while --prompt-key adds one template column and binds each input you name. Presets: `person_enrich` (one LinkedIn profile lookup — Blitz first, the LinkedIn Scraper only when Blitz has no match — then first/last/full name, current company and its LinkedIn URL, job title, start date, education, school, headline, bio, location and followers as free stored fields that fill when the lookup runs; the person templates in `columns catalog --category people` all read its payload column), `company_enrich` (one company lookup from a domain or LinkedIn URL — Blitz first, the LinkedIn Scraper only when Blitz has no match, about 1 credit a company — keeping the whole profile in its JSON column plus name, domain, LinkedIn URL, headcount, industry, description, founded year and HQ country as free stored fields; no field choices; binds to the person preset's current_company_linkedin_url automatically), `company_tech_stack` (the technologies a company runs, from its website and hiring), `company_funding` (total raised, latest round, number of rounds and investors), `company_revenue` (an annual revenue estimate), `company_hiring` (the roles a company is hiring for, with a count) — each of these four is one paid lookup column that fills its own columns, priced per row in `tools search --for-table` — or `domain_check` (1 credit/row for a live/redirect/parked/not_found/dead verdict on every domain, cached 30 days, plus a free label column to filter on). For a single cleaned or classified column, use a template from `columns catalog` instead — that is one column, not a bundle. Name the input column with --input: `url` for person_enrich, `domain` and/or `linkedin_url` for the company presets. Any column works whatever it is called; without --input Oxygen guesses from column names. Creating the columns is free; run them afterwards, --dry-run first.")
         .option("--input <slot=column...>", "Bind a preset or template input to an exact column, e.g. --input url=pricing_url with --prompt-key, or --input domain=website --input linkedin_url=company_li with --preset. Repeatable. For a preset it is only needed when the automatic match is wrong or missing; for a template it names the column each declared input reads.", collectRepeatable, [])
         // No preset takes a field list any more (founder, 2026-09-24). Hidden,
         // not removed: an old script passing them gets the server's refusal,
-        // which names `find company --fields` and `--preset company_tech_stack`,
+        // which names the funding, revenue, hiring and tech-stack presets,
         // instead of an unknown-option error that explains nothing.
         .addOption(new Option("--preset-fields <fields>", "Retired: presets take no field list.").hideHelp())
         .addOption(new Option("--check-technologies <names>", "Retired: presets take no field list.").hideHelp())
-        .option("--capability <capability>", "Seed a ready-to-run enrichment column WITHOUT running it (0 credits): verify_email grades the address a row already holds \u2014 MillionVerifier first, catch-all domains escalate to BounceBan; work_email, personal_email, mobile_phone and linkedin_url find a value the row is missing through the managed waterfall (personal_email is the non-work mailbox, graded by MillionVerifier before it is written). Sets kind=enrichment and jsonb; label and key default from the capability. Preview cost with `enrich-column preview --capability <same>` and run later with `enrich-column run --approved --max-credits <n>`.")
+        .option("--capability <capability>", "Seed a ready-to-run enrichment column WITHOUT running it (0 credits): verify_email grades the address a row already holds \u2014 MillionVerifier first, catch-all domains escalate to BounceBan; work_email, mobile_phone and linkedin_url find a value the row is missing through the managed waterfall. For a personal (non-work) email add --include-personal-email to work_email: one column finds both (personal_email alone still works for existing scripts). Sets kind=enrichment and jsonb; label and key default from the capability. Inputs are mapped from this table's columns; the response names any it could not find and the command that maps it. Preview cost with `enrich-column preview --capability <same>` and run later with `enrich-column run --approved --max-credits <n>`.")
+        .option("--include-personal-email", "With --capability work_email: also find the person's personal (non-work) email from their LinkedIn URL, billed only on a hit and graded before it is written, into the same cell's personal_email.")
         .option("--label <label>", "Display label for the new column. Required unless --prompt-key or --capability supplies a default title.")
         .option("--key <key>", "Optional stable column key. Defaults to a normalized label.")
         .option("--data-type <type>", "Column data type: text, numeric, boolean, jsonb, or timestamptz.")
@@ -9429,16 +9551,11 @@ Examples:
         .option("--structured-output", "Undo --no-structured-output: let the prompt's named sections shape the answer again.")
         .option("--output-schema-json <json>", "AI column output JSON schema as inline JSON.")
         .option("--output-schema-file <path>", "AI column output JSON schema read from a file path.")
-        // Classification columns stay out of --help until OXYGEN_SYSTEM_ONE_COLUMN_MODE
-        // is on in production: a help screen the npm CLI prints everywhere must not
-        // offer what production answers with classification_not_enabled. They still
-        // parse where the surface is on (dev), and the flag-aware `tools search`
-        // catalog advertises them there. Unhide at the production flip (ADR 0027).
-        .addOption(new Option("--classify <labels>", "Classification column: label every row with one of these comma-separated labels (2-20), answering --prompt. Each cell holds the label, a 0-1 confidence and uncertain:true below --min-confidence (the best guess is kept). Flat ~0.075 credits/row; see `columns run --dry-run`.").hideHelp())
-        .addOption(new Option("--yes-no <question>", "Classification column: answer this yes/no question per row (reference columns as {{column_key}}). Filter on the answer with `tables query --filter-tree-json` and a path leaf, e.g. '{\"type\":\"group\",\"conjunction\":\"and\",\"children\":[{\"type\":\"leaf\",\"columnKey\":\"<column>\",\"path\":\"answer\",\"operator\":\"is\",\"value\":true}]}'.").hideHelp())
-        .addOption(new Option("--score <levels>", "Classification column: rate each row on these comma-separated levels, lowest first (2-10), answering --prompt.").hideHelp())
-        .addOption(new Option("--min-confidence <0-1>", "Classification columns: below this the answer is marked uncertain. Default 0.85 (0.7 for --yes-no).").hideHelp())
-        .addOption(new Option("--grounding <mode>", "Classification columns: none (default) judges only the row and your question; workspace also sends your workspace knowledge (ICP, positioning), which can pull answers toward your ICP.").hideHelp())
+        .addOption(new Option("--classify <labels>", "Classification column: label every row with one of these comma-separated labels (2-20), answering --prompt. Each cell holds the label, a 0-1 confidence and uncertain:true below --min-confidence (the best guess is kept). Flat ~0.075 credits/row; see `columns run --dry-run`."))
+        .addOption(new Option("--yes-no <question>", "Classification column: answer this yes/no question per row (reference columns as {{column_key}}). Filter on the answer with `tables query --filter-tree-json` and a path leaf, e.g. '{\"type\":\"group\",\"conjunction\":\"and\",\"children\":[{\"type\":\"leaf\",\"columnKey\":\"<column>\",\"path\":\"answer\",\"operator\":\"is\",\"value\":true}]}'."))
+        .addOption(new Option("--score <levels>", "Classification column: rate each row on these comma-separated levels, lowest first (2-10), answering --prompt."))
+        .addOption(new Option("--min-confidence <0-1>", "Classification columns: below this the answer is marked uncertain. Default 0.85 (0.7 for --yes-no)."))
+        .addOption(new Option("--grounding <mode>", "Classification columns: none (default) judges only the row and your question; workspace also sends your workspace knowledge (ICP, positioning), which can pull answers toward your ICP."))
         .option("--bind-object <slug>", "Bind column CRM object slug (companies, people, deals, ...). Sets kind=bind and resolves rows to CRM records by identity.")
         .option("--bind-map <pairs>", "Bind identity mapping as identity=column pairs, e.g. domain=website,linkedin_url=li.")
         .option("--bind-create", "Bind columns: assert a new CRM record for unmatched rows (onNoMatch=create; a truth write, needs --approved on run).")
@@ -9564,6 +9681,8 @@ Examples:
             const isResearch = requestedKind === "research";
             if (capability)
                 column.capability = capability;
+            if (options.includePersonalEmail)
+                column.include_personal_email = true;
             // An enrichment cell is always the provider envelope, so the server
             // rejects any other data type ("Enrichment columns must use jsonb
             // data type."). Default it, the way --bind-object already does,
@@ -10084,7 +10203,7 @@ Examples:
         });
     }))
         .addCommand(new Command("catalog")
-        .description("List the column templates you can add with `columns add <table> --prompt-key <key>`: the extract templates (pricing-page, job-posting, event, 10-K, website-fact, market and text extractors) and the company research questions (founders, parent company, subsidiaries, funding rounds, market cap, cloud provider, is SaaS, offers demos, industry, NAICS, HQ / states / cities, competitors, LinkedIn / Crunchbase / Glassdoor / careers page lookups) and the person templates (--category people: skill set, grad school, location, job fit and current company read from the person_enrich payload for 15 credits; events, keynotes, podcasts and GitHub profile searched by name), each with the input it reads (bind it with --input <name>=<column_key>), the providers behind it, the answer fields, and the credits per row. Read-only and free. Tool-backed columns that read a page or call a provider — e.g. Website contacts (emails and phones from each row's site) — are found with `oxygen tools search <words>`, not here. Provider waterfalls and enrichment bundles are a different list with their own per-row prices: `oxygen enrichment catalog`.")
+        .description("List column templates and native Classify. For ICP fit, Classify Score (0.075 credits/row) appears in `data.native`, including with `--family classification`; `data.entries` lists separate prompt templates. Templates can be added with `columns add <table> --prompt-key <key>`: the extract templates (pricing-page, job-posting, event, 10-K, website-fact, market and text extractors) and the company research questions (founders, parent company, subsidiaries, funding rounds, market cap, cloud provider, is SaaS, offers demos, industry, NAICS, HQ / states / cities, competitors, LinkedIn / Crunchbase / Glassdoor / careers page lookups) and the person templates (--category people: skill set, grad school, location, job fit and current company read from the person_enrich payload for 15 credits; events, keynotes, podcasts and GitHub profile searched by name), each with the input it reads (bind it with --input <name>=<column_key>), the providers behind it, the answer fields, and the credits per row. Read-only and free. Tool-backed columns that read a page or call a provider — e.g. Website contacts (emails and phones from each row's site) — are found with `oxygen tools search <words>`, not here. Provider waterfalls and enrichment bundles are a different list with their own per-row prices: `oxygen enrichment catalog`.")
         .option("--category <category>", "Only templates in one picker section: extract (page and text extraction), normalize, organize, summarize (free cleanups and classifications), people (person questions and appearances) or company (company research questions); comma-separate to combine (extract,people). The outreach prompts sit under copy, scoring, qa, research.")
         .option("--family <family>", "Only one family. Extract: pricing, job_posting, events, filings, site_facts, market, portfolio, text_extraction. Cleanups: company, person, email, lists, classification. Company: web_presence, corporate_structure, funding, footprint, business_model, tech, market. People: profile, appearances.")
         .option("--kind <kind>", "Only one column kind: research (reads the web or a page, answer with sources), search (a managed web search whose cell is a page URL or the result list, fixed price), ai (reads row text), or formula (free).")
@@ -10746,7 +10865,7 @@ Examples:
         .description("Inspect missing company fields, provider routing, and credit estimates without provider calls.")
         .argument("<table>", "Table id or slug.")
         .option("--missing-fields <fields>", "Comma-separated fields to fill; accepts every key `oxygen find company --list-fields` prints, not just the identity set. Derived fields (description, founded_year, hq_country, funding_stage, latest_funding_round, investors, job_openings, parent_company, subsidiaries) are read from a payload the run already fetches and add no provider lane of their own.")
-        .option("--providers <providers>", "Comma-separated provider order pool. Defaults to scraper,blitzapi,crustdata,ai_ark,prospeo,leadmagic.")
+        .option("--providers <providers>", "Comma-separated provider order pool. Defaults to scraper,blitzapi,apollo,peopledatalabs,theirstack,leadmagic.")
         .option("--all", "Preview all rows.")
         .option("--limit <n>", "Preview a limited row scope.")
         .option("--row-ids <ids>", "Comma-separated row ids.")
@@ -10949,7 +11068,7 @@ Examples:
         .description("Plan-tier limits, spend-safety defaults, per-channel sending limits, and storage capacity posture.")
         .addHelpText("after", "\nRun `oxygen limits show --json` to see your current plan's API and webhook rates, Table and workspace storage headroom, and the next scheduled change. The $999 and $1,999 rows-per-Table increases remain held until capacity testing passes.\n")
         .addCommand(new Command("show")
-        .description("Compare every plan size: price, monthly credits, volume bonus and price per 100 credits (`plan_bands`). Show your plan band and its limits beside every plan size's (API rate, webhook ingress, storage, import file size, columns per auto-run, signals feed, spend defaults incl. Agent and Copilot caps, fastest workflow schedule), the per-channel sending limits every plan shares (emails per mailbox, WhatsApp, LinkedIn, calls) and its workflow Code-step and run-attempt limits, plus Tables capacity usage naming the largest Table. Each plan size's storage says whether it is in force, scheduled to change on a date, or awaiting its rows-per-Table capacity test, with the values it moves to. `spend_safety_defaults.applies_to` says what each spend default bounds: an unattended trigger delivery, a table auto-run batch, one Agent run, or the attended Copilot. `web_url` opens the same view in the web app (Settings → Plan limits), including any scheduled change. Read-only; spends no credits. Recovery: https://oxygen-agent.com/docs/safety/billing.")
+        .description("Compare every plan size: price, monthly credits, volume bonus and price per 100 credits (`plan_bands`). Show your plan band and its limits beside every plan size's (API rate, webhook ingress, storage, import file size, columns per auto-run, signals feed, spend defaults incl. Agent and Copilot caps, fastest workflow schedule), the per-channel sending limits every plan shares (emails per mailbox, WhatsApp, LinkedIn, calls) and its workflow Code-step and run-attempt limits, plus Tables capacity usage naming the largest Table. Each plan size's storage says whether it is in force, scheduled to change on a date, or awaiting its rows-per-Table capacity test, with the values it moves to. `spend_safety_defaults.enterprise_agent_run_default` gives Enterprise the $1,999 band’s in-force Agent default with no contract override; `agent_run_approved_max_credits` is the maximum for an explicitly approved higher run. `spend_safety_defaults.applies_to` says what each spend default bounds: an unattended trigger delivery, a table auto-run batch, one Agent run, or the attended Copilot. `web_url` opens the same view in the web app (Settings → Plan limits), including any scheduled change. Read-only; spends no credits. Recovery: https://oxygen-agent.com/docs/safety/billing.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
         await handleAsyncAction("limits show", options, () => requestOxygen("/api/cli/limits"));
@@ -11202,7 +11321,6 @@ Examples:
         .option("--rollover <n>", "Max balance credits roll over to. Defaults to the monthly credits.")
         .option("--base-tier <tier>", "Base pricing tier to inherit feature flags from. Defaults to growth_250.")
         .option("--byok", "Enable bring-your-own-key integrations for the plan.")
-        .option("--agent-run-default-credits <n>", "The contract's own default Agent run ceiling in credits (at most 25,000). Omitted keeps the plan's default; re-running set-plan without it clears it.")
         .option("--note <text>", "Internal note stored on the contract.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
@@ -11221,9 +11339,6 @@ Examples:
                     : {}),
                 ...(readOption(options.baseTier) ? { base_tier: readOption(options.baseTier) } : {}),
                 ...(options.byok ? { byok: true } : {}),
-                ...(readOption(options.agentRunDefaultCredits)
-                    ? { agent_run_default_credits: readPositiveNumber(options.agentRunDefaultCredits) }
-                    : {}),
                 ...(readOption(options.note) ? { note: readOption(options.note) } : {}),
             },
         }));
@@ -12013,9 +12128,10 @@ Examples:
     }))
         .addCommand(new Command("custom")
         .description("List the org's user-defined custom agents (distinct from `agent list`, which shows the built-in roster).")
+        .option("--tag <tag>", "Only custom agents carrying this workspace tag.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
-        await handleAsyncAction("agent custom", options, () => requestOxygen("/api/cli/agent/custom"));
+        await handleAsyncAction("agent custom", options, () => requestOxygen(`/api/cli/agent/custom${options.tag ? `?tag=${encodeURIComponent(options.tag)}` : ""}`));
     }))
         .addCommand(new Command("delete")
         .description("Archive a custom agent (soft delete): its triggers stop firing and it leaves the roster; versions/runs are preserved.")
@@ -12787,15 +12903,15 @@ Examples:
         .description("Preflight an enrichment column without provider calls or credit usage. A lane on your own key (BYOK) is quoted at OXYGEN's platform fee per call, hit or miss (provider_cost_breakdown[].byok_platform_fee_credits_per_call).")
         .argument("<table>", "Table id or slug.")
         .option("--source-column <column>", "Source column key or id. For mobile_phone this is the LinkedIn URL column.")
-        .option("--full-name-column <column>", "Column key or id containing the person's full name for work_email. Pair with company-domain/name for Prospeo, RocketReach, LeadMagic, Hunter, Dropleads, ContactOut, BetterContact, or People Data Labs.")
+        .option("--full-name-column <column>", "Column key or id containing the person's full name for work_email. Pair with company-domain/name for Prospeo, LeadMagic, Hunter, Dropleads, ContactOut, BetterContact, or People Data Labs.")
         .option("--first-name-column <column>", "Column key or id containing the person's first name for work_email.")
         .option("--last-name-column <column>", "Column key or id containing the person's last name for work_email.")
-        .option("--linkedin-url-column <column>", "Column key or id containing the person's LinkedIn URL. Required by BlitzAPI and enough for RocketReach, Prospeo, Hunter, ContactOut, BetterContact, Crustdata, or People Data Labs.")
+        .option("--linkedin-url-column <column>", "Column key or id containing the person's LinkedIn URL. Required by BlitzAPI and enough for Prospeo, Hunter, ContactOut, BetterContact, People Data Labs, or Crustdata on your own key.")
         .option("--email-column <column>", "Column key or id containing a known work email for providers that accept email as an identity fallback.")
         .option("--company-domain-column <column>", "Column key or id containing the company domain for work_email. Pair with full-name/first+last for name+company providers.")
         .option("--company-name-column <column>", "Column key or id containing the company name for work_email when no domain is available.")
         .option("--company-linkedin-url-column <column>", "Column key or id containing the company's LinkedIn URL for company identity fallback.")
-        .option("--capability <capability>", "What to run: mobile_phone, work_email, personal_email, linkedin_url (find a missing value), or verify_email (grade an email the row already has). Defaults to mobile_phone.")
+        .option("--capability <capability>", "What to run: mobile_phone, work_email, linkedin_url (find a missing value), or verify_email (grade an email the row already has). For a personal email add --include-personal-email to work_email (personal_email alone still works). Defaults to mobile_phone.")
         .option("--target-column <column>", "Target enrichment column key. Defaults to the capability payload column.")
         .option("--on-existing-manual-column <mode>", "How to handle an existing manual target: error, write_if_empty, or create_enrichment_column.")
         .option("--provider-order <providers>", "Comma-separated provider order. Overrides the default cost-aware waterfall profile.")
@@ -12804,6 +12920,7 @@ Examples:
         .option("--phone-waterfall-profile <profile>", "Phone waterfall profile: auto (input-aware), linkedin_url, email, or name_domain. Auto picks the cheapest cost-ordered provider set for each row's inputs (mobile match rate ~30-60%).")
         .option("--verify-phone", "Validate found phone numbers with ClearoutPhone (adds phone_line_type + phone_carrier; filter phone_line_type=mobile for mobile-only).")
         .option("--allow-premium-lanes", "Opt in to managed lanes billing over 50 credits per call. Only linkedin_url has one (LeadMagic email_to_profile, 122.5cr), until the 2026-09 repricing date, when a LinkedIn URL starts billing only on a hit; it is off by default so an unattended run can't bill-shock. No effect on mobile_phone, work_email or verify_email.")
+        .option("--include-personal-email", "work_email only: also find the personal (non-work) email from the LinkedIn URL column, billed only on a hit; the preview adds its price and the address lands in the cell's personal_email.")
         .option("--phone-verification-credential-mode <mode>", "ClearoutPhone credential mode for phone verification: managed or user_api_key.")
         .option("--limit <n>", "Rows to estimate. Defaults to 10.")
         .option("--all", "Estimate all rows.")
@@ -12821,16 +12938,16 @@ Examples:
         .description("Create or reuse an enrichment column and queue a background run.")
         .argument("<table>", "Table id or slug.")
         .option("--source-column <column>", "Source column key or id. For mobile_phone this is the LinkedIn URL column.")
-        .option("--full-name-column <column>", "Column key or id containing the person's full name for work_email. Pair with company-domain/name for Prospeo, RocketReach, LeadMagic, Hunter, Dropleads, ContactOut, BetterContact, or People Data Labs.")
+        .option("--full-name-column <column>", "Column key or id containing the person's full name for work_email. Pair with company-domain/name for Prospeo, LeadMagic, Hunter, Dropleads, ContactOut, BetterContact, or People Data Labs.")
         .option("--first-name-column <column>", "Column key or id containing the person's first name for work_email.")
         .option("--last-name-column <column>", "Column key or id containing the person's last name for work_email.")
-        .option("--linkedin-url-column <column>", "Column key or id containing the person's LinkedIn URL. Required by BlitzAPI and enough for RocketReach, Prospeo, Hunter, ContactOut, BetterContact, Crustdata, or People Data Labs.")
+        .option("--linkedin-url-column <column>", "Column key or id containing the person's LinkedIn URL. Required by BlitzAPI and enough for Prospeo, Hunter, ContactOut, BetterContact, People Data Labs, or Crustdata on your own key.")
         .option("--email-column <column>", "Column key or id containing a known work email for providers that accept email as an identity fallback.")
         .option("--company-domain-column <column>", "Column key or id containing the company domain for work_email. Pair with full-name/first+last for name+company providers.")
         .option("--company-name-column <column>", "Column key or id containing the company name for work_email when no domain is available.")
         .option("--company-linkedin-url-column <column>", "Column key or id containing the company's LinkedIn URL for company identity fallback.")
         .requiredOption("--max-credits <credits>", "Required credit ceiling for the queued run.")
-        .option("--capability <capability>", "What to run: mobile_phone, work_email, personal_email, linkedin_url (find a missing value), or verify_email (grade an email the row already has). Defaults to mobile_phone.")
+        .option("--capability <capability>", "What to run: mobile_phone, work_email, linkedin_url (find a missing value), or verify_email (grade an email the row already has). For a personal email add --include-personal-email to work_email (personal_email alone still works). Defaults to mobile_phone.")
         .option("--target-column <column>", "Target enrichment column key. Defaults to the capability payload column.")
         .option("--on-existing-manual-column <mode>", "How to handle an existing manual target: error, write_if_empty, or create_enrichment_column.")
         .option("--provider-order <providers>", "Comma-separated provider order. Overrides the default cost-aware waterfall profile.")
@@ -12839,6 +12956,7 @@ Examples:
         .option("--phone-waterfall-profile <profile>", "Phone waterfall profile: auto (input-aware), linkedin_url, email, or name_domain. Auto picks the cheapest cost-ordered provider set for each row's inputs (mobile match rate ~30-60%).")
         .option("--verify-phone", "Validate found phone numbers with ClearoutPhone (adds phone_line_type + phone_carrier; filter phone_line_type=mobile for mobile-only).")
         .option("--allow-premium-lanes", "Opt in to managed lanes billing over 50 credits per call. Only linkedin_url has one (LeadMagic email_to_profile, 122.5cr), until the 2026-09 repricing date, when a LinkedIn URL starts billing only on a hit; it is off by default so an unattended run can't bill-shock. No effect on mobile_phone, work_email or verify_email.")
+        .option("--include-personal-email", "work_email only: also find the personal (non-work) email from the LinkedIn URL column, billed only on a hit; the preview adds its price and the address lands in the cell's personal_email.")
         .option("--phone-verification-credential-mode <mode>", "ClearoutPhone credential mode for phone verification: managed or user_api_key.")
         .option("--limit <n>", "Rows to queue.")
         .option("--all", "Queue all rows.")
@@ -13219,7 +13337,7 @@ Examples:
         await handleAsyncAction("integrations list", options, () => requestOxygen("/api/cli/integrations/composio/list"));
     }))
         .addCommand(new Command("connect")
-        .description("Connect an integration. OAuth toolkits return a redirect URL, which grants nothing until you approve access on the provider's page; API-key integrations accept --api-key. Run without credentials first for a 0-credit preview of the provider's exact fields (mode: needs_api_key): no credential is submitted, nothing is stored, and no provider call is made. Use repeatable --credential name=value when a provider also requires a host, subdomain, or other named value. To keep a secret out of shell history and process arguments, open the preview's web_url and submit it in Connections; --api-key is for controlled noninteractive use. Credential submission creates or replaces the connection immediately and needs no separate --approved flag. LinkedIn and WhatsApp return a Unipile hosted-auth URL instead (`oxygen senders connect` / `oxygen whatsapp connect` are the canonical paths).")
+        .description("Connect an integration. For OAuth toolkits, running this command immediately creates a pending provider authorization and returns a redirect URL; account access starts only if you approve on the provider's page. This is not a price preview. On a repriced workspace, a connected X account reserves 1,000 credits ($10) monthly; inspect the current pricing schedule with `oxygen limits show --json` before connecting. API-key integrations accept --api-key. Run without credentials only for an API-key integration to get a 0-credit preview of its exact fields (mode: needs_api_key): no credential is submitted, nothing is stored, and no provider call is made. Use repeatable --credential name=value when a provider also requires a host, subdomain, or other named value. To keep a secret out of shell history and process arguments, open the preview's web_url and submit it in Connections; --api-key is for controlled noninteractive use. Credential submission creates or replaces the connection immediately and needs no separate --approved flag. LinkedIn and WhatsApp return a Unipile hosted-auth URL instead (`oxygen senders connect` / `oxygen whatsapp connect` are the canonical paths).")
         .argument("<integration_id>", "Integration id, such as 'slack' or 'serpapi'.")
         .option("--api-key <value>", "API key for controlled noninteractive use. Literal values can appear in shell history and process arguments; prefer the preview web_url for manual entry.")
         .option("--credential <name=value>", "Named provider credential field. Repeat for multi-field integrations (for example, PostHog: --credential subdomain=us).", collectRepeatable, [])
@@ -13353,8 +13471,8 @@ Examples:
         .action(async (options) => {
         await handleAsyncAction("senders list", options, () => {
             const params = new URLSearchParams();
-            if (options.usage !== false)
-                params.set("include_usage", "true");
+            // The server counts usage unless told not to, so --no-usage must say so.
+            params.set("include_usage", options.usage === false ? "false" : "true");
             const status = readOption(options.status);
             if (status)
                 params.set("status", status);
@@ -13372,7 +13490,7 @@ Examples:
         await handleAsyncAction("senders checkpoints", options, () => requestOxygen("/api/cli/senders/checkpoints"));
     }))
         .addCommand(new Command("connect")
-        .description("Get a Unipile hosted-auth URL to connect a new LinkedIn account (or reconnect with --reconnect). Each connected LinkedIn account has one monthly price, never two: a LinkedIn sending seat ($30/month, billed in dollars to the billing owner) while seats are sold, or a monthly credit reservation once they are retired, when a connect the balance cannot cover fails with insufficient_credits. Invites, messages and other LinkedIn actions cost 0 credits on top. Check `oxygen billing seats --json` before connecting: it says which applies and the price. A workspace linked to another organization's plan is billed at that organization. New accounts require --country (the owner's normal LinkedIn login country) and default to syncing only conversations OXYGEN starts; use --inbox-scope all to opt into the full LinkedIn inbox. Use --cookie-auth and --custom-proxy to expose those inputs inside Unipile's hosted wizard; their secrets never pass through OXYGEN. Use --count for bulk onboarding. LinkedIn restricts automated activity: every connection needs --acknowledge-risk (only a reconnect that already recorded one is exempt), and --count above 1 also needs --owner-consent (each owner connects their own account). Links are shareable and valid for 10 minutes.")
+        .description("Get a Unipile hosted-auth URL to connect a new LinkedIn account (or reconnect with --reconnect). This command creates a pending provider authorization; it does not preview a price. Each connected LinkedIn account has one monthly charge, never two: an existing dollar seat until it ends at renewal, or a monthly credit reservation after seats retire. On a repriced workspace that reservation is 3,400 credits ($34) monthly; a connect the balance cannot cover fails with insufficient_credits. Invites, messages and other LinkedIn actions cost 0 credits on top. Check `oxygen billing seats --json` before connecting for the current charge and seat status. A workspace linked to another organization's plan is billed at that organization. New accounts require --country (the owner's normal LinkedIn login country) and default to syncing only conversations OXYGEN starts; use --inbox-scope all to opt into the full LinkedIn inbox. Use --cookie-auth and --custom-proxy to expose those inputs inside Unipile's hosted wizard; their secrets never pass through OXYGEN. Use --count for bulk onboarding. LinkedIn restricts automated activity: every connection needs --acknowledge-risk (only a reconnect that already recorded one is exempt), and --count above 1 also needs --owner-consent (each owner connects their own account). Links are shareable and valid for 10 minutes.")
         .option("--reconnect <connection_id>", "Reconnect an existing connection instead of creating a new one. Accepts a connection id.")
         .option("--country <code>", "Required for new accounts: ISO 3166-1 alpha-2 code for the account owner's normal LinkedIn login country (for example DE or US).")
         .option("--sales-nav", "Request Classic + Sales Navigator access during Unipile hosted authentication.")
@@ -14321,8 +14439,7 @@ Examples:
         .action(async (options) => {
         await handleAsyncAction("whatsapp accounts", options, () => {
             const params = new URLSearchParams();
-            if (options.usage !== false)
-                params.set("include_usage", "true");
+            params.set("include_usage", options.usage === false ? "false" : "true");
             const status = readOption(options.status);
             if (status)
                 params.set("status", status);
@@ -14726,6 +14843,20 @@ Examples:
                 ...(options.personRowId ? { person_row_id: readOption(options.personRowId) } : {}),
                 text: readOption(options.text), ...(options.approved ? { approved: true } : {}) },
         }));
+    }))
+        .addCommand(new Command("forget-whatsapp-chat")
+        .description("Permanently erase a terminal old WhatsApp chat and its messages from OXYGEN. Preview first; --approved confirms the exact chat. --sender and --before guard the scope. This does not delete from WhatsApp; for a connected account find whatsapp.chats_delete with oxygen tools search, inspect tools run --mode dry-run, then use --mode live --approved and verify the provider result.")
+        .argument("<conversationId>", "OXYGEN conversation id from inbox list.")
+        .requiredOption("--sender <id>", "Original disconnected WhatsApp sender account id.")
+        .requiredOption("--before <iso>", "Delete only when the latest message predates this ISO timestamp.")
+        .option("--approved", "Approve permanent removal from OXYGEN after reviewing the preview.")
+        .option("--json", "Print a JSON envelope.")
+        .action(async (conversationId, options) => {
+        await handleAsyncAction("inbox forget-whatsapp-chat", options, () => requestOxygen(`/api/cli/inbox/${encodeURIComponent(conversationId)}/forget-whatsapp`, {
+            method: "POST",
+            body: { sender_account_id: readOption(options.sender), before: readOption(options.before),
+                approved: options.approved === true },
+        }));
     }))
         .addCommand(new Command("delete-message")
         .description("Delete your sent LinkedIn message for everyone within 60 minutes. This cannot be undone. Omit --approved for a preview; show it before approving. Other channels and inbound messages are unsupported.")
@@ -15276,9 +15407,10 @@ Examples:
     program.addCommand(new Command("sequences")
         .description("Multichannel outreach sequences: one enrollment per lead can span LinkedIn, email, WhatsApp, human call tasks, and connected-CRM tasks. LinkedIn steps dispatch natively (rate-limited, credit-capped); email steps send natively or place/move/stop the lead in a bound Instantly campaign (BYOK); crm_task can exact-match/upsert/link CRM records and create a mapped external follow-up (HubSpot first), with replay-safe per-operation receipts. A reply always stops that lead, on every channel. To also pause the replier's colleagues, set `--company-reply-pause` on `create`/`update` (pick the reply categories); to pause or resume a company by hand or from a workflow (e.g. a meeting was booked), use `pause-company` / `resume-company` / `paused-companies`. A pause is resumable; a company do-not-contact entry (`suppressions`) is a permanent block.")
         .addCommand(new Command("list")
-        .description("List sequences with persisted launch status kept separate from current operational state. Fleet counts report marked-active versus operationally-live (active with nonterminal work), and rows explain flowing, paced, blocked, degraded, drained, or empty work without SQL. --stats joins each row's LIFETIME funnel.")
+        .description("List sequences with persisted launch status kept separate from current operational state. Fleet counts report marked-active versus operationally-live (active with nonterminal work), and rows explain flowing, paced, paused, blocked, degraded, drained, or empty work without SQL. An active sequence whose every lead has finished shows drained (completed); leads enrolled into it later are contacted on its next dispatch tick. --stats joins each row's LIFETIME funnel.")
         .option("--status <status>", "Filter by status: draft, active, paused, or archived.")
-        .addOption(new Option("--operational-state <state>", "Filter by current work state; fleet counts remain unfiltered: empty, drained, never_started (enrolled leads, never launched), blocked, degraded, flowing, or paced.").choices(["empty", "drained", "never_started", "blocked", "degraded", "flowing", "paced"]))
+        .addOption(new Option("--operational-state <state>", "Filter by current work state; fleet counts remain unfiltered: empty, drained, never_started (enrolled leads, never launched), blocked, degraded, flowing, paced, or paused (work waiting on a paused sequence).").choices(["empty", "drained", "never_started", "blocked", "degraded", "flowing", "paced", "paused"]))
+        .addOption(new Option("--lifecycle <lifecycle>", "Filter by the lifecycle a person reads; fleet counts remain unfiltered: draft, active, completed (active, every lead finished), paused, or archived.").choices([...SEQUENCE_LIFECYCLES]))
         .addOption(new Option("--channel <channel>", "Only sequences carrying this channel.").choices(["email", "linkedin", "whatsapp"]))
         .option("--tag <tag>", "Only sequences carrying this workspace tag (see `oxygen tags list`).")
         .option("--stats", "Attach lifetime stats per sequence (a stats pass per row — slower on large workspaces).")
@@ -15292,6 +15424,9 @@ Examples:
             const operationalState = readOption(options.operationalState);
             if (operationalState)
                 params.set("operational_state", operationalState);
+            const lifecycle = readOption(options.lifecycle);
+            if (lifecycle)
+                params.set("lifecycle", lifecycle);
             const channel = readOption(options.channel);
             if (channel)
                 params.set("channel", channel);
@@ -15552,7 +15687,7 @@ Examples:
         .addHelpText("after", "\nSenders: each new lead gets one of the --sender-profiles people, and its LinkedIn and email steps come from that person (email from one of their inboxes). Per step, in the steps file: email_send.sender_mailbox_id sends that email from one exact inbox; a LinkedIn step's sender_profile_id sends it from one selected person. Invite, message, inmail and withdraw_invite steps must share one sender_profile_id or none: that person then owns every lead's LinkedIn thread (LinkedIn allows one of your accounts per conversation). visit_profile, follow, like_post and comment_post may each name anyone selected. An email whose From changes, including the return to the lead's inbox, needs its own subject_template.\n")
         .requiredOption("--name <name>", "Human-readable sequence name.")
         .requiredOption("--slug <slug>", "Unique slug for the sequence.")
-        .requiredOption("--steps-file <path>", "Path to a JSON file: { \"steps\": [...] }. LinkedIn steps (visit_profile | invite | wait_for_connection | message | inmail | follow | like_post | comment_post | withdraw_invite), email steps (email_send | email_enroll | email_move | email_stop), WhatsApp (whatsapp_message), human call tasks (call_task), connected-CRM tasks (crm_task; channel crm; exact identity record_mappings + explicit create/update policy + record_links + dynamic task property_mappings/associations), and control steps (wait | wait_for_signal | branch | stop), each with an `id`. Copy templates support {{column}} interpolation from the lead's row, {{column|fallback}} inline fallbacks, deterministic spintax — {{RANDOM|a|b|c}} or industry-standard bare {Hi|Hey|Hello}, nestable like {Would {Tuesday|Thursday} work|next week?} — and {% if column %}…{% endif %} conditionals; a bare {…} region is spintax only when it contains a top-level |, so literal braces (CSS/JSON) pass through. Native email sends (email_send) also expose three reserved sender variables from the sending mailbox: {{sender_name}} (mailbox display name), {{sender_first_name}} (its first word), and {{sender_email}} (the from address); a row column of the same name WINS on collision, and a missing display name renders empty. comment_post takes text_template and/or ai_prompt — a KG-grounded comment generated at send time (a paid AI call) that falls back to text_template if generation fails. A `branch` routes on signals (then/else) or the legacy connection_accepted/already_connected/open_profile sugar (then_id/else_id). A signal condition can also branch on the LEAD'S DATA: a data leaf { has_column: \"email\" } is true when that row_values column has a non-empty value (add present:false for \"missing\") — e.g. route leads that have an email down an email arm and the rest down a LinkedIn arm. MINIMAL EMAIL STEP SHAPE: { \"id\": \"s1\", \"channel\": \"email\", \"kind\": \"email_send\", \"subject_template\": \"...\", \"body_template\": \"...\" } — body_template is REQUIRED on email_send; subject_template is OPTIONAL and is the one control that decides threading: give a step its own subject and it goes out as a NEW email, omit it and the step continues the lead's previous email in the same thread, going out as \"Re: <the previous email's subject>\" (what the retired email_reply kind used to be — still accepted on input, rewritten into this shape, and reported under `warnings` in the response). The FIRST email step of a sequence must carry a subject, since it has no earlier thread to continue. MINIMAL WHATSAPP STEP SHAPE: { \"id\": \"s1\", \"channel\": \"whatsapp\", \"kind\": \"whatsapp_message\", \"template\": \"Hi {{first_name|there}} …\" } — template is REQUIRED, and a live WhatsApp start also needs the sequence's --whatsapp-cold-initiate opt-in. A/B tests use an explicit `variants` array of copy partials on the step (up to 25 alternates, a–z; spintax varies wording INSIDE one variant and is not A/B-tracked). For the complete replay-safe crm_task upsert mapping shape, install/read the oxygen-sequencer skill.")
+        .requiredOption("--steps-file <path>", "Path to a JSON file: { \"steps\": [...] }. LinkedIn steps (visit_profile | invite | wait_for_connection | message | inmail | follow | like_post | comment_post | withdraw_invite), email steps (email_send | email_enroll | email_move | email_stop), WhatsApp (whatsapp_message), human call tasks (call_task), connected-CRM tasks (crm_task; channel crm; exact identity record_mappings + explicit create/update policy + record_links + dynamic task property_mappings/associations), and control steps (wait | wait_for_signal | branch | stop), each with an `id`. Copy templates support {{column}} interpolation from the lead's row, {{column|fallback}} inline fallbacks, deterministic spintax — {{RANDOM|a|b|c}} or industry-standard bare {Hi|Hey|Hello}, nestable like {Would {Tuesday|Thursday} work|next week?} — and {% if column %}…{% endif %} conditionals; a bare {…} region is spintax only when it contains a top-level |, so literal braces (CSS/JSON) pass through. Every step's copy can also use {{sender_first_name}}, {{sender_last_name}} and {{sender_full_name}} (alias {{sender_name}}): the name of the person who sends that step (their sender profile, else the account or inbox display name), with no table column needed; email steps add {{sender_email}} (the from address). A row column of the same name WINS on collision, and a missing name renders empty. comment_post takes text_template and/or ai_prompt — a KG-grounded comment generated at send time (a paid AI call) that falls back to text_template if generation fails. A `branch` routes on signals (then/else) or the legacy connection_accepted/already_connected/open_profile sugar (then_id/else_id). A signal condition can also branch on the LEAD'S DATA: a data leaf { has_column: \"email\" } is true when that row_values column has a non-empty value (add present:false for \"missing\") — e.g. route leads that have an email down an email arm and the rest down a LinkedIn arm. MINIMAL EMAIL STEP SHAPE: { \"id\": \"s1\", \"channel\": \"email\", \"kind\": \"email_send\", \"subject_template\": \"...\", \"body_template\": \"...\" } — body_template is REQUIRED on email_send; subject_template is OPTIONAL and is the one control that decides threading: give a step its own subject and it goes out as a NEW email, omit it and the step continues the lead's previous email in the same thread, going out as \"Re: <the previous email's subject>\" (what the retired email_reply kind used to be — still accepted on input, rewritten into this shape, and reported under `warnings` in the response). The FIRST email step of a sequence must carry a subject, since it has no earlier thread to continue. MINIMAL WHATSAPP STEP SHAPE: { \"id\": \"s1\", \"channel\": \"whatsapp\", \"kind\": \"whatsapp_message\", \"template\": \"Hi {{first_name|there}} …\" } — template is REQUIRED, and a live WhatsApp start also needs the sequence's --whatsapp-cold-initiate opt-in. A/B tests use an explicit `variants` array of copy partials on the step (up to 25 alternates, a–z; spintax varies wording INSIDE one variant and is not A/B-tracked). For the complete replay-safe crm_task upsert mapping shape, install/read the oxygen-sequencer skill.")
         .option("--channels <list>", "Comma-separated channels: linkedin,email,whatsapp,call,crm. Defaults to the channels the journey touches. crm_task currently supports HubSpot.")
         .option("--whatsapp-cold-initiate", "WhatsApp: allow cold-initiating new chats (no prior conversation). Required to start a WhatsApp sequence live — WhatsApp via Unipile is unofficial WhatsApp Web, so cold-initiating is an explicit ban-risk opt-in.")
         .option("--phone-column-key <key>", "WhatsApp: row_values key holding each lead's phone number (else falls back to phone/phone_number/mobile).")
@@ -15567,16 +15702,15 @@ Examples:
         .option("--max-credits <n>", "Credit cap for the LinkedIn track (also set when starting).")
         .option("--max-live-sends <n>", "External-action ceiling for 0-credit email/WhatsApp/CRM-task tracks (positive integer). Required to start any of them live.")
         .option("--max-emails-per-mailbox-per-day <n>", "Per-mailbox daily email cap (positive integer) applied across the sending pool; also sets each mailbox's send pace (send window ÷ cap, catching up when a slot is missed). Daily capacity = this cap × sendable mailboxes; `sequences stats` reports it under daily_budget.")
-        .option("--send-window-file <path>", "Email window JSON: { timezone, days?, start, end, timezone_mode?, recipient_timezone_column? }; days are ISO 1-7. New sequences default to weekdays 09:00-17:00 in the workspace timezone when available, otherwise UTC. Gates email steps only; LinkedIn/WhatsApp steps use --linkedin-timezone/-days/-hours-start/-hours-end.")
-        .option("--linkedin-timezone <tz>", "LinkedIn/WhatsApp sending schedule (the web Sending schedule): IANA zone, e.g. Europe/Zurich. Set with --linkedin-days, --linkedin-hours-start and --linkedin-hours-end; the window narrows each sender's working hours.")
-        .option("--linkedin-days <days>", "LinkedIn sending schedule days: mon-fri, mon,wed,fri, or ISO numbers 1-7 (1 = Monday).")
-        .option("--linkedin-hours-start <HH:MM>", "LinkedIn sending schedule start, local to --linkedin-timezone, e.g. 06:45.")
-        .option("--linkedin-hours-end <HH:MM>", "LinkedIn sending schedule end (exclusive), e.g. 18:30. Must be after the start. The window only narrows each sender's working hours (default 07:00-22:00, see senders limits get), never widens them.")
+        .option("--schedule-timezone <tz>", "One sending schedule for every channel, the same as Launch's Sending schedule: IANA zone, e.g. Europe/Berlin. Give it with --schedule-days, --schedule-hours-start and --schedule-hours-end; it sets the email window and the LinkedIn/WhatsApp window together. To give one channel different hours, or to send email in each recipient's own timezone, run `sequences update` after creating (--send-window-file, --linkedin-*).")
+        .option("--schedule-days <days>", "Sending schedule days: mon-fri, mon,wed,fri, or ISO numbers 1-7 (1 = Monday).")
+        .option("--schedule-hours-start <HH:MM>", "Sending schedule start, local to --schedule-timezone, e.g. 09:00.")
+        .option("--schedule-hours-end <HH:MM>", "Sending schedule end (exclusive), e.g. 17:00. An email step's own send_window (on the step in --steps-file) still overrides it for that step. LinkedIn sends also stay inside each LinkedIn account's working hours (default 07:00-22:00 in the account's timezone; set with `oxygen senders limits set`); WhatsApp accounts and email mailboxes have no hours of their own.")
         .option("--max-emails-per-day <n>", "Sequence-wide daily live-send cap across all senders/mailboxes. Unset means no additional sequence-wide cap; mailbox caps still apply. Omit on update to keep the current setting.")
         .option("--max-new-enrollments-per-day <n>", "Daily cap on NEW first-touch leads. Unset means no additional intake cap; sending limits still apply. Omit on update to keep the current setting.")
         .option("--sequence-prioritization <mode>", "Under a tight daily budget, serve 'followups' or 'new_leads' first.")
         .option("--esp-matching <mode>", "Native-email ESP matching: 'prefer' (DEFAULT) biases toward a mailbox on the recipient's own provider, falling back to any; 'off' rotates mailboxes freely; 'strict' requires a same-provider mailbox and defers the send when none exists.")
-        .option("--esp-routing-file <path>", "Path to a JSON file holding the WHOLE native-email routing policy: { mode?, routes?, exclude? }. `routes` is keyed by the RECIPIENT's provider and its values are relative send shares per sending provider, so { \"google\": { \"microsoft\": 100 } } sends Google-hosted recipients from Microsoft inboxes. `exclude` bars a sending domain outright: [{ \"domain\": \"burned.example\", \"from_recipients\": [\"google\"] }]. Replaces --esp-matching and the file is the complete policy, not a patch.")
+        .option("--esp-routing-file <path>", "Path to a JSON file holding the WHOLE native-email routing policy: { mode?, routes? }. `routes` is keyed by the RECIPIENT's provider and its values are relative send shares per sending provider, so { \"google\": { \"microsoft\": 100 } } sends Google-hosted recipients from Microsoft inboxes. Replaces --esp-matching and the file is the complete policy, not a patch. To stop sending from a domain, leave its inboxes out with --mailboxes.")
         .option("--sender-failover <mode>", "What happens when an enrollment's LinkedIn/WhatsApp sender goes unavailable: 'wait' (default) resumes when the sender recovers; 'rebind' moves UNTOUCHED enrollments (no thread, no pending invite, no lead binding) to the least-loaded healthy sender in the pool after ~5h of confirmed outage.")
         .option("--email-min-gap-minutes <n>", "Minimum same-mailbox gap, default 12 minutes (integer 0-720; 0 disables the extra gap). Sends are spread across the window and may be farther apart. Daily caps and windows still apply.")
         .option("--opportunity-value <usd>", "Estimated USD value of one positive-reply opportunity (>= 0). Analytics-only: sequence stats multiply it by the positive-reply count to report pipeline $ (stats.opportunities). Never gates a send or spends a credit.")
@@ -15588,11 +15722,8 @@ Examples:
         .option("--company-reply-pause <off|default|statuses>", "Pause the replier's company in this campaign when a reply has one of these statuses. Oxygen detects the company from work-email domains or explicit company fields; with no company identity, only the replier stops. New sequences start with this setting off. 'default' = interested,neutral,not_now,not_interested; or comma-separated Inbox status keys (`inbox labels list`); 'off' disables it. Read the saved setting with `sequences get`.")
         .option("--stop-on-reply-scope <scope>", "(deprecated: use --company-reply-pause) 'company_domain' = --company-reply-pause interested,neutral,not_now,not_interested,wrong_person; 'lead' = off.")
         .option("--bounce-protection <json>", "Sequence bounce policy JSON (partial updates merge): enabled=true, warning_rate=.02, pause_rate=.03, min_sends=20, window_days=7. Hard bounces / accepted sends in the rolling window; pauses this sequence, not the fleet. Rates are fractions; mailbox protection is separate.")
-        .option("--include-unsubscribe-headers", "Opt in to one-click unsubscribe headers (default off); visible link is separate.")
-        .option("--no-include-unsubscribe-headers", "Omit one-click headers.")
-        .option("--reply-to-stop-text <text>", "Personal opt-out text (default empty); empty clears it.")
-        .option("--include-unsubscribe-link", "Append OXYGEN's visible recipient-bound unsubscribe footer to first-touch cold emails. Explicit opt-in; off by default. Plain-text messages show the URL, while HTML messages show a linked Unsubscribe label.")
-        .option("--no-include-unsubscribe-link", "Do not append OXYGEN's visible unsubscribe footer (the default). Sends the authored body unchanged and never removes suppression from recipients who already opted out.")
+        .option("--include-unsubscribe", "Add an unsubscribe option to emails, the same as Launch's switch: a visible recipient-bound link (plain text shows the URL, HTML a linked Unsubscribe label) plus one-click headers that mail apps show as an Unsubscribe button, both on first-touch cold emails; in-thread follow-ups carry neither. Zapbox sends (mailboxes imported from Zapmail, `transport: \"zapbox\"` in `mailboxes list --json`) carry the link only. Off by default. There is no separate opt-out text: write any reply-to-stop line into the email copy. `sequences update` can switch on the link or the headers alone.")
+        .option("--no-include-unsubscribe", "Turn off both the visible unsubscribe link and the one-click headers.")
         .option("--tracking-opens", "Opt in to open tracking (default off). Requires a verified tracking domain and deployment tracking secret.")
         .option("--no-tracking-opens", "Turn OFF the open pixel for this sequence's native email sends (a deliverability knob — a pixel is spam-filter surface).")
         .option("--tracking-clicks", "Opt in to click tracking (default off). Requires a verified tracking domain and deployment tracking secret.")
@@ -15637,6 +15768,7 @@ Examples:
                     ...(options.trackingOpens !== undefined ? { tracking_opens: options.trackingOpens } : {}),
                     ...(options.trackingClicks !== undefined ? { tracking_clicks: options.trackingClicks } : {}),
                     ...(settings ? { settings } : {}),
+                    ...readUnifiedSequenceBody(options),
                 },
             });
         });
@@ -15669,11 +15801,11 @@ Examples:
         }
     }))
         .addCommand(new Command("update")
-        .description("Update a sequence. Journey structure/channels/email binding are draft-only so revised scope receives a fresh launch approval; a started sequence may only re-time waits it already has (clear a delay by zeroing it, never by deleting the step — enrollments track position by index); sender pools can change while draft or paused; launch caps change through `sequences start` after first start. Name, throttles, tags, the default-off visible unsubscribe footer, and open/click tracking toggles remain editable as allowed by the server. Pass only the fields you want to change.")
+        .description("Update a sequence. Journey structure/channels/email binding are draft-only so revised scope receives a fresh launch approval; a started sequence may only re-time waits it already has (clear a delay by zeroing it, never by deleting the step — enrollments track position by index); sender pools can change while draft or paused; launch caps change through `sequences start` after first start. Name, throttles, the sending schedule, tags, the unsubscribe option (off by default), and open/click tracking toggles remain editable as allowed by the server. Pass only the fields you want to change.")
         .addHelpText("after", "\nSenders: email_send.sender_mailbox_id sends one email from an exact inbox of a selected sender; a LinkedIn step's sender_profile_id sends it from a selected person (invite, message, inmail and withdraw_invite share one or none). Omit both to use the lead's assigned person. An email whose From changes needs its own subject_template.\n")
         .argument("<sequence>", "Sequence id or slug.")
         .option("--name <name>", "New human-readable sequence name.")
-        .option("--steps-file <path>", "Draft only: path to a JSON file: { \"steps\": [...] } replacing the journey. Copy supports {{column}} interpolation; native email steps also expose {{sender_name}} / {{sender_first_name}} / {{sender_email}} from the sending mailbox (a same-named row column wins). A `branch` can also route on the lead's data with a data leaf { has_column: \"email\" } (true when that row_values column is non-empty; present:false for \"missing\").")
+        .option("--steps-file <path>", "Draft only: path to a JSON file: { \"steps\": [...] } replacing the journey. Copy supports {{column}} interpolation; every step also takes {{sender_first_name}} / {{sender_last_name}} / {{sender_full_name}} for the person who sends it, and email adds {{sender_email}} (a same-named row column wins). A `branch` can also route on the lead's data with a data leaf { has_column: \"email\" } (true when that row_values column is non-empty; present:false for \"missing\").")
         .option("--channels <list>", "Draft only: comma-separated channels: linkedin,email,whatsapp,call,crm.")
         .option("--whatsapp-cold-initiate", "WhatsApp: allow cold-initiating new chats (no prior conversation). Required to start a WhatsApp sequence live (draft-editable).")
         .option("--phone-column-key <key>", "WhatsApp: row_values key holding each lead's phone number (else falls back to phone/phone_number/mobile).")
@@ -15688,16 +15820,20 @@ Examples:
         .option("--max-credits <n>", "Credit cap for the LinkedIn track (draft only).")
         .option("--max-live-sends <n>", "Draft-time external-action ceiling for 0-credit email/WhatsApp/CRM-task tracks (positive integer). After first start, change it through `sequences start`.")
         .option("--max-emails-per-mailbox-per-day <n>", "Per-mailbox daily email cap (positive integer) applied across the sending pool; also sets each mailbox's send pace (send window ÷ cap, catching up when a slot is missed). Daily capacity = this cap × sendable mailboxes; `sequences stats` reports it under daily_budget.")
-        .option("--send-window-file <path>", "Email window JSON: { timezone, days?, start, end, timezone_mode?, recipient_timezone_column? }; days are ISO 1-7. New sequences default to weekdays 09:00-17:00 in the workspace timezone when available, otherwise UTC. Gates email steps only; LinkedIn/WhatsApp steps use --linkedin-timezone/-days/-hours-start/-hours-end.")
-        .option("--linkedin-timezone <tz>", "LinkedIn/WhatsApp sending schedule (the web Sending schedule): IANA zone, e.g. Europe/Zurich. Set with --linkedin-days, --linkedin-hours-start and --linkedin-hours-end; the window narrows each sender's working hours.")
+        .option("--schedule-timezone <tz>", "One sending schedule for every channel, the same as Launch's Sending schedule: IANA zone, e.g. Europe/Berlin. Give it with --schedule-days, --schedule-hours-start and --schedule-hours-end; it sets the email window and the LinkedIn/WhatsApp window together. Use it instead of --send-window-file and the --linkedin-* flags. Email set to send in each recipient's own timezone keeps doing so, with this zone for leads that have none.")
+        .option("--schedule-days <days>", "Sending schedule days: mon-fri, mon,wed,fri, or ISO numbers 1-7 (1 = Monday).")
+        .option("--schedule-hours-start <HH:MM>", "Sending schedule start, local to --schedule-timezone, e.g. 09:00.")
+        .option("--schedule-hours-end <HH:MM>", "Sending schedule end (exclusive), e.g. 17:00. An email step's own send_window (on the step in --steps-file) still overrides it for that step. LinkedIn sends also stay inside each LinkedIn account's working hours (default 07:00-22:00 in the account's timezone; set with `oxygen senders limits set`); WhatsApp accounts and email mailboxes have no hours of their own.")
+        .option("--send-window-file <path>", "Email-only window JSON: { timezone, days?, start, end, timezone_mode?, recipient_timezone_column? }; days are ISO 1-7. New sequences default to weekdays 09:00-17:00 in the workspace timezone when available, otherwise UTC. Use it to keep email on different hours from LinkedIn/WhatsApp, or to send in each recipient's own timezone (timezone_mode recipient, which --schedule-* then keeps); for one schedule across channels, use --schedule-* instead.")
+        .option("--linkedin-timezone <tz>", "LinkedIn/WhatsApp-only sending schedule: IANA zone, e.g. Europe/Zurich. Set with --linkedin-days, --linkedin-hours-start and --linkedin-hours-end; for LinkedIn the window narrows each account's working hours, for WhatsApp it is the only hours limit. For one schedule across channels, use --schedule-* instead.")
         .option("--linkedin-days <days>", "LinkedIn sending schedule days: mon-fri, mon,wed,fri, or ISO numbers 1-7 (1 = Monday).")
         .option("--linkedin-hours-start <HH:MM>", "LinkedIn sending schedule start, local to --linkedin-timezone, e.g. 06:45.")
-        .option("--linkedin-hours-end <HH:MM>", "LinkedIn sending schedule end (exclusive), e.g. 18:30. Must be after the start. The window only narrows each sender's working hours (default 07:00-22:00, see senders limits get), never widens them.")
+        .option("--linkedin-hours-end <HH:MM>", "LinkedIn sending schedule end (exclusive), e.g. 18:30. Must be after the start. For LinkedIn the window only narrows each account's working hours (default 07:00-22:00, see senders limits get), never widens them.")
         .option("--max-emails-per-day <n>", "Sequence-wide daily live-send cap across all senders/mailboxes. Unset means no additional sequence-wide cap; mailbox caps still apply. Omit on update to keep the current setting.")
         .option("--max-new-enrollments-per-day <n>", "Daily cap on NEW first-touch leads. Unset means no additional intake cap; sending limits still apply. Omit on update to keep the current setting.")
         .option("--sequence-prioritization <mode>", "Under a tight daily budget, serve 'followups' or 'new_leads' first.")
         .option("--esp-matching <mode>", "Native-email ESP matching: 'prefer' (DEFAULT) biases toward a mailbox on the recipient's own provider, falling back to any; 'off' rotates mailboxes freely; 'strict' requires a same-provider mailbox and defers the send when none exists.")
-        .option("--esp-routing-file <path>", "Path to a JSON file holding the WHOLE native-email routing policy: { mode?, routes?, exclude? }. `routes` is keyed by the RECIPIENT's provider and its values are relative send shares per sending provider, so { \"google\": { \"microsoft\": 100 } } sends Google-hosted recipients from Microsoft inboxes. `exclude` bars a sending domain outright: [{ \"domain\": \"burned.example\", \"from_recipients\": [\"google\"] }]. Replaces --esp-matching and the file is the complete policy, not a patch.")
+        .option("--esp-routing-file <path>", "Path to a JSON file holding the WHOLE native-email routing policy: { mode?, routes? }. `routes` is keyed by the RECIPIENT's provider and its values are relative send shares per sending provider, so { \"google\": { \"microsoft\": 100 } } sends Google-hosted recipients from Microsoft inboxes. Replaces --esp-matching and the file is the complete policy, not a patch. To stop sending from a domain, leave its inboxes out with --mailboxes.")
         .option("--sender-failover <mode>", "What happens when an enrollment's LinkedIn/WhatsApp sender goes unavailable: 'wait' (default) resumes when the sender recovers; 'rebind' moves UNTOUCHED enrollments (no thread, no pending invite, no lead binding) to the least-loaded healthy sender in the pool after ~5h of confirmed outage.")
         .option("--email-min-gap-minutes <n>", "Minimum same-mailbox gap, default 12 minutes (integer 0-720; 0 disables the extra gap). Sends are spread across the window and may be farther apart. Daily caps and windows still apply.")
         .option("--opportunity-value <usd>", "Estimated USD value of one positive-reply opportunity (>= 0). Analytics-only: sequence stats multiply it by the positive-reply count to report pipeline $ (stats.opportunities). Never gates a send or spends a credit.")
@@ -15709,10 +15845,11 @@ Examples:
         .option("--company-reply-pause <off|default|statuses>", "Pause the replier's company in this campaign when a reply has one of these statuses. Oxygen detects the company from work-email domains or explicit company fields; with no company identity, only the replier stops. New sequences start with this setting off. 'default' = interested,neutral,not_now,not_interested; or comma-separated Inbox status keys (`inbox labels list`); 'off' disables it. Read the saved setting with `sequences get`.")
         .option("--stop-on-reply-scope <scope>", "(deprecated: use --company-reply-pause) 'company_domain' = --company-reply-pause interested,neutral,not_now,not_interested,wrong_person; 'lead' = off.")
         .option("--bounce-protection <json>", "Sequence bounce policy JSON (partial updates merge): enabled=true, warning_rate=.02, pause_rate=.03, min_sends=20, window_days=7. Hard bounces / accepted sends in the rolling window; pauses this sequence, not the fleet. Rates are fractions; mailbox protection is separate.")
-        .option("--include-unsubscribe-headers", "Opt in to one-click unsubscribe headers (default off); visible link is separate.")
+        .option("--include-unsubscribe", "Add an unsubscribe option to emails, the same as Launch's switch: a visible recipient-bound link (plain text shows the URL, HTML a linked Unsubscribe label) plus one-click headers that mail apps show as an Unsubscribe button, both on first-touch cold emails; in-thread follow-ups carry neither. Zapbox sends (mailboxes imported from Zapmail, `transport: \"zapbox\"` in `mailboxes list --json`) carry the link only. Off by default. There is no separate opt-out text: write any reply-to-stop line into the email copy.")
+        .option("--no-include-unsubscribe", "Turn off both the visible unsubscribe link and the one-click headers.")
+        .option("--include-unsubscribe-headers", "Only the one-click unsubscribe headers (default off); --include-unsubscribe turns on the headers and the visible link together.")
         .option("--no-include-unsubscribe-headers", "Omit one-click headers.")
-        .option("--reply-to-stop-text <text>", "Personal opt-out text (default empty); empty clears it.")
-        .option("--include-unsubscribe-link", "Append OXYGEN's visible recipient-bound unsubscribe footer to first-touch cold emails. Explicit opt-in; off by default. Plain-text messages show the URL, while HTML messages show a linked Unsubscribe label.")
+        .option("--include-unsubscribe-link", "Only the visible recipient-bound unsubscribe footer on first-touch cold emails (default off; --include-unsubscribe adds the one-click headers too). Plain-text messages show the URL, while HTML messages show a linked Unsubscribe label.")
         .option("--no-include-unsubscribe-link", "Turn the visible unsubscribe footer OFF. Future first-touch emails send the authored body unchanged; existing suppression records remain enforced.")
         .option("--tracking-opens", "Opt in to open tracking (default off). Requires a verified tracking domain and deployment tracking secret.")
         .option("--no-tracking-opens", "Turn OFF the open pixel for this sequence's native email sends (a deliverability knob — a pixel is spam-filter surface).")
@@ -15757,6 +15894,7 @@ Examples:
             const settings = readSequenceSettings(options);
             if (settings)
                 body.settings = settings;
+            Object.assign(body, readUnifiedSequenceBody(options));
             // Tri-state tracking toggles: only send the key when a flag was
             // explicitly passed, so an unrelated update never flips tracking.
             if (options.trackingOpens !== undefined)
@@ -15772,7 +15910,7 @@ Examples:
                     body.email = email;
             }
             if (Object.keys(body).length === 0) {
-                throw new Error("Provide at least one field to update (--name, --steps-file, --source-table, --channels, --senders, --tags, --email-*, --clear-email, --max-credits, --max-live-sends, --max-emails-per-mailbox-per-day, --send-window-file, --linkedin-* schedule, --company-reply-pause, --[no-]include-unsubscribe-link, --no-stop-on-bounce, --[no-]exclude-contacted, or --[no-]tracking-opens / --[no-]tracking-clicks).");
+                throw new Error("Provide at least one field to update (--name, --steps-file, --source-table, --channels, --senders, --tags, --email-*, --clear-email, --max-credits, --max-live-sends, --max-emails-per-mailbox-per-day, --schedule-* sending schedule, --send-window-file, --linkedin-* schedule, --company-reply-pause, --[no-]include-unsubscribe, --[no-]include-unsubscribe-link, --no-stop-on-bounce, --[no-]exclude-contacted, or --[no-]tracking-opens / --[no-]tracking-clicks).");
             }
             return requestOxygen(`/api/cli/sequences/${encodeURIComponent(sequence)}`, {
                 method: "PATCH",
@@ -15789,7 +15927,7 @@ Examples:
         await handleAsyncAction("sequences get", options, () => requestOxygen(`/api/cli/sequences/${encodeURIComponent(sequence)}${options.readiness ? "?include=readiness" : ""}`));
     }))
         .addCommand(new Command("enroll")
-        .description("Enroll leads into a sequence. Enrolling spends no credits and sends nothing — dispatch only happens at `sequences start`. --from-table enrolls every not-yet-enrolled row of the sequence's bound source table (up to 500 per run; the response's from_table.has_more says whether to run again) — for a LinkedIn sequence the profile is read from the bound table's URL column, where a full /in/ URL and a bare public handle carrying a hyphen or digit (ada-lovelace) both work, so no pre-resolved provider ids are needed; each handle Oxygen canonicalized is echoed in linkedin_handles_canonicalized (value + url) to check before start, and every row that still cannot be resolved is named in unresolved_linkedin_lead_details (row, value, reason) rather than only counted in unresolved_linkedin_leads. --leads-file enrolls an explicit JSON list { leads: [...] }: for an email/WhatsApp sequence a lead identified only by an email (row_values.email) or phone (row_values.phone) is auto-filed as a row in the sequence's leads table (auto-creating and binding one if there is none), deduped by email/phone, so no table has to exist first (the table is returned as leads_table with a web_url); a LinkedIn lead needs a lead_provider_id, a lead_profile_url (a /in/ URL or a bare public handle with a hyphen or digit), or a table_row_id whose row carries one of those. A CRM-only lead needs a stable table_row_id or lead_provider_id in addition to mapped row_values; a HubSpot contact id used in crm_task associations identifies the destination record, not the Oxygen enrollment. When the sequence is bound to a source table, a lead's table_row_id auto-snapshots that row's columns (incl. AI/tool outputs) into row_values for {{column}} copy — explicit row_values win. Idempotent per table row (and per email/phone for auto-filed leads). The org do-not-contact list is always enforced; --exclude-contacted and --suppress-list add further opt-in skips (reported under skipped_by_reason). Leads already owned by a sender account (from an earlier real send) are routed back to that same account; a lead owned by a sender NOT on this sequence is skipped (bound_to_other_sender) unless --ignore-sender-bindings. This enrolls into an OXYGEN Sequence; to put the same rows into a campaign you already run in Smartlead, Instantly, lemlist or HeyReach, use `sequences push-external`.")
+        .description("Enroll leads into a sequence. Enrolling spends no credits. An active sequence contacts the new leads on its next dispatch tick; a draft or paused one holds them until `sequences start`. --from-table enrolls every not-yet-enrolled row of the sequence's bound source table (up to 500 per run; the response's from_table.has_more says whether to run again) — for a LinkedIn sequence the profile is read from the bound table's URL column, where a full /in/ URL and a bare public handle carrying a hyphen or digit (ada-lovelace) both work, so no pre-resolved provider ids are needed; each handle Oxygen canonicalized is echoed in linkedin_handles_canonicalized (value + url) to check before start, and every row that still cannot be resolved is named in unresolved_linkedin_lead_details (row, value, reason) rather than only counted in unresolved_linkedin_leads. --leads-file enrolls an explicit JSON list { leads: [...] }: for an email/WhatsApp sequence a lead identified only by an email (row_values.email) or phone (row_values.phone) is auto-filed as a row in the sequence's leads table (auto-creating and binding one if there is none), deduped by email/phone, so no table has to exist first (the table is returned as leads_table with a web_url); a LinkedIn lead needs a lead_provider_id, a lead_profile_url (a /in/ URL or a bare public handle with a hyphen or digit), or a table_row_id whose row carries one of those. A CRM-only lead needs a stable table_row_id or lead_provider_id in addition to mapped row_values; a HubSpot contact id used in crm_task associations identifies the destination record, not the Oxygen enrollment. When the sequence is bound to a source table, a lead's table_row_id auto-snapshots that row's columns (incl. AI/tool outputs) into row_values for {{column}} copy — explicit row_values win. Idempotent per table row (and per email/phone for auto-filed leads). The org do-not-contact list is always enforced; --exclude-contacted and --suppress-list add further opt-in skips (reported under skipped_by_reason). Leads already owned by a sender account (from an earlier real send) are routed back to that same account; a lead owned by a sender NOT on this sequence is skipped (bound_to_other_sender) unless --ignore-sender-bindings. This enrolls into an OXYGEN Sequence; to put the same rows into a campaign you already run in Smartlead, Instantly, lemlist or HeyReach, use `sequences push-external`.")
         .argument("<sequence>", "Sequence id or slug.")
         .option("--leads-file <path>", "Path to a JSON file: { \"leads\": [{ row_values: { email }, lead_name }] } for cold email; { lead_provider_id, lead_name, table_row_id, row_values } for LinkedIn/existing rows; CRM-only leads require table_row_id or a stable lead_provider_id alongside mapped row_values. A CRM association object id is not the enrollment identity. Exactly one of --leads-file or --from-table.")
         .option("--from-table", "Enroll every not-yet-enrolled row of the sequence's bound source table (up to 500 per run; re-run to continue). Exactly one of --leads-file or --from-table.")
@@ -15964,19 +16102,28 @@ Examples:
         });
     }))
         .addCommand(new Command("contacts")
-        .description("List a launched campaign's table-backed contacts with full source variables, durable engagement stage, and factual or assigned sender. Contacts removed from this campaign are hidden; source rows remain intact.")
+        .description("List a launched campaign's table-backed contacts with full source variables, contact tags, and factual or assigned sender. A contact carries every tag it reached: contacted means an invite, message or email was sent (a profile visit is not), and a positive reply is also replied and contacted. Contacts removed from this campaign are hidden; source rows remain intact.")
         .argument("<sequence>", "Sequence id or slug.")
-        .option("--contact-state <state>", "Filter: all, not_contacted, contacted, connected, replied, or positive_reply.", "all")
+        .option("--contact-state <tags>", "Only contacts with any of these tags, comma-separated: not_contacted, contacted, connected, replied, positive_reply; or all.", "all")
+        .option("--exclude-contact-state <tags>", "Hide contacts with any of these tags, comma-separated.")
         .option("--limit <n>", "Maximum contacts per page (1-500). Page with --cursor (next_cursor from the previous page) or --offset.", "100")
         .option("--cursor <c>", "Pagination cursor from the previous page's next_cursor.")
         .option("--offset <n>", "Skip this many contacts before the page (0-based); an absolute alternative to --cursor.")
         .option("--json", "Print a JSON envelope.")
         .action(async (sequence, options) => {
         await handleAsyncAction("sequences contacts", options, () => {
-            const contactState = readOption(options.contactState) ?? "all";
-            if (!["all", "not_contacted", "contacted", "connected", "replied", "positive_reply"].includes(contactState)) {
-                throw new Error("--contact-state must be all, not_contacted, contacted, connected, replied, or positive_reply.");
-            }
+            const contactTags = ["not_contacted", "contacted", "connected", "replied", "positive_reply"];
+            const readTags = (flag, raw) => {
+                const tags = raw.split(",").map((tag) => tag.trim()).filter(Boolean);
+                if (tags.length === 0 || tags.some((tag) => !contactTags.includes(tag))) {
+                    throw new Error(`${flag} takes comma-separated tags: ${contactTags.join(", ")}.`);
+                }
+                return tags.join(",");
+            };
+            const contactStateRaw = readOption(options.contactState) ?? "all";
+            const contactState = contactStateRaw === "all" ? "all" : readTags("--contact-state", contactStateRaw);
+            const excludeRaw = readOption(options.excludeContactState);
+            const excludeContactState = excludeRaw ? readTags("--exclude-contact-state", excludeRaw) : null;
             const limit = readPositiveInt(options.limit);
             if (limit === undefined || limit > 500) {
                 throw new Error("--limit must be between 1 and 500.");
@@ -15985,6 +16132,8 @@ Examples:
                 contact_state: contactState,
                 limit: String(limit),
             });
+            if (excludeContactState)
+                params.set("exclude_contact_state", excludeContactState);
             const cursor = readOption(options.cursor);
             if (cursor)
                 params.set("cursor", cursor);
@@ -16175,7 +16324,7 @@ Examples:
         });
     }))
         .addCommand(new Command("stats")
-        .description("Show one sequence's persisted launch status and current operational state separately, including reasons, open work, lifetime sent/terminal-failed/deferral counts, and the funnel. daily_budget carries today's sends against the caps; operational.reasons carries why work is waiting (outside_send_window, mailbox_spacing, daily_send_cap_reached, ...). For a per-day send series use `sequences analytics --sequence <id> --range <window>`.")
+        .description("Show one sequence's persisted launch status and current operational state separately, including reasons, open work, lifetime sent/terminal-failed/deferral counts, and the funnel. Today's completed sends, reservations and remaining capacity appear in the default output and daily_budget. operational.reasons carries why work is waiting (outside_send_window, mailbox_spacing, daily_send_cap_reached, ...). For a per-day send series use `sequences analytics --sequence <id> --range <window>`.")
         .argument("<sequence>", "Sequence id or slug.")
         .option("--json", "Print a JSON envelope.")
         .action(async (sequence, options) => {
@@ -17740,7 +17889,7 @@ Examples:
         .addCommand(new Command("emailguard")
         .description("Assess every mailbox origin for EmailGuard and connect credential-capable Google Workspace mailboxes from managed, Zapmail, or compatible encrypted external imports. Manual/native Google rows report credential_required; Microsoft 365/Azure reports vendor_blocked. Preview never materializes a password; approved execution fetches it just in time and never prints it.")
         .addCommand(new Command("connect")
-        .description("Preview or connect selected mailboxes to EmailGuard. Managed mode is 100 credits/inbox-month (135 from the 2026-09 repricing's effective date; the preview shows the price in force); BYOK is 0 Oxygen credits. Google Workspace requires a real app password, fetched only after approval. Microsoft 365/Azure is explicitly vendor-blocked because EmailGuard exposes neither Microsoft OAuth nor tenant consent; Oxygen never downgrades it to password auth. Starts with a 0-credit, no-provider-write preview. Account connection sends no placement probe.")
+        .description("Preview or connect selected mailboxes to EmailGuard. On a repriced workspace managed mode is 135 credits/inbox-month, with two placement tests per inbox per cycle included; an extra managed test costs 66 credits. The preview shows the price in force; BYOK is 0 Oxygen credits. Google Workspace requires a real app password, fetched only after approval. Microsoft 365/Azure is explicitly vendor-blocked because EmailGuard exposes neither Microsoft OAuth nor tenant consent; Oxygen never downgrades it to password auth. Starts with a 0-credit, no-provider-write preview. Account connection sends no placement probe.")
         .option("--mailboxes <list>", "Comma-separated mailbox ids or addresses. Omit for the whole pool.")
         .option("--approved", "Perform the external EmailGuard account write.")
         .option("--plan <hash>", "Exact hash from the fresh preview (required with --approved).")
@@ -17857,7 +18006,7 @@ Examples:
         });
     }))
         .addCommand(new Command("warmup")
-        .description("OXYGEN Warm-up for the sending pool — the weeks of low-volume conversational mail that make a new inbox look trusted before you cold-send from it. It costs 100 credits per warming inbox per month ($1), or nothing once it is included in your own mailbox's 100-credit monthly connection (2026-09 repricing); the preview shows which applies. Fresh managed InboxKit Google/Microsoft/Azure orders with the default-on warm-up add-on activate automatically after provisioning under the approved order quote; do not run a second `warmup enable`. Google reuses the InboxKit-held credential only during activation and never stores or returns it; Microsoft/Azure uses exact native export. Standalone preview → approval is for BYOK/imported mailboxes, a managed opt-out, or later separate enrollment. InboxKit auto-export stays off for Microsoft/Azure because Oxygen submits only the exact authorized UIDs, and any non-cancelled InboxKit warm-up blocks either handoff so one mailbox cannot warm twice. OXYGEN Warm-up never owns campaign dispatch: native OXYGEN Sequences still own campaigns and sends. Eligible non-InboxKit Microsoft mailboxes use the separate `mailboxes warmup microsoft` OAuth fallback. Inboxes already warming on the retired TrulyInbox rail keep reporting and are wound down there with `warmup disable`; they are never silently moved to the current managed rail. When worker recovery is enforcing (the unset default), existing active paid OXYGEN Warm-up seats get bounded automatic recovery: Google uses usable stored credential authority, Microsoft OAuth or tenant-consent seats get a credential-free vendor reactivation, and stalled dispatch or DNS readiness is rechecked. An explicit shadow/off rollout observes candidates without automatic repair writes. Correct bad DNS records yourself; an active unpaused paid seat needs no manual resume after that correction. OXYGEN never invents consent, resumes a human or safety pause, starts a new paid enrollment, or blindly repeats an ambiguous provider write. Check `warmup status` and `mailboxes list` for the exact next action.")
+        .description("OXYGEN Warm-up for the sending pool — the weeks of low-volume conversational mail that make a new inbox look trusted before you cold-send from it. It costs 100 credits per warming inbox per month ($1), or nothing once it is included in your own mailbox's 100-credit monthly connection (2026-09 repricing); the preview shows which applies. Fresh managed InboxKit Google/Microsoft/Azure orders with the default-on warm-up add-on activate automatically after provisioning under the approved order quote; do not run a second `warmup enable`. Google reuses the InboxKit-held credential only during activation and never stores or returns it; Microsoft/Azure uses exact native export. Standalone preview → approval is for BYOK/imported mailboxes, a managed opt-out, or later separate enrollment. InboxKit auto-export stays off for Microsoft/Azure because Oxygen submits only the exact authorized UIDs, and any non-cancelled InboxKit warm-up blocks either handoff so one mailbox cannot warm twice. OXYGEN Warm-up never owns campaign dispatch: native OXYGEN Sequences still own campaigns and sends. Eligible non-InboxKit Microsoft mailboxes use the separate `mailboxes warmup microsoft` OAuth fallback. Inboxes already warming on the retired TrulyInbox rail keep reporting and are wound down there with `warmup disable`; they are never silently moved to the current managed rail. On existing active paid seats, Google credential repair uses its own enabled-by-default switch. When the separate worker recovery mode is enforce (the unset default), Microsoft OAuth or tenant-consent seats get a credential-free vendor reactivation, and stalled dispatch or DNS readiness is rechecked. Shadow reports candidates in those enabled lanes without their vendor writes; off skips those lanes. Google credential repair can still run in shadow/off. Correct bad DNS records yourself; an active unpaused paid seat in enforce mode needs no manual resume after that correction. OXYGEN never invents consent, resumes a human or safety pause, starts a new paid enrollment, or blindly repeats an ambiguous provider write. Check `warmup status` and `mailboxes list` for the exact next action.")
         .addHelpText("after", "\nDocs: https://oxygen-agent.com/docs/providers/mailboxes\n")
         .addCommand(new Command("enable")
         .description("Optional provider warm-up defaults to 1/day, +1/day, max 10/day (dedicated-tenant profiles stay stricter); see `mailboxes warmup config` for the effective plan and unsupported OXYGEN Warm-up reply-rate control. This is separate from the 5/10/20 campaign ramp. STANDALONE ENROLLMENT: enroll BYOK/imported mailboxes, a managed order that opted out, or mailboxes being added to warmup later. Fresh managed InboxKit Google/Microsoft/Azure orders whose approved quote included warmup activate automatically after provisioning and do not need this command. Targets the whole pool unless --mailboxes is given; one synchronous preview/approval is capped at 220 mailboxes, so split larger pools into explicit batches. Without --approved this is a 0-credit, no-provider-write priced preview: nothing is handed off, enrolled, or billed. The price is 100 credits per warming mailbox-month, or 0 once warm-up is included in the mailbox's 100-credit monthly connection (2026-09 repricing; the preview's included_in_connection says which, and its max_credits is then 0); the preview returns the exact first-cycle ceiling. Preview one inbox with `oxygen mailboxes warmup enable --mailboxes sender@example.com --json`. Execute by echoing its --plan and --max-credits with --approved. Eligible managed Google targets use the InboxKit-held credential just in time without storing or returning it; Microsoft/Azure targets use native InboxKit Sequencer export with exact UIDs and auto-export off. Any non-cancelled InboxKit warmup must be cancelled before either handoff (pausing is not enough). Only eligible non-InboxKit Microsoft mailboxes need `mailboxes warmup microsoft`. OXYGEN Warm-up retains no campaign authority — OXYGEN Sequences own enrollment and dispatch. New enrollments only ever land on the managed OXYGEN rail; the retired TrulyInbox rail is refused here and only accepts teardown.")
@@ -18075,7 +18224,7 @@ Examples:
         });
     }))
         .addCommand(new Command("reconnect")
-        .description("Manual repair for an existing live paid seat when worker recovery is shadow/off, exhausted, or needs a new credential: push the mailbox's CURRENT credential to its warmup provider. Use this when a new app password is needed because the old one was rotated or revoked (the provider reporting 'Username and Password not accepted'): re-import the new credential with `mailboxes import`, then run this. It costs 0 credits and leaves your warmup subscription and its renewal date exactly as they are — you do NOT need to disable and re-enable warmup, which would charge a second month. The provider cannot change a stored password in place, so the inbox's warmup history restarts from day 1. Targets the whole pool unless --mailboxes is given.")
+        .description("Manual repair for an existing live paid seat when automatic credential repair is disabled, exhausted, or needs a new credential: push the mailbox's CURRENT credential to its warmup provider. Use this when a new app password is needed because the old one was rotated or revoked (the provider reporting 'Username and Password not accepted'): re-import the new credential with `mailboxes import`, then run this. It costs 0 credits and leaves your warmup subscription and its renewal date exactly as they are — you do NOT need to disable and re-enable warmup, which would charge a second month. The provider cannot change a stored password in place, so the inbox's warmup history restarts from day 1. Targets the whole pool unless --mailboxes is given.")
         .option("--mailboxes <list>", "Comma-separated mailbox ids or addresses. Omit for the whole pool.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
@@ -18217,7 +18366,7 @@ Examples:
         }));
     }))
         .addCommand(new Command("list")
-        .description("Inspect recent directional inbox-placement tests, their status, results, and credits used, plus `pricing`: the EmailGuard monitoring credits per inbox-month and the managed test price in force (0 on your own EmailGuard key). The returned web link opens Accounts; use get for an exact result link. Costs 0 credits and never creates or sends a test; active tests may refresh their observations.")
+        .description("Inspect recent directional inbox-placement tests, their status, results, and credits used, plus `pricing`: EmailGuard monitoring credits per inbox-month, two included tests per inbox per cycle, and the managed extra-test price in force (0 on your own EmailGuard key). The returned web link opens Accounts; use get for an exact result link. Costs 0 credits and never creates or sends a test; active tests may refresh their observations.")
         .option("--limit <n>", "Max rows (default 50, cap 200).")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
@@ -18234,7 +18383,7 @@ Examples:
         await handleAsyncAction("deliverability placement-test get", options, () => requestOxygen(`/api/cli/deliverability/placement-tests/${encodeURIComponent(id)}`));
     }))));
     program.addCommand(new Command("domains")
-        .description("Cold-email domains: sync zones from your own Cloudflare account (BYOK), inspect age/warmup/DNS health, check availability and pricing, buy domains, and archive or delete domains with their inboxes (OXYGEN-bought domains included). Purchases bill your Cloudflare payment method, never Oxygen credits.")
+        .description("Cold-email domains: sync zones from your own Cloudflare account (BYOK), inspect age/warmup/DNS health, check availability and pricing, buy domains, and archive or delete domains with their inboxes (OXYGEN-bought domains included). Your own Cloudflare account bills purchases to its payment method; domains registered by OXYGEN cost credits at the vendor price. Preview `domains buy` before approval.")
         .addCommand(new Command("list")
         .description("List the org's cached Cloudflare domains with cold-email metadata (age, mailboxes, warmup, sending volume, DNS health). Each row's `dns` object explains the status (ok, issues, not checked, check failed, partial check, no zone) with a reason and fix path; `managed_domains` lists InboxKit-managed bundle domains (vendor-registered + vendor-DNS'd — manage via `managed-inboxes`), each carrying `internal_billing_status` (ok|past_due) and `last_billed_cycle_key` — a domain the vendor keeps live can still be one OXYGEN could not renew. Reads the cache only — run `domains sync` to refresh.")
         .option("--status <status>", "Filter by zone status: unknown, initializing, pending, active, moved, or deleted.")
@@ -19591,6 +19740,7 @@ Full trigger schema: oxygen workflows schema --subject trigger --json
     registerFunctionsCommands(program, handleAsyncAction);
     registerUgcCommands(program, handleAsyncAction);
     registerKnowledgeRepositoryCommands(program, handleAsyncAction);
+    registerConnectorsCommands(program, handleAsyncAction);
     // Last, so every command registered above is covered — including the ones the
     // register* helpers add after applyOxygenHelp.
     enableCommandSuggestions(program);
@@ -20971,7 +21121,7 @@ function printColumnCatalog(result) {
     lines.push("Add one: oxygen columns add <table> --prompt-key <key> --input <input>=<column_key>, then `columns run <table> <key> --dry-run` for the exact cost.");
     // The blind acceptance judge watched an agent filter this list with python3
     // because nothing on screen said the command can narrow itself.
-    lines.push("Narrow this list: --family pricing|job_posting|events|filings|site_facts|market|portfolio|text_extraction, --category extract, --search <word>, --kind research|ai|formula. Credits are the reserved ceiling per row (primary lane + fallback); a typical row spends the primary lane only.");
+    lines.push("Narrow this list: --family pricing|job_posting|events|filings|site_facts|market|portfolio|text_extraction, --category extract, --search <word>, --kind research|ai|formula. Template credits may reserve primary and fallback lanes; Classify has the fixed per-row price shown in its entry.");
     process.stderr.write(`${lines.join("\n")}\n`);
 }
 function applyAiColumnConfig(definition, options) {
@@ -25928,9 +26078,11 @@ function renderTextTable(headers, rows) {
     return [renderRow(headers), separator, ...rows.map(renderRow)];
 }
 // Sequence state is derived only by the shared API. These helpers render those
-// facts; they never infer flowing/blocked/live client-side. JSON remains the
-// untouched API data inside the standard CLI envelope.
-const SEQUENCE_OPERATIONAL_STATE_ORDER = ["empty", "drained", "never_started", "blocked", "degraded", "flowing", "paced"];
+// facts; they never infer flowing/blocked/live client-side. The one label drawn
+// from them, completed, is the server's `lifecycle` (the shared helper covers a
+// server that predates it). JSON remains the untouched API data inside the
+// standard CLI envelope.
+const SEQUENCE_OPERATIONAL_STATE_ORDER = ["empty", "drained", "never_started", "blocked", "degraded", "flowing", "paced", "paused"];
 /**
  * `crm objects`, as an operator reads it.
  *
@@ -26164,6 +26316,9 @@ function formatSequenceListHealth(data) {
     }
     else {
         lines.push(...renderTextTable(["SEQUENCE", "PERSISTED", "OPERATIONAL", "OPEN WORK", "SENT / FAILED", "REASONS"], sequences.map((sequence) => sequenceHealthRow(sequence))));
+        const warnings = sequenceRowWarnings(sequences);
+        if (warnings.length > 0)
+            lines.push("", ...warnings);
         lines.push("", ...sequenceInspectionLinks(sequences));
     }
     const listLink = stringValue(data.web_url) ?? stringValue(data.deepLink);
@@ -26290,14 +26445,23 @@ function formatSequenceReplyRollup(replies) {
 function formatSequenceStatsHealth(data) {
     const stats = recordValue(data.stats);
     const operational = recordValue(stats.operational);
+    const budget = recordValue(data.daily_budget);
     const lines = [
         stringValue(data.name) ?? stringValue(data.sequence_id) ?? "Sequence",
         `Persisted status: ${stringValue(data.status) ?? "unknown"}`,
-        `Operational state: ${stringValue(operational.operationalState) ?? "unknown (legacy response)"}`,
+        `Operational state: ${operationalStateText(data, operational) ?? "unknown (legacy response)"}`,
         `Open work: ${formatSequenceOpenWork(operational.openWork)}`,
         `Reasons: ${formatSequenceReasons(operational)}`,
         `${formatFailureWindow(operational.failureAnalytics)} outcomes: ${formatSequenceFailureTotals(operational.failureAnalytics)}`,
     ];
+    const sentToday = numericValue(budget.sends_used);
+    if (sentToday !== null) {
+        const reserved = numericValue(budget.sends_reserved);
+        const remaining = numericValue(budget.sends_remaining);
+        lines.push(`Today${stringValue(budget.day) ? ` (${budget.day} UTC)` : ""}: ${sentToday} sent`
+            + (reserved === null ? "" : ` · ${reserved} reserved`)
+            + ` · ${remaining === null ? "unlimited" : remaining} available`);
+    }
     const failureMix = formatCountRecord(recordValue(recordValue(operational.failureAnalytics).byFailureClass));
     if (failureMix !== "—")
         lines.push(`Failure mix: ${failureMix}`);
@@ -26373,12 +26537,37 @@ function sequenceHealthRow(sequence) {
     return [
         stringValue(sequence.name) ?? stringValue(sequence.slug) ?? "—",
         stringValue(sequence.status) ?? "unknown",
-        stringValue(operational.operationalState) ?? "unknown",
+        operationalStateText(sequence, operational) ?? "unknown",
         formatSequenceOpenWork(operational.openWork),
         formatSequenceFailureTotals(operational.failureAnalytics),
         formatSequenceReasons(operational),
     ];
 }
+/**
+ * The operational state, naming the lifecycle a person reads when the two
+ * disagree. A campaign that contacted every lead keeps its persisted `active`,
+ * and a blind user eval (2026-09-29) had to infer it was done from `drained`
+ * plus zero open work. The web lists the same Sequence as Completed.
+ */
+function operationalStateText(sequence, operational) {
+    const state = stringValue(operational.operationalState);
+    if (!state)
+        return null;
+    // The server's own `lifecycle`; the shared helper covers a server that predates it.
+    const lifecycle = stringValue(sequence.lifecycle) ?? sequenceDisplayStatus(stringValue(sequence.status) ?? "", state);
+    return lifecycle === "completed" ? `${state} (completed)` : state;
+}
+/** A listed Sequence's launch warnings (e.g. two sending schedules), one line each. */
+function sequenceRowWarnings(sequences) {
+    return sequences.flatMap((sequence) => {
+        const label = stringValue(sequence.name) ?? stringValue(sequence.slug) ?? "Sequence";
+        const warnings = Array.isArray(sequence.warnings) ? sequence.warnings.filter(isRecord) : [];
+        return warnings.flatMap((warning) => {
+            const message = stringValue(warning.message);
+            return message ? [`Warning (${label}): ${message}`] : [];
+        });
+    });
+}
 function sequenceInspectionLinks(sequences) {
     return sequences.flatMap((sequence) => {
         const exactLink = stringValue(sequence.web_url) ?? stringValue(sequence.deepLink);
@@ -26394,27 +26583,38 @@ function formatSequenceFleetSummary(value) {
     // should not read a line of zeroes every time it lists its sequences.
     const neverStarted = typeof fleet.neverStarted === "number" ? fleet.neverStarted : 0;
     const parkedLeads = typeof fleet.neverStartedEnrollments === "number" ? fleet.neverStartedEnrollments : 0;
+    const completed = recordValue(fleet.byLifecycle).completed;
+    const completedText = typeof completed === "number" ? ` · ${numberText(completed)} completed` : "";
     return [
-        `Fleet: ${numberText(fleet.markedActive)} marked active · ${numberText(fleet.operationallyLive)} operationally live · ${numberText(fleet.total)} total`,
+        `Fleet: ${numberText(fleet.markedActive)} marked active · ${numberText(fleet.operationallyLive)} operationally live${completedText} · ${numberText(fleet.total)} total`,
         `States: ${SEQUENCE_OPERATIONAL_STATE_ORDER.map((state) => `${state} ${numberText(states[state])}`).join(" · ")}`,
         ...(neverStarted > 0
             ? [`Never started: ${numberText(neverStarted)} draft${neverStarted === 1 ? "" : "s"} holding ${numberText(parkedLeads)} enrolled lead${parkedLeads === 1 ? "" : "s"} — these send nothing until launched. List them with \`oxygen sequences list --operational-state never_started\`, then check one with \`oxygen sequences get <sequence> --readiness\` (read-only).`]
             : []),
     ];
 }
+/**
+ * Spelled out because a blind user eval (2026-09-29) read `enr 352` as 352
+ * enrolled when it meant 352 leads still in progress, and told the founder the
+ * wrong count. Only the first two counts have a unit: ready, in flight, paced
+ * and blocked add leads with no open action to open actions.
+ */
 function formatSequenceOpenWork(value) {
     const work = recordValue(value);
     if (Object.keys(work).length === 0)
         return "unknown";
-    return [
-        `enr ${numberText(work.enrollments)}`,
-        `act ${numberText(work.actions)}`,
-        `now ${numberText(work.actionableNow)}`,
-        `flight ${numberText(work.inFlight)}`,
-        `paced ${numberText(work.paced)}`,
-        `blocked ${numberText(work.blocked)}`,
-        `unresolved ${numberText(work.unresolvedFailures)}`,
-    ].join(" · ");
+    const counts = [
+        ["leads in progress", work.enrollments],
+        ["open actions", work.actions],
+        ["ready now", work.actionableNow],
+        ["in flight", work.inFlight],
+        ["paced", work.paced],
+        ["blocked", work.blocked],
+        ["unresolved failures", work.unresolvedFailures],
+    ];
+    if (counts.every(([, count]) => count === 0))
+        return "none";
+    return counts.map(([label, count]) => `${label} ${numberText(count)}`).join(" · ");
 }
 function formatSequenceFailureTotals(value) {
     const analytics = recordValue(value);
@@ -28843,6 +29043,7 @@ table, options) {
             : {}),
         ...(options.verifyPhone ? { verify_phone: true } : {}),
         ...(options.allowPremiumLanes ? { allow_premium_lanes: true } : {}),
+        ...(options.includePersonalEmail ? { include_personal_email: true } : {}),
         ...(readOption(options.phoneVerificationCredentialMode)
             ? { phone_verification_credential_mode: readOption(options.phoneVerificationCredentialMode) }
             : {}),
@@ -28868,6 +29069,25 @@ function readLinkedinScheduleOptions(options) {
     }
     return { timezone, days: parseWorkingDaysOption(days), start, end };
 }
+// Launch's one sending schedule and one unsubscribe switch. The server writes
+// `sending_schedule` to the email window and the LinkedIn/WhatsApp window, and
+// `include_unsubscribe` to the visible link and the one-click headers.
+function readUnifiedSequenceBody(options) {
+    const timezone = readOption(options.scheduleTimezone);
+    const days = readOption(options.scheduleDays);
+    const start = readOption(options.scheduleHoursStart);
+    const end = readOption(options.scheduleHoursEnd);
+    const body = {};
+    if (timezone || days || start || end) {
+        if (!timezone || !days || !start || !end) {
+            throw new OxygenError("invalid_sending_schedule", "Set the sending schedule with all four flags: --schedule-timezone, --schedule-days, --schedule-hours-start and --schedule-hours-end.", { exitCode: 1 });
+        }
+        body.sending_schedule = { timezone, days: parseWorkingDaysOption(days), start, end };
+    }
+    if (options.includeUnsubscribe !== undefined)
+        body.include_unsubscribe = options.includeUnsubscribe;
+    return body;
+}
 /**
  * A whole seat count. Unlike readPositiveNumber, ZERO IS VALID and meaningful:
  * `--quantity 0` is how a customer gives back every seat of a channel, and
@@ -29123,8 +29343,6 @@ function readSequenceSettings(options) {
         settings.bounce_protection = JSON.parse(options.bounceProtection);
     if (options.includeUnsubscribeHeaders !== undefined)
         settings.include_unsubscribe_headers = options.includeUnsubscribeHeaders;
-    if (options.replyToStopText !== undefined)
-        settings.reply_to_stop_text = options.replyToStopText;
     if (options.includeUnsubscribeLink !== undefined) {
         settings.include_unsubscribe_link = options.includeUnsubscribeLink;
     }
@@ -29215,23 +29433,31 @@ process.stdout.on("error", (error) => {
 maybeScheduleBackgroundUpdate();
 const program = createProgram();
 installCommanderExitOverride(program);
+const argv = withoutHelpForUnknownCommand(program, process.argv);
 try {
-    await program.parseAsync(process.argv);
+    await program.parseAsync(argv);
 }
 catch (error) {
     if (error instanceof CommanderError) {
-        const cliArgs = process.argv.slice(2);
+        const cliArgs = argv.slice(2);
+        // Every hint goes to stderr as it always has; the first, the most specific,
+        // also becomes the --json envelope's details.next_step below.
+        const hints = [];
+        const writeHint = (hint) => {
+            hints.push(hint);
+            process.stderr.write(`${hint}\n`);
+        };
         if (error.code === "commander.unknownOption" &&
             error.message.includes("unknown option '--json'") &&
             cliArgs.slice(-2).join(" ") === "limits --json") {
-            process.stderr.write(`Hint: --json belongs to the show subcommand. Run \`${program.name()} limits show --json\`.\n`);
+            writeHint(`Hint: --json belongs to the show subcommand. Run \`${program.name()} limits show --json\`.`);
         }
         // `error: unknown command 'get'` names what is wrong and nothing to try
         // next; commander's edit-distance suggester cannot reach a synonym.
         if (error.code === "commander.unknownCommand") {
             const hint = unknownCommandHint(program, cliArgs);
             if (hint)
-                process.stderr.write(`${hint}\n`);
+                writeHint(hint);
         }
         // `error: unknown option '--filter'` on `tables query` got no suggestion
         // either (blind user eval, 2026-09-18): commander caps its suggester at
@@ -29239,7 +29465,7 @@ catch (error) {
         if (error.code === "commander.unknownOption") {
             const hint = unknownOptionHint(program, cliArgs, error.message);
             if (hint)
-                process.stderr.write(`${hint}\n`);
+                writeHint(hint);
         }
         if (error.code === "commander.excessArguments" &&
             cliArgs[0] === "skills" &&
@@ -29252,11 +29478,17 @@ catch (error) {
             const skillArgument = /^[a-z0-9][a-z0-9_-]*$/i.test(requestedSkill)
                 ? requestedSkill
                 : "<name>";
-            process.stderr.write(looksLikePath
-                ? `Hint: --project takes no value; it installs into the current directory. Did you mean \`${program.name()} skills install --project\`?\n`
-                : `Hint: skill names use the --skill option. Did you mean \`${program.name()} skills install --skill ${skillArgument}\`?\n`);
-        }
-        process.exitCode = error.exitCode;
+            writeHint(looksLikePath
+                ? `Hint: --project takes no value; it installs into the current directory. Did you mean \`${program.name()} skills install --project\`?`
+                : `Hint: skill names use the --skill option. Did you mean \`${program.name()} skills install --skill ${skillArgument}\`?`);
+        }
+        // Commander refused before any action ran, so no handler printed the --json
+        // envelope; agents parse stdout and branch on the exit code, and the exit
+        // table classes a usage error as 2 in every mode.
+        const usage = commanderUsageFailure(program, cliArgs, error, hints[0] ?? null);
+        if (usage && argvRequestsJson(cliArgs))
+            writeJson(usage.envelope);
+        process.exitCode = usage?.exitCode ?? error.exitCode;
     }
     else {
         throw error;