@oxygen-agent/cli 1.1011.468 → 1.1011.487

package/README.md

@@ -34,4 +34,4 @@ oxygen update
 
 For product documentation, visit https://oxygen-agent.com/docs. For support, visit https://oxygen-agent.com.
 
-Version: 1.1011.468
+Version: 1.1011.487

package/dist/index.js

@@ -7569,7 +7569,7 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         .option("--on <column>", "Pin one table's column by name or key. Oxygen must still find a compatible column on the other table: generic text needs a strongly similar label, while domains, emails, LinkedIn URLs, and external IDs pair by semantic role.")
         .option("--approved", "Queue the bulk link after inspecting the preview; then wait with `oxygen table-runs wait <run_id>`.")
         .option("--create-missing", "Also create target rows for unmatched source keys (CRM records when filling an existing CRM relationship). Free.")
-        .option("--max-concurrency <n>", "Maximum concurrent row items for the run (1-250). Defaults to 250; native --create-missing runs serialize target-row creation safely.")
+        .option("--max-concurrency <n>", "Maximum concurrent row items for the run (1-1000; a ceiling shared with worker and provider capacity). Defaults to 250; native --create-missing runs serialize target-row creation safely.")
         .option("--undo <run_id>", "Undo a previous link run, archiving only the links that run created.")
         .option("--relation <slug>", "Row form: relation slug defined on the source table, such as client.")
         .option("--target-row-id <row_id>", "Row form: target row id in the related table.")
@@ -7656,7 +7656,7 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         .option("--row-id <id...>", "Promote only these row ids. Defaults to every bound row.")
         .option("--dry-run", "Preview per-field would_fill/would_overwrite/conflicts without writing (the default when --approved is absent).")
         .option("--approved", "Confirm the truth write onto CRM records after inspecting the preview.")
-        .option("--max-concurrency <n>", "Maximum concurrent row items for the run (1-250). Defaults to 50.")
+        .option("--max-concurrency <n>", "Maximum concurrent row items for the run (1-1000; a ceiling shared with worker and provider capacity). Defaults to 50.")
         .option("--json", "Print a JSON envelope.")
         .action(async (table, options) => {
         if (options.dryRun && options.approved) {
@@ -9653,7 +9653,7 @@ Examples:
         .option("--prompt <text-or-file>", "AI or research column prompt, or a path to a prompt file — a value that resolves to a readable file is read as one, matching --prompt everywhere else in this CLI. On its own it sets kind=ai; pair it with --kind research to make it a Web Research Agent that searches the web per row. If the prompt names its output sections — a line reading 'Return the following sections:' followed by 'Score: ...', 'Reasoning: ...' — the column answers in exactly that shape and each section becomes a referenceable sub-column; otherwise it answers in plain text. Use --no-structured-output to keep it plain text either way. Reference other columns inline as {{column_key}} — no --input-mapping needed; unknown keys are rejected here instead of failing per row. Merges into --definition-json (the escape hatch for everything else); a `prompt` in both is an error.")
         .option("--prompt-key <key>", "Add a column template from `oxygen columns catalog` (e.g. pricing_plan_summary_v1 reads a pricing-page URL column and returns plan count, price range and enterprise plan; company_founders_v1 reads a domain column and returns the founders with sources; person_skill_set_v1 reads the person_enrich payload column with --input profile=person_enrich). Materializes the template's prompt, output schema and grounding and sets its kind (ai, research, formula, or search — a managed web search whose cell is a page URL). Bind each declared input with --input <name>=<column_key>.")
         .option("--input-mapping <json>", "JSON alternative to --input for --prompt-key: an object mapping template input names to columns, e.g. '{\"url\":{\"column\":\"pricing_url\"}}' (a bare column-key string or {\"literal\": ...} also works). Copy templates (email_draft_v1, subject_line_variants_v1, ...) reject mappings built only from manual name/title/company columns — ground them on a research or enrichment column, or write a freeform prompt with --prompt instead.")
-        .option("--model <openrouter-model-id>", "BYOK only: the model to run on your own OpenRouter key. Managed columns pick a tier with --reasoning-level.")
+        .option("--model <openrouter-model-id>", "OpenRouter model id. Managed columns accept allow-listed models and bill by Oxygen tier; --reasoning-level selects a tier. BYOK uses your own key and provider pricing.")
         .option("--reasoning-level <level>", REASONING_LEVEL_OPTION_HELP)
         .option("--run-condition <formula>", "Formula expression gating whether the AI column runs per row. A formula over bare column keys (eu_israel = true), not {{tokens}}.")
         .option("--run-condition-columns <csv>", "Comma-separated column keys referenced by --run-condition.")
@@ -9930,7 +9930,7 @@ Examples:
         .option("--approved", "Confirm a paid durable run, or a bind create-mode run (onNoMatch=create), after inspecting a dry run or preview.")
         .option("--approved-effect-unknown", "With --row-id, allow rerunning a cell whose previous external write was dispatched but never confirmed. Verify the destination first: this can apply the same external effect twice.")
         .option("--max-credits <n>", "Maximum managed model/provider/web-grounding credits to reserve. BYOK covers the model call only; managed grounding still needs this ceiling.")
-        .option("--max-concurrency <n>", "Maximum concurrent row items for a background run (1-250). Defaults to 250 for AI columns and 50 otherwise (160 for Firecrawl scrape columns).")
+        .option("--max-concurrency <n>", "Maximum concurrent row items for a background run (1-1000; a ceiling shared with worker and provider capacity). Defaults to 250 for AI columns and 50 otherwise (160 for Firecrawl scrape columns).")
         .option("--local", "Run a custom HTTP column in this CLI process, where {env:...} secrets read your own machine's environment. Without it the column runs in the background on Oxygen and the same reference resolves from this workspace's registered custom integration.")
         .option("--local-concurrency <n>", "Maximum concurrent custom HTTP requests for --local. Defaults to 3.")
         .option("--dry-run", "Preview the model tier, credit estimate, run-condition posture, and — for an AI column — the prompt rendered with one real row's values, without spending any credits.")
@@ -10099,7 +10099,7 @@ Examples:
         .option("--data-type <type>", "New output data type for a lookup column (text, numeric, boolean, jsonb, timestamptz). Discards the cached cells; other column kinds use `oxygen columns retype`.")
         .option("--prompt <text-or-file>", "Replacement AI column prompt, or a path to a prompt file. Reference other columns inline as {{column_key}}; unknown keys are rejected here instead of failing per row. Merges into --definition-json; a `prompt` in both is an error.")
         .option("--input-mapping <json>", "Replace the column's named inputs wholesale. Row columns belong in the prompt as {{column_key}}; use this for the inputs a prompt cannot name on its own — literals and workspace context ({\"icp\":{\"type\":\"context_profile\",\"path\":\"icp\"}}), which the prompt then reads as {{icp}}. Pass {} to clear it; --definition-json can only add mapping keys, never remove one.")
-        .option("--model <openrouter-model-id>", "BYOK only: the model to run on your own OpenRouter key. Managed columns pick a tier with --reasoning-level.")
+        .option("--model <openrouter-model-id>", "OpenRouter model id. Managed columns accept allow-listed models and bill by Oxygen tier; --reasoning-level selects a tier. BYOK uses your own key and provider pricing.")
         .option("--reasoning-level <level>", REASONING_LEVEL_OPTION_HELP)
         .option("--run-condition <formula>", "Formula expression gating whether the AI column runs per row. A formula over bare column keys (eu_israel = true), not {{tokens}}.")
         .option("--run-condition-columns <csv>", "Comma-separated column keys referenced by --run-condition.")
@@ -10449,7 +10449,7 @@ Examples:
         .option("--connection-id <connection_id>", "Optional provider integration connection id.")
         .option("--approved", "Confirm the paid table action run after inspecting a dry run or preview.")
         .option("--max-credits <n>", "Maximum managed/provider credits to reserve for this run.")
-        .option("--max-concurrency <n>", "Maximum concurrent row items for this run (1-250). Defaults to 50 (160 for Firecrawl scrape columns).")
+        .option("--max-concurrency <n>", "Maximum concurrent row items for this run (1-1000; a ceiling shared with worker and provider capacity). Defaults to 50 (160 for Firecrawl scrape columns).")
         .option("--metadata-json <json>", "Optional metadata object to attach to the run.")
         .option("--idempotency-key <key>", "Reuse the same scoped run when retrying this exact request.")
         .option("--then-json <json>", "JSON array of sequential follow-up steps. Each step runs after the previous terminates with completed or completed_with_errors. Paid steps require selection and max_credits. Shape: [{actions:[{type:'tool_column',column}],selection,force,max_concurrency,max_credits,metadata,run_on_failure}].")
@@ -11542,7 +11542,7 @@ Examples:
     program.addCommand(new Command("egress")
         .description("Native email egress: status, shared/dedicated IP inventory, the dedicated-IP add-on, policy assignments, and a fail-closed retired rotation shim.")
         .addCommand(new Command("status")
-        .description("Show this workspace's actual native egress mode, active IP, health counts, dedicated add-on, and one bounded page of the inspectable mailbox policy ledger. Native Gmail/Microsoft sends, reply reads and token refreshes use the active IP; Zapmail-connected (Zapbox) mailboxes send through Zapmail and never use it. Read-only, 0 credits.")
+        .description("Show this workspace's configured native email routing, active IP, transport readiness, health counts, dedicated add-on, and one bounded page of the mailbox policy ledger. Configuration and readiness do not prove observed traffic. Native Gmail/Microsoft sends, reply reads and token refreshes are configured for the workspace email proxy; Zapmail-connected (Zapbox) mailboxes send through Zapmail. Read-only, 0 credits.")
         .option("--assignment-offset <number>", "Continue the policy ledger from open_assignments_next_offset.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
@@ -11553,7 +11553,7 @@ Examples:
         await handleAsyncAction("egress status", options, () => requestOxygen(`/api/cli/egress${query}`));
     }))
         .addCommand(new Command("ips")
-        .description("List the shared native worker IP (it carries the sends, reply reads and token refreshes of every workspace without a dedicated IP) and this workspace's dedicated IP history. Read-only, 0 credits.")
+        .description("List the configured shared email-proxy IP and this workspace's dedicated IP history. A configured address does not prove observed traffic; inspect readiness and verification fields with `egress status`. Read-only, 0 credits.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
         await handleAsyncAction("egress ips", options, () => requestOxygen("/api/cli/egress?view=ips"));
@@ -11561,7 +11561,7 @@ Examples:
         .addCommand(new Command("dedicated")
         .description("Dedicated native egress add-on (2,500 credits per 30-day period): one static IP only this workspace uses, which IT can allowlist; workspace tenant isolation and account safety, not a deliverability or inbox-placement lever. Preview the quote, order with `request --approved`, cancel with `cancel --approve`, or check status.")
         .addCommand(new Command("request")
-        .description("Preview the dedicated native egress add-on (2,500 credits per 30-day period, $25 face value). With --approved, ORDER it: OXYGEN provisions one isolated send drain plus one static egress IP for the workspace, debits the first period immediately, and debits the next 30 days later — not on the 1st. Every current inbox is assigned to that IP, every future inbox joins it automatically, and after the guarded handoff every send, reply read and token refresh for the workspace's mailboxes uses that one IP, so IT can allowlist it in Microsoft Conditional Access or Google context-aware access. Recipients of Gmail API and Microsoft Graph sends still see Google/Microsoft relay IPs; a Microsoft mailbox on the SMTP transport may show the sending IP, shared or dedicated, in its headers. This is workspace tenant isolation and account safety, not a deliverability or inbox-placement lever. Without --approved nothing is ordered or charged. While native provisioning is unavailable, ordering fails closed and the preview says so.")
+        .description("Preview the dedicated native egress add-on (2,500 credits per 30-day period, $25 face value). With --approved, ORDER it: OXYGEN provisions one isolated email proxy plus one static egress IP for the workspace, captures the first period only after the proxy is ready, and debits the next 30 days later — not on the 1st. Every current inbox is assigned to that IP, every future inbox joins it automatically, and after the guarded handoff every native send, reply read and token refresh for the workspace's mailboxes uses that one IP, so IT can allowlist it in Microsoft Conditional Access or Google context-aware access. Recipients of Gmail API and Microsoft Graph sends still see Google/Microsoft relay IPs; a Microsoft mailbox on the SMTP transport may show the sending IP, shared or dedicated, in its headers. This is workspace tenant isolation and account safety, not a deliverability or inbox-placement lever. Without --approved nothing is ordered or charged. While native provisioning is unavailable, ordering fails closed and the preview says so.")
         // --approved (not --approve): the credit-spending approval flag,
         // which is also what derives spends_credits in the self-index.
         .option("--approved", "Execute the order (a real recurring credit charge). Omit for a no-side-effect preview.")
@@ -11586,7 +11586,7 @@ Examples:
         }));
     }))
         .addCommand(new Command("cancel")
-        .description("Cancel the dedicated sending-IP add-on. Approval-gated: without --approve it previews. Cancellation takes effect at the END of the 30-day period already paid for: the IP keeps sending until then, and only at period end does it retire, the workspace returns to the shared native worker, and credit billing stops. No refund, no early cutoff.")
+        .description("Cancel the dedicated sending-IP add-on. Approval-gated: without --approve it previews. Cancellation takes effect at the END of the 30-day period already paid for: the dedicated IP remains active until then, and only at period end does it retire, the workspace returns to the shared email proxy, and credit billing stops. No refund, no early cutoff.")
         .option("--approve", "Execute the cancellation. Omit for a no-side-effect preview.")
         .option("--json", "Print a JSON envelope.")
         .action(async (options) => {
@@ -11618,7 +11618,7 @@ Examples:
         }));
     }))
         .addCommand(new Command("register")
-        .description("STAFF RECOVERY: register legacy/manual logical policy inventory for this environment. This does not configure native send transport; dedicated native drains are created only by `egress dedicated request`. Secrets never pass here — --credential-ref names the Doppler family EGRESS_CRED_<REF>_USERNAME/_PASSWORD, set separately in Doppler.")
+        .description("STAFF RECOVERY: register legacy/manual logical policy inventory for this environment. This does not configure native send transport; dedicated email proxies are created only by `egress dedicated request`. Secrets never pass here — --credential-ref names the Doppler family EGRESS_CRED_<REF>_USERNAME/_PASSWORD, set separately in Doppler.")
         .requiredOption("--host <host>", "Proxy hostname or IP — bare, no scheme/port/credentials.")
         .requiredOption("--port <port>", "Proxy port (1-65535).")
         .requiredOption("--credential-ref <ref>", "Doppler credential-family name (A-Z, 0-9, _).")
@@ -13076,7 +13076,7 @@ Examples:
         .option("--selection-json <json>", "Full row selection object for server-side row selection.")
         .option("--only-missing", "Queue rows missing the capability's normalized output when no explicit selection is passed.")
         .option("--force", "Re-run rows with an existing target enrichment value.")
-        .option("--max-concurrency <n>", "Maximum concurrent row items for this enrichment run (1-250). Defaults to 20.")
+        .option("--max-concurrency <n>", "Maximum concurrent row items for this enrichment run (1-1000; a ceiling shared with worker and provider capacity). Defaults to 20.")
         .option("--json", "Print a JSON envelope.")
         .option("--approved", "Approve THIS run after inspecting `enrich-column preview` (free). Paid enrichment runs fail with approval_required (exit 7) without it.")
         .action(async (table, options) => {
@@ -15855,7 +15855,7 @@ 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("--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-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. Without it, email sends weekdays 09:00-17:00 UTC. 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.")
@@ -15979,7 +15979,7 @@ Examples:
         .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("--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 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.")

package/node_modules/@oxygen/shared/dist/table-limits.d.ts

@@ -4,20 +4,9 @@ export declare const MAX_FORMULA_ACTION_RUN_ROWS = 1000000;
 export declare const MAX_FORMULA_ACTION_RUN_ITEMS = 5000000;
 export declare const MAX_WORKSPACE_ROW_DELETE_ROWS = 50000;
 /**
- * Platform ceiling for a table action run's `max_concurrency` (T-27).
- *
- * The API used to accept 1..1000 and silently throttle anything the worker could
- * not serve (the August incident: a customer set 200-250 and watched it behave
- * nothing like the number they chose). This is the honest upper bound: 250, the
- * highest per-run in-flight ceiling ANY lane genuinely serves — the set-wise
- * link_batch lane (LINK_BATCH_ROWS = 250 in the worker scheduler). No run type is
- * validated below its real cap.
- *
- * It is deliberately NOT the external-tool provider feeder cap
- * (EXTERNAL_TOOL_RUN_FEEDER_CAP = 160, an independent constant in the worker):
- * an external_tool run is accepted up to this ceiling and the worker bounds it at
- * 160 in-flight, and the create envelope reports that lower effective ceiling
- * honestly (max_concurrency_platform_ceiling / max_concurrency_provider_ceiling)
- * rather than under-serving link runs to make one flat number "true".
+ * Maximum requested row concurrency for one table action run. Native BullMQ
+ * persists at most this many slot heads. Actual execution also shares worker
+ * slots, tenant admission and provider permits, so this is not an allocation
+ * or a rows-per-second guarantee. Defaults stay unchanged.
  */
-export declare const MAX_TABLE_ACTION_RUN_MAX_CONCURRENCY = 250;
+export declare const MAX_TABLE_ACTION_RUN_MAX_CONCURRENCY = 1000;

package/node_modules/@oxygen/shared/dist/table-limits.js

@@ -6,20 +6,9 @@ export const MAX_FORMULA_ACTION_RUN_ROWS = 1_000_000;
 export const MAX_FORMULA_ACTION_RUN_ITEMS = 5_000_000;
 export const MAX_WORKSPACE_ROW_DELETE_ROWS = 50_000;
 /**
- * Platform ceiling for a table action run's `max_concurrency` (T-27).
- *
- * The API used to accept 1..1000 and silently throttle anything the worker could
- * not serve (the August incident: a customer set 200-250 and watched it behave
- * nothing like the number they chose). This is the honest upper bound: 250, the
- * highest per-run in-flight ceiling ANY lane genuinely serves — the set-wise
- * link_batch lane (LINK_BATCH_ROWS = 250 in the worker scheduler). No run type is
- * validated below its real cap.
- *
- * It is deliberately NOT the external-tool provider feeder cap
- * (EXTERNAL_TOOL_RUN_FEEDER_CAP = 160, an independent constant in the worker):
- * an external_tool run is accepted up to this ceiling and the worker bounds it at
- * 160 in-flight, and the create envelope reports that lower effective ceiling
- * honestly (max_concurrency_platform_ceiling / max_concurrency_provider_ceiling)
- * rather than under-serving link runs to make one flat number "true".
+ * Maximum requested row concurrency for one table action run. Native BullMQ
+ * persists at most this many slot heads. Actual execution also shares worker
+ * slots, tenant admission and provider permits, so this is not an allocation
+ * or a rows-per-second guarantee. Defaults stay unchanged.
  */
-export const MAX_TABLE_ACTION_RUN_MAX_CONCURRENCY = 250;
+export const MAX_TABLE_ACTION_RUN_MAX_CONCURRENCY = 1000;

package/node_modules/@oxygen/shared/dist/version.generated.d.ts

@@ -1 +1 @@
-export declare const OXYGEN_BUILD_VERSION = "1.1011.468";
+export declare const OXYGEN_BUILD_VERSION = "1.1011.487";

package/node_modules/@oxygen/shared/dist/version.generated.js

@@ -1,2 +1,2 @@
 // GENERATED by scripts/ci/version-stamp.mjs from VERSION + git history. Do not edit; do not commit.
-export const OXYGEN_BUILD_VERSION = "1.1011.468";
+export const OXYGEN_BUILD_VERSION = "1.1011.487";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oxygen-agent/cli",
-  "version": "1.1011.468",
+  "version": "1.1011.487",
   "private": false,
   "license": "UNLICENSED",
   "type": "module",