@oxygen-agent/cli 1.1021.7 → 1.1022.49

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (54) hide show
  1. package/README.md +1 -1
  2. package/dist/command-families/program.js +2 -0
  3. package/dist/command-families/tables/bundle-export.d.ts +2 -1
  4. package/dist/command-families/tables/bundle-export.js +14 -3
  5. package/dist/command-manifest.js +2 -0
  6. package/dist/command-support.d.ts +6 -0
  7. package/dist/command-support.js +61 -9
  8. package/dist/commands/agent.js +2 -2
  9. package/dist/commands/approvals.js +3 -52
  10. package/dist/commands/billing.js +5 -5
  11. package/dist/commands/context.js +2 -2
  12. package/dist/commands/copilot.js +1 -1
  13. package/dist/commands/knowledge.js +2 -2
  14. package/dist/commands/members.d.ts +7 -0
  15. package/dist/commands/members.js +32 -0
  16. package/dist/commands/orgs.js +1 -1
  17. package/dist/commands/publishing.js +36 -2
  18. package/dist/commands/recipes.js +1 -1
  19. package/dist/commands/sequences.js +4 -4
  20. package/dist/commands/suppressions.js +2 -2
  21. package/dist/commands/verify.js +1 -1
  22. package/dist/commands/workspace-export.d.ts +61 -0
  23. package/dist/commands/workspace-export.js +565 -0
  24. package/dist/commands/workspace.js +24 -1
  25. package/dist/help.js +6 -1
  26. package/node_modules/@oxygen/shared/dist/access/permissions.d.ts +101 -0
  27. package/node_modules/@oxygen/shared/dist/access/permissions.js +129 -0
  28. package/node_modules/@oxygen/shared/dist/access/roles.d.ts +73 -0
  29. package/node_modules/@oxygen/shared/dist/access/roles.js +116 -0
  30. package/node_modules/@oxygen/shared/dist/agents/sessions.js +2 -1
  31. package/node_modules/@oxygen/shared/dist/agents/teammates.js +2 -1
  32. package/node_modules/@oxygen/shared/dist/capability-intents/collaboration.js +7 -6
  33. package/node_modules/@oxygen/shared/dist/capability-intents/discovery-and-skills.d.ts +12 -0
  34. package/node_modules/@oxygen/shared/dist/capability-intents/discovery-and-skills.js +54 -0
  35. package/node_modules/@oxygen/shared/dist/capability-intents/discovery-and-skills.rules.d.ts +2 -0
  36. package/node_modules/@oxygen/shared/dist/capability-intents/discovery-and-skills.rules.js +19 -0
  37. package/node_modules/@oxygen/shared/dist/capability-intents/index.generated.js +2 -0
  38. package/node_modules/@oxygen/shared/dist/capability-routes/discovery-and-skills.js +4 -4
  39. package/node_modules/@oxygen/shared/dist/collab.d.ts +0 -29
  40. package/node_modules/@oxygen/shared/dist/collab.js +0 -32
  41. package/node_modules/@oxygen/shared/dist/contracts/browser-operations.js +2 -2
  42. package/node_modules/@oxygen/shared/dist/contracts/customer-operations.js +4 -3
  43. package/node_modules/@oxygen/shared/dist/contracts/publishing-reads.js +1 -1
  44. package/node_modules/@oxygen/shared/dist/copilot/access.d.ts +1 -1
  45. package/node_modules/@oxygen/shared/dist/copilot/access.js +2 -1
  46. package/node_modules/@oxygen/shared/dist/decision-ledger.generated.js +11 -0
  47. package/node_modules/@oxygen/shared/dist/onboarding/guided-activation.js +3 -1
  48. package/node_modules/@oxygen/shared/dist/product-briefing-rules.js +2 -2
  49. package/node_modules/@oxygen/shared/dist/product-doctrine.js +1 -1
  50. package/node_modules/@oxygen/shared/dist/version.d.ts +1 -1
  51. package/node_modules/@oxygen/shared/dist/version.generated.d.ts +1 -1
  52. package/node_modules/@oxygen/shared/dist/version.generated.js +1 -1
  53. package/node_modules/@oxygen/shared/dist/version.js +1 -1
  54. package/package.json +1 -1
@@ -1678,7 +1678,7 @@ export function registerSequencesFamily(program, handleAsyncAction) {
1678
1678
  .option("--mailboxes <ids>", "Per-sequence sending-account allowlist for native email (Instantly's 'Accounts to use'): comma-separated mailbox ids. Native email sends rotate ONLY over these mailboxes instead of the whole pool. Omit for the whole pool. Note: a narrow allowlist plus --esp-matching strict can starve sends when no allowed same-provider mailbox exists (surfaced as blocked defer reasons in stats).")
1679
1679
  .option("--sender-profiles <ids>", "Send from these sender profiles (unified LinkedIn/WhatsApp/inbox identities): comma-separated profile ids (`oxygen senders profiles list` lists them). The server resolves each into its senders + inboxes. Live start is blocked if a selected profile lacks an account for a channel the journey uses.")
1680
1680
  .option("--no-stop-on-bounce", "Keep a lead's enrollment running after a hard bounce (default: stop it). The bounce is still recorded as an email_bounced signal either way.")
1681
- .option("--exclude-contacted", "Default every enroll into this sequence to cross-campaign exclusion: skip leads whose LinkedIn identity (lead_provider_id) another active sequence is already contacting. Leads without one, such as email- or phone-only leads, are never checked, and enrolling from a table or file stores one only in a sequence with LinkedIn steps unless you pass lead_provider_id. A per-enroll `sequences enroll --exclude-contacted` / `--no-exclude-contacted` always overrides this default. Off by default.")
1681
+ .option("--exclude-contacted", "Default enrolls into this sequence to cross-campaign exclusion: skip leads whose LinkedIn identity (lead_provider_id) is still enrolled in another active sequence. `sequences enroll`, the bound table's auto-enroll and Workflow enroll steps apply this default when they set no value of their own; a signal watch's auto-enroll ignores it, and the HubSpot list import uses its own setting. Leads without one, such as email- or phone-only leads, are never checked, and enrolling from a table or file stores one only in a sequence with LinkedIn steps unless you pass lead_provider_id. A per-enroll `sequences enroll --exclude-contacted` / `--no-exclude-contacted` always overrides this default. Off by default.")
1682
1682
  .option("--no-exclude-contacted", "Turn the sequence-level exclude-contacted default back OFF (enrollments then exclude cross-campaign only when a call opts in).")
1683
1683
  .option("--auto-enroll-table-rows", "Rows added to the sequence's table join it while it is active (a first launch turns this on unless it was turned off).")
1684
1684
  .option("--no-auto-enroll-table-rows", "Keep enrollment manual: launching does not enroll the table, and new rows wait for `sequences enroll`.")
@@ -1828,7 +1828,7 @@ export function registerSequencesFamily(program, handleAsyncAction) {
1828
1828
  .option("--mailboxes <ids>", "Per-sequence sending-account allowlist for native email (Instantly's 'Accounts to use'): comma-separated mailbox ids. Native email sends rotate ONLY over these mailboxes instead of the whole pool. Note: a narrow allowlist plus --esp-matching strict can starve sends when no allowed same-provider mailbox exists (surfaced as blocked defer reasons in stats). \"\" removes the allowlist.")
1829
1829
  .option("--sender-profiles <ids>", "Send from these sender profiles (unified LinkedIn/WhatsApp/inbox identities): comma-separated profile ids (`oxygen senders profiles list` lists them). The server resolves each into its senders + inboxes. Live start is blocked if a selected profile lacks an account for a channel the journey uses.")
1830
1830
  .option("--no-stop-on-bounce", "Keep a lead's enrollment running after a hard bounce (default: stop it). The bounce is still recorded as an email_bounced signal either way.")
1831
- .option("--exclude-contacted", "Default every enroll into this sequence to cross-campaign exclusion: skip leads whose LinkedIn identity (lead_provider_id) another active sequence is already contacting. Leads without one, such as email- or phone-only leads, are never checked, and enrolling from a table or file stores one only in a sequence with LinkedIn steps unless you pass lead_provider_id. A per-enroll `sequences enroll --exclude-contacted` / `--no-exclude-contacted` always overrides this default. Off by default.")
1831
+ .option("--exclude-contacted", "Default enrolls into this sequence to cross-campaign exclusion: skip leads whose LinkedIn identity (lead_provider_id) is still enrolled in another active sequence. `sequences enroll`, the bound table's auto-enroll and Workflow enroll steps apply this default when they set no value of their own; a signal watch's auto-enroll ignores it, and the HubSpot list import uses its own setting. Leads without one, such as email- or phone-only leads, are never checked, and enrolling from a table or file stores one only in a sequence with LinkedIn steps unless you pass lead_provider_id. A per-enroll `sequences enroll --exclude-contacted` / `--no-exclude-contacted` always overrides this default. Off by default.")
1832
1832
  .option("--no-exclude-contacted", "Turn the sequence-level exclude-contacted default back OFF (enrollments then exclude cross-campaign only when a call opts in).")
1833
1833
  .option("--auto-enroll-table-rows", "Rows added to the sequence's table join it while it is active (a first launch turns this on unless it was turned off).")
1834
1834
  .option("--no-auto-enroll-table-rows", "Keep enrollment manual: launching does not enroll the table, and new rows wait for `sequences enroll`.")
@@ -1945,13 +1945,13 @@ export function registerSequencesFamily(program, handleAsyncAction) {
1945
1945
  await handleAsyncAction("sequences get", options, () => requestOxygen(`/api/cli/sequences/${encodeURIComponent(sequence)}${query}`));
1946
1946
  }))
1947
1947
  .addCommand(new Command("enroll")
1948
- .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. In a mixed journey a row with no usable LinkedIn profile still enrolls when its email or phone reaches another step, or it has a stable table_row_id or lead_provider_id for crm_task steps. CRM tasks do not require email, LinkedIn or phone; their configured record identities and property mappings are validated when planned. Missing-channel steps are skipped; LinkedIn skips use no_linkedin_profile, a connection wait passes at once and a connection branch takes its not-connected path. These rows appear in linkedin_unavailable_lead_details; unresolved_linkedin_leads names only rows that were not enrolled. --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 + email sequence auto-files an email-only lead the same way; 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; in a sequence with LinkedIn steps a lead with a lead_profile_url and no table_row_id is filed the same way, onto the person's existing row in the bound table (another spelling of the same profile URL matches) or as a new row, deduped by profile URL, and a person the sequence already holds keeps that enrollment; where the sequence has no table and every new table needs a client signoff the enroll is refused instead (sequence_leads_table_needs_signoff). Like any table-row lead a filed one cannot re-enroll in that sequence once its enrollment ends; leads_without_table_row counts the leads in the request that no table lists (those given only a lead_provider_id, and people the sequence already holds without a row). A CRM-task lead in a CRM-only or mixed journey 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 or profile URL for auto-filed leads). WhatsApp-only campaigns also enroll each normalized number once across all source rows and enrollment statuses; mixed campaigns keep other channels and skip duplicate WhatsApp actions. Duplicate protection defaults to this campaign; --whatsapp-duplicate-scope on create/update can additionally block identical copy across all campaigns. 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`. esp.pool_scope identifies the active workspace inventory used for routing and strict_deferred_leads estimates; these estimates omit sequence sender restrictions, readiness and daily limits. A zero estimate does not guarantee readiness. Review sequences preview before launch.")
1948
+ .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. In a mixed journey a row with no usable LinkedIn profile still enrolls when its email or phone reaches another step, or it has a stable table_row_id or lead_provider_id for crm_task steps. CRM tasks do not require email, LinkedIn or phone; their configured record identities and property mappings are validated when planned. Missing-channel steps are skipped; LinkedIn skips use no_linkedin_profile, a connection wait passes at once and a connection branch takes its not-connected path. These rows appear in linkedin_unavailable_lead_details; unresolved_linkedin_leads names only rows that were not enrolled. --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 + email sequence auto-files an email-only lead the same way; 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; in a sequence with LinkedIn steps a lead with a lead_profile_url and no table_row_id is filed the same way, onto the person's existing row in the bound table (another spelling of the same profile URL matches) or as a new row, deduped by profile URL, and a person the sequence already holds keeps that enrollment; where the sequence has no table and every new table needs a client signoff the enroll is refused instead (sequence_leads_table_needs_signoff). Like any table-row lead a filed one cannot re-enroll in that sequence once its enrollment ends; leads_without_table_row counts the leads in the request that no table lists (those given only a lead_provider_id, and people the sequence already holds without a row). A CRM-task lead in a CRM-only or mixed journey 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 or profile URL for auto-filed leads). WhatsApp-only campaigns also enroll each normalized number once across all source rows and enrollment statuses; mixed campaigns keep other channels and skip duplicate WhatsApp actions. Duplicate protection defaults to this campaign; --whatsapp-duplicate-scope on create/update can additionally block identical copy across all campaigns. The org do-not-contact list is always checked, by exact match: a lead is skipped when its provider id or normalized LinkedIn profile URL equals a person entry (on_suppress_list), or when a company domain or LinkedIn company URL in its row is on the list (on_company_suppress_list); --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`. esp.pool_scope identifies the active workspace inventory used for routing and strict_deferred_leads estimates; these estimates omit sequence sender restrictions, readiness and daily limits. A zero estimate does not guarantee readiness. Review sequences preview before launch.")
1949
1949
  .argument("<sequence>", "Sequence id or slug.")
1950
1950
  .option("--leads-file <path>", "Path to a JSON file: { \"leads\": [{ row_values: { email }, lead_name }] } for cold email; { lead_profile_url, lead_name, row_values } or { lead_provider_id, lead_name, table_row_id, row_values } for LinkedIn/existing rows; CRM-task leads in single/mixed journeys 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, --from-table or --from-list.")
1951
1951
  .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, --from-table or --from-list.")
1952
1952
  .option("--from-list <idOrKey>", "Sending-domain Sequences: enroll up to 500 subscribed addresses of the Sequence's own subscription list per run, each filed as an email-only lead in its leads table (another list is refused: sequence_from_list_mismatch). Re-run with --from-list-after <from_list.next_after> while from_list.has_more.")
1953
1953
  .option("--from-list-after <email>", "With --from-list: continue after this address (the previous run's from_list.next_after).")
1954
- .option("--exclude-contacted", "Also skip leads whose LinkedIn identity (lead_provider_id) another active sequence is already contacting (cross-campaign exclusion), for THIS enroll; email- or phone-only leads, and leads of a sequence without LinkedIn steps that carry no explicit lead_provider_id, are never checked. Off by default; forces exclusion on even if the sequence's exclude_contacted default is off.")
1954
+ .option("--exclude-contacted", "Also skip leads whose LinkedIn identity (lead_provider_id) is still enrolled in another active sequence (cross-campaign exclusion), for THIS enroll; email- or phone-only leads, and leads of a sequence without LinkedIn steps that carry no explicit lead_provider_id, are never checked. Without this flag or --no-exclude-contacted, the sequence's exclude_contacted default applies (off unless set); this flag forces exclusion on even when that default is off.")
1955
1955
  .option("--no-exclude-contacted", "Force-INCLUDE cross-campaign leads for this enroll even when the sequence's exclude_contacted default is on (per-call override).")
1956
1956
  .option("--suppress-list <ids>", "Per-call do-not-enroll lead provider ids dropped for this enroll only: a comma-separated list, or @<path> to a file of ids (comma/whitespace separated).")
1957
1957
  .option("--ignore-sender-bindings", "Enroll leads even when they are already owned by a sender account outside this sequence's pool (overrides the one-person-one-sender guarantee). Off by default.")
@@ -35,7 +35,7 @@ export function registerSuppressionsFamily(program, handleAsyncAction) {
35
35
  program.addCommand(new Command("suppressions")
36
36
  .description("Unified do-not-contact controls for people and typed identities. `policy` decides WHO GETS ADDED automatically -- which replies, bounces, unsubscribes and call outcomes add an identity to the list (an email event adds only the address), and whether each one blocks it forever or only stops the current campaign. `crm-backfill` files the people already on the list into your CRM. `import-person` bundles one contact's email, LinkedIn, phone, and explicit company domain; `import` preserves the legacy mixed-file contract; `import-identities` is the integration-level typed endpoint; `hubspot lists|sync` arms additive synchronization. Company DNC applies across Sequence channels and is never inferred from a person's email. Consumes 0 credits.")
37
37
  .addCommand(new Command("policy")
38
- .description("Do-not-contact RULES: who gets added to the list automatically. Seven events can add someone -- an email hard bounce, a one-click unsubscribe, opt-out wording in a reply, ANY inbound LinkedIn reply, ANY inbound WhatsApp reply, and the do-not-call / wrong-number call outcomes -- plus an optional rule per inbox reply classification. Each rule is off, stop_only (end this campaign but do not block future ones) or suppress (the default for all seven, and what every version before this did). Blocking itself is never configurable: an entry always blocks the identity it holds, and an email entry blocks email steps only. Consumes 0 credits.")
38
+ .description("Do-not-contact RULES: who gets added to the list automatically. Eight events can add someone -- an email hard bounce, a one-click unsubscribe, a spam complaint, opt-out wording in a reply, ANY inbound LinkedIn reply, ANY inbound WhatsApp reply, and the do-not-call / wrong-number call outcomes -- plus an optional rule per inbox reply classification. Each rule is off, stop_only (end this campaign but do not block future ones; not offered for the two call outcomes) or suppress (the default for all eight; the reply-classification rules default to off). Blocking itself is never configurable: an entry always blocks the identity it holds, and an email entry blocks email steps only. Consumes 0 credits.")
39
39
  .addCommand(new Command("show")
40
40
  .description("Show every do-not-contact rule with its current setting, whether that is your change or the shipped default, and the values it accepts.")
41
41
  .option("--json", "Print a JSON envelope.")
@@ -128,7 +128,7 @@ export function registerSuppressionsFamily(program, handleAsyncAction) {
128
128
  });
129
129
  }))
130
130
  .addCommand(new Command("add")
131
- .description("Add or refresh selected lead ids on the org do-not-contact list so the sequencer never enrolls them again. Use --lead or --leads (1-500). Idempotent; --reason defaults to manual.")
131
+ .description("Add or refresh selected lead provider ids on the org do-not-contact list; enrollment skips, and each step rechecks, a lead whose provider id or normalized LinkedIn profile URL equals one. Ids are stored as typed, so a URL matches a lead's profile URL only in the form https://www.linkedin.com/in/<lowercase handle>. Use --lead or --leads (1-500). Idempotent; --reason defaults to manual.")
132
132
  .option("--lead <provider_id>", "One lead provider id to suppress; exclusive with --leads.")
133
133
  .option("--leads <ids>", "Comma-separated lead provider ids to suppress in one bounded batch (1-500).")
134
134
  .option("--reason <reason>", "Why: manual (default), replied, unsubscribed, bounced, do_not_contact, friends.")
@@ -14,7 +14,7 @@ export function registerVerifyFamily(program, handleAsyncAction) {
14
14
  .description("Verify one or more email addresses. MillionVerifier answers first; eligible catch-all (accept-all) addresses escalate to BounceBan when available. Returns valid / invalid / catch_all / unknown per address. If escalation cannot run, catch_all stays unconfirmed; escalation_unavailable_reason and next_action explain why. On the managed lane, Oxygen staff own dry provider balances, credential repair and hold release; workspace credits do not fix those blockers. A free preview reports an availability snapshot, not guaranteed live readiness. See https://oxygen-agent.com/docs/providers/email-verification and the oxygen-enrichment skill (`oxygen skills get oxygen-enrichment --file references/verification.md --json`).")
15
15
  .argument("<emails...>", `One or more email addresses to verify, up to ${EMAIL_VERIFICATION_LIST_MAX.toLocaleString("en-US")}. A live run sends them in pages of ${EMAIL_VERIFICATION_LIVE_PAGE_MAX} under one --max-credits ceiling.`)
16
16
  .option("--mode <mode>", "dry_run (default) previews the plan and spends nothing; live spends credits and returns the answer.")
17
- .option("--approved", "Same as --mode live. Accepted because the global help footer names --approved as the way to authorize a credit-spending command.")
17
+ .option("--approved", "Same as --mode live. Accepted because other paid runs authorize spend with --approved.")
18
18
  .option("--max-credits <credits>", "Spend ceiling for the whole run. Required for --mode live. The free dry_run returns estimate.recommended_max_credits, which covers the estimated maximum subject to live provider availability and eligibility; it is a ceiling, not a charge or a guaranteed verdict. Re-verifying the exact same address in this workspace replays MillionVerifier's first pass free for up to 30 days, so a repeat run can report credits_used 0 — catch-all escalation is never cached, and its reservation is released in full when that call returns no verdict.")
19
19
  .option("--json", "Print a JSON envelope.")
20
20
  .action(async (emails, options) => {
@@ -0,0 +1,61 @@
1
+ import { requestOxygen } from "../http-client.js";
2
+ export declare const WORKSPACE_EXPORT_PARTS: readonly ["tables", "crm", "knowledge", "workflows", "sequences", "dashboards", "tags", "folders", "do_not_contact", "settings"];
3
+ export type WorkspaceExportPart = (typeof WORKSPACE_EXPORT_PARTS)[number];
4
+ export declare const WORKSPACE_EXPORT_FORMAT = "oxygen-workspace-export";
5
+ export declare const WORKSPACE_EXPORT_FORMAT_VERSION = 1;
6
+ export declare const WORKSPACE_EXPORT_NOT_INCLUDED: readonly [{
7
+ readonly what: "Connections, API keys, OAuth tokens and mailbox credentials OXYGEN stores";
8
+ readonly why: "Never exported; reconnect each account wherever you restore. A secret typed into a column or workflow definition is part of that definition and is exported as written.";
9
+ }, {
10
+ readonly what: "Unibox conversations and message history";
11
+ readonly why: "Not part of this export yet.";
12
+ }, {
13
+ readonly what: "Sequence enrollments and send history";
14
+ readonly why: "Not part of this export yet; sequences/ holds each sequence's definition and settings.";
15
+ }, {
16
+ readonly what: "CRM notes, tasks, files and activity timelines";
17
+ readonly why: "Not part of this export yet. CRM companies, people and deals are in tables/, their object definitions in crm-objects.json.";
18
+ }, {
19
+ readonly what: "Links between tables and records";
20
+ readonly why: "Table bundles carry no relation edges; re-create them with `oxygen tables relate` and `oxygen tables link` after importing.";
21
+ }, {
22
+ readonly what: "Saved table views, feeds, webhooks, schedules and auto-run or auto-dedupe settings";
23
+ readonly why: "Not part of this export yet; each table's columns and rows are.";
24
+ }, {
25
+ readonly what: "Prompt templates, email assets, spintax, Functions, custom HTTP integrations and sender profiles";
26
+ readonly why: "Not part of this export yet.";
27
+ }, {
28
+ readonly what: "Members, roles, billing and personal preferences";
29
+ readonly why: "Not part of this export; settings.json holds the workspace-wide settings the CLI can read.";
30
+ }, {
31
+ readonly what: "Archived tables and wiki pages, and pending knowledge proposals";
32
+ readonly why: "Only live tables and pages are exported; workflows and sequences are exported whatever their status.";
33
+ }, {
34
+ readonly what: "The wiki's activity log, earlier page revisions and pages shared from other workspaces";
35
+ readonly why: "Not part of this export yet; knowledge/ holds the current version of each page this workspace owns.";
36
+ }, {
37
+ readonly what: "Agents, posts, signals, ads and knowledge files";
38
+ readonly why: "Not part of this export yet.";
39
+ }];
40
+ export type WorkspaceExportRequest = typeof requestOxygen;
41
+ type ExportOptions = {
42
+ output: string;
43
+ parts: readonly WorkspaceExportPart[];
44
+ /** Human-mode progress, one line per step; never written to stdout. */
45
+ progress?: (line: string) => void;
46
+ };
47
+ type ExportDependencies = {
48
+ request?: WorkspaceExportRequest;
49
+ wait?: (ms: number) => Promise<void>;
50
+ now?: () => Date;
51
+ };
52
+ /** `--only` → parts, accepting `do-not-contact` for `do_not_contact`. */
53
+ export declare function readWorkspaceExportParts(value: string | undefined): WorkspaceExportPart[];
54
+ export declare function exportWorkspace(options: ExportOptions, dependencies?: ExportDependencies): Promise<Record<string, unknown>>;
55
+ /**
56
+ * Every export call is a read, so a rate limit or a dropped connection is
57
+ * waited out and retried instead of failing a long export. Anything else
58
+ * surfaces at once.
59
+ */
60
+ export declare function retryingRead(request: WorkspaceExportRequest, wait: (ms: number) => Promise<void>, progress: (line: string) => void): WorkspaceExportRequest;
61
+ export {};