@oxygen-agent/cli 1.844.8 → 1.846.0

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.844.8
+Version: 1.846.0

package/dist/index.js

@@ -12342,7 +12342,7 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         }
     }))
         .addCommand(new Command("update")
-        .description("Update a sequence. Journey definition/channels/email binding are draft-only so revised scope receives a fresh launch approval; sender pools can change while draft or paused; launch caps change through `sequences start` after first start. Name, throttles, tags, 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 still accepts a definition that changes nothing but its wait steps (the delays between steps, including the one before step 1); sender pools can change while draft or paused; launch caps change through `sequences start` after first start. Name, throttles, tags, and open/click tracking toggles remain editable as allowed by the server. Pass only the fields you want to change.")
         .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\").")
@@ -13522,7 +13522,7 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         await handleAsyncAction("mailboxes get", options, () => requestOxygen(`/api/cli/mailboxes/${encodeURIComponent(mailbox)}`));
     }))
         .addCommand(new Command("delete")
-        .description("Preview or approve removal of exact mailboxes from Oxygen at 0 credits. Deletion immediately removes them from sending but never deletes the underlying Google Workspace or Microsoft 365 accounts. It preserves conversation/message/delivery history and stops any separately listed 1,000-credit connected-mailbox commitment for future renewals; that line is currently built but not charged, and it is not the 3,000-credit OXYGEN Warm-up subscription. The current period is not refunded. Listed active/paused sequences keep their status but lose these senders and are not automatically paused. Managed mailboxes and live warmup/monitoring add-ons fail closed with their exact address-scoped teardown steps.")
+        .description("Preview or approve removal of exact mailboxes from Oxygen at 0 credits. Deletion immediately removes them from sending but never deletes the underlying Google Workspace or Microsoft 365 accounts. It preserves conversation/message/delivery history and stops any separately listed 1,000-credit connected-mailbox commitment for future renewals; that line is currently built but not charged, and it is not the 1,000-credit OXYGEN Warm-up subscription. The current period is not refunded. Listed active/paused sequences keep their status but lose these senders and are not automatically paused. Managed mailboxes and live warmup/monitoring add-ons fail closed with their exact address-scoped teardown steps.")
         .requiredOption("--mailboxes <list>", "Comma-separated mailbox ids or addresses (maximum 500).")
         .option("--approved", "Execute the fresh preview. Requires --plan-hash and --confirmation.")
         .option("--plan-hash <hash>", "Fresh preview plan_hash.")
@@ -13930,10 +13930,10 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         });
     }))
         .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 is managed and credit-billed at 3,000 credits per warming inbox per month ($3). 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.")
+        .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 is managed and credit-billed at 1,000 credits per warming inbox per month ($1). 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.")
         .addHelpText("after", "\nDocs: https://oxygen-agent.com/docs/providers/mailboxes\n")
         .addCommand(new Command("enable")
-        .description("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 current public price is 3,000 credits per warming mailbox-month; 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.")
+        .description("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 current public price is 1,000 credits per warming mailbox-month; 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.")
         .addHelpText("after", "\nDocs: https://oxygen-agent.com/docs/providers/mailboxes\n")
         .option("--mailboxes <list>", "Comma-separated mailbox ids or addresses to warm. Omit to warm the whole pool.")
         .option("--approved", "Execute the PRICED enrollment. Without it the response is a priced preview and nothing is enrolled or billed.")
@@ -14107,7 +14107,7 @@ fixed scan; watermark_cursor starts a later bounded replay. Consumers must retai
         });
     }))
         .addCommand(new Command("disable")
-        .description("Disable warmup and unenroll each mailbox from the rail that actually enrolled it. On a managed rail — OXYGEN Warm-up today, TrulyInbox for older enrollments — this also cancels that mailbox's warmup subscription, so billing stops with the provider removal. This is how you wind an inbox off the retired TrulyInbox rail. NOT the way to fix a rotated app password — use `mailboxes warmup reconnect` for that, which costs 0 credits instead of a new 3,000-credit month. Targets the whole pool unless --mailboxes is given.")
+        .description("Disable warmup and unenroll each mailbox from the rail that actually enrolled it. On a managed rail — OXYGEN Warm-up today, TrulyInbox for older enrollments — this also cancels that mailbox's warmup subscription, so billing stops with the provider removal. This is how you wind an inbox off the retired TrulyInbox rail. NOT the way to fix a rotated app password — use `mailboxes warmup reconnect` for that, which costs 0 credits instead of a new 1,000-credit month. 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) => {

package/node_modules/@oxygen/shared/dist/pricing-snapshot.generated.d.ts

@@ -20,7 +20,7 @@ export declare const WHATSAPP_ACCOUNT_CREDITS_PER_MONTH = 10000;
 export declare const EGRESS_IP_CREDITS_PER_MONTH = 25000;
 export declare const SENDING_MAILBOX_CREDITS_PER_MONTH = 1000;
 export declare const MANAGED_INBOX_CREDITS_PER_MONTH = 3000;
-export declare const MAILBOX_WARMUP_CREDITS_PER_MONTH = 3000;
+export declare const MAILBOX_WARMUP_CREDITS_PER_MONTH = 1000;
 export declare const DELIVERABILITY_SEAT_CREDITS_PER_MONTH = 1000;
 /** Included inbox-placement tests per subscribed inbox per cycle. */
 export declare const DELIVERABILITY_INCLUDED_TESTS_PER_INBOX = 2;

package/node_modules/@oxygen/shared/dist/pricing-snapshot.generated.js

@@ -37,7 +37,7 @@ export const WHATSAPP_ACCOUNT_CREDITS_PER_MONTH = 10_000;
 export const EGRESS_IP_CREDITS_PER_MONTH = 25_000;
 export const SENDING_MAILBOX_CREDITS_PER_MONTH = 1_000;
 export const MANAGED_INBOX_CREDITS_PER_MONTH = 3_000;
-export const MAILBOX_WARMUP_CREDITS_PER_MONTH = 3_000;
+export const MAILBOX_WARMUP_CREDITS_PER_MONTH = 1_000;
 export const DELIVERABILITY_SEAT_CREDITS_PER_MONTH = 1_000;
 /** Included inbox-placement tests per subscribed inbox per cycle. */
 export const DELIVERABILITY_INCLUDED_TESTS_PER_INBOX = 2;

package/node_modules/@oxygen/shared/dist/sequences.d.ts

@@ -815,6 +815,22 @@ export declare function sequenceWaitStepJitterMs(step: SequenceWaitStep, enrollm
  * spreads a same-instant batch across the jitter window.
  */
 export declare function sequenceWaitStepDelayWithJitterMs(step: SequenceWaitStep, enrollmentId: string): number;
+/**
+ * Whether `after` changes nothing about `before` except its timing — the delays
+ * between steps, including the lead-in delay in front of the very first one.
+ *
+ * This is the one journey edit a LIVE sequence accepts. The journey lock exists
+ * so a revised journey gets a fresh launch preview and approval, and a wait
+ * provably cannot move that preview: estimateSequenceActions (the start route's
+ * estimator) skips every step with no channel, so waits contribute nothing to the
+ * planned actions, the channel mix, or the credit estimate the approval was
+ * granted against. What a delay does change is when the next step fires — exactly
+ * the knob a founder reaches for after watching day one of a live campaign.
+ *
+ * Inserting or removing a wait counts as timing too: a wait dispatches nothing, so
+ * adding one only postpones a send and removing one only brings it forward.
+ */
+export declare function sequenceDefinitionsDifferOnlyInTiming(before: SequenceDefinition, after: SequenceDefinition): boolean;
 /**
  * Render a sequence-copy template against a row's values. Delegates to the shared
  * deterministic engine (sequence-template.ts): `{{column}}` substitution plus

package/node_modules/@oxygen/shared/dist/sequences.js

@@ -1835,6 +1835,86 @@ export function sequenceWaitStepJitterMs(step, enrollmentId) {
 export function sequenceWaitStepDelayWithJitterMs(step, enrollmentId) {
     return sequenceWaitStepDelayMs(step) + sequenceWaitStepJitterMs(step, enrollmentId);
 }
+/**
+ * Branch fields that name another step. A signal branch spells its arms `then`/
+ * `else`; a connection branch spells them `then_id`/`else_id`. Both are erased
+ * from the skeleton and replaced by one normalized pair, so an arm that is absent
+ * on one side and explicitly null on the other still compares equal.
+ */
+const BRANCH_TARGET_KEYS = ["then", "else", "then_id", "else_id"];
+/** Key-sorted JSON, so two structurally equal definitions compare equal whatever order their keys were built in. */
+function stableJson(value) {
+    if (Array.isArray(value))
+        return `[${value.map(stableJson).join(",")}]`;
+    if (value && typeof value === "object") {
+        const entries = Object.entries(value)
+            .filter(([, entry]) => entry !== undefined)
+            .sort(([a], [b]) => (a < b ? -1 : a > b ? 1 : 0));
+        return `{${entries.map(([key, entry]) => `${JSON.stringify(key)}:${stableJson(entry)}`).join(",")}}`;
+    }
+    return JSON.stringify(value) ?? "null";
+}
+/**
+ * The definition with every `wait` step erased: the actions, in order, with each
+ * branch arm repointed to the step its delay leads INTO. Two definitions share a
+ * skeleton exactly when they perform the same journey and differ only in when.
+ *
+ * Waits are folded rather than simply filtered out because a delay is modelled as
+ * a step, so an arm whose delay was edited legitimately repoints from one wait id
+ * to another (setBranchArmDelay in the web builder does exactly that) — a naive
+ * filter would read that as a rerouted branch.
+ */
+function sequenceTimingSkeleton(definition) {
+    const steps = Array.isArray(definition?.steps) ? definition.steps : [];
+    const indexById = new Map(steps.map((step, index) => [step.id, index]));
+    // The first non-wait step at or after `id`. A dangling target, an absent one,
+    // and a trailing run of waits all end the path — all resolve to null.
+    const throughWaits = (id) => {
+        if (typeof id !== "string")
+            return null;
+        const from = indexById.get(id);
+        if (from === undefined)
+            return null;
+        for (let k = from; k < steps.length; k++) {
+            const step = steps[k];
+            if (step.kind !== "wait")
+                return step.id;
+        }
+        return null;
+    };
+    const actions = steps
+        .filter((step) => step.kind !== "wait")
+        .map((step) => {
+        const fields = { ...step };
+        const branch = step;
+        for (const key of BRANCH_TARGET_KEYS)
+            delete fields[key];
+        return {
+            ...fields,
+            arm_then: throughWaits(branch.then ?? branch.then_id),
+            arm_else: throughWaits(branch.else ?? branch.else_id),
+        };
+    });
+    return stableJson(actions);
+}
+/**
+ * Whether `after` changes nothing about `before` except its timing — the delays
+ * between steps, including the lead-in delay in front of the very first one.
+ *
+ * This is the one journey edit a LIVE sequence accepts. The journey lock exists
+ * so a revised journey gets a fresh launch preview and approval, and a wait
+ * provably cannot move that preview: estimateSequenceActions (the start route's
+ * estimator) skips every step with no channel, so waits contribute nothing to the
+ * planned actions, the channel mix, or the credit estimate the approval was
+ * granted against. What a delay does change is when the next step fires — exactly
+ * the knob a founder reaches for after watching day one of a live campaign.
+ *
+ * Inserting or removing a wait counts as timing too: a wait dispatches nothing, so
+ * adding one only postpones a send and removing one only brings it forward.
+ */
+export function sequenceDefinitionsDifferOnlyInTiming(before, after) {
+    return sequenceTimingSkeleton(before) === sequenceTimingSkeleton(after);
+}
 /**
  * Render a sequence-copy template against a row's values. Delegates to the shared
  * deterministic engine (sequence-template.ts): `{{column}}` substitution plus

package/node_modules/@oxygen/shared/dist/spend-safety.d.ts

@@ -68,6 +68,29 @@ export declare function resolveByokProviderDailyCapEnforcementMode(configured?:
  * customer who had already paid for the credits, and the refusal was invisible
  * on every surface. 20x still stops an unattended loop within hours.
  */
+/**
+ * Credit categories the IMPLICIT org-daily guard does not count.
+ *
+ * The guard is a runaway-loop backstop. A loop cannot produce these: every one
+ * is a deliberate, approval-gated subscription commitment tied to a specific
+ * mailbox, so the count is bounded by how many mailboxes a human chose to
+ * enroll, not by how fast something iterates. Their shape says the same thing —
+ * over one week `managed_warmup` was 182 transactions carrying 273k credits,
+ * while `managed_enrichment` was 50,967 transactions. High value, low
+ * cardinality is a purchase; low value, high cardinality is a loop.
+ *
+ * Counting commitments made the guard refuse exactly the deliberate provisioning
+ * its own contract says it must not refuse. That failure has now happened twice:
+ * once at the 1x multiple (fixed by raising to 20x on 2026-08-17) and again on
+ * 2026-08-25, when an org holding 400k paid credits was blocked mid-enrollment
+ * at 249,735 of a 250,000 daily guard. Raising the multiple a third time would
+ * only move the wall; excluding commitments removes it for the case that was
+ * never a loop.
+ *
+ * This applies ONLY to the implicit default. An org that sets its own org-daily
+ * policy has chosen a real spend ceiling, and that ceiling counts everything.
+ */
+export declare const IMPLICIT_ORG_DAILY_GUARD_EXCLUDED_CATEGORIES: readonly string[];
 export declare const DEFAULT_ORG_DAILY_SPEND_WARN_MULTIPLE = 5;
 export declare const DEFAULT_ORG_DAILY_SPEND_BLOCK_MULTIPLE = 20;
 /** Resolved credit thresholds of the implicit org-daily guard for one plan. */

package/node_modules/@oxygen/shared/dist/spend-safety.js

@@ -85,6 +85,32 @@ export function resolveByokProviderDailyCapEnforcementMode(configured = process.
  * customer who had already paid for the credits, and the refusal was invisible
  * on every surface. 20x still stops an unattended loop within hours.
  */
+/**
+ * Credit categories the IMPLICIT org-daily guard does not count.
+ *
+ * The guard is a runaway-loop backstop. A loop cannot produce these: every one
+ * is a deliberate, approval-gated subscription commitment tied to a specific
+ * mailbox, so the count is bounded by how many mailboxes a human chose to
+ * enroll, not by how fast something iterates. Their shape says the same thing —
+ * over one week `managed_warmup` was 182 transactions carrying 273k credits,
+ * while `managed_enrichment` was 50,967 transactions. High value, low
+ * cardinality is a purchase; low value, high cardinality is a loop.
+ *
+ * Counting commitments made the guard refuse exactly the deliberate provisioning
+ * its own contract says it must not refuse. That failure has now happened twice:
+ * once at the 1x multiple (fixed by raising to 20x on 2026-08-17) and again on
+ * 2026-08-25, when an org holding 400k paid credits was blocked mid-enrollment
+ * at 249,735 of a 250,000 daily guard. Raising the multiple a third time would
+ * only move the wall; excluding commitments removes it for the case that was
+ * never a loop.
+ *
+ * This applies ONLY to the implicit default. An org that sets its own org-daily
+ * policy has chosen a real spend ceiling, and that ceiling counts everything.
+ */
+export const IMPLICIT_ORG_DAILY_GUARD_EXCLUDED_CATEGORIES = [
+    "managed_warmup",
+    "managed_inbox",
+];
 export const DEFAULT_ORG_DAILY_SPEND_WARN_MULTIPLE = 5;
 export const DEFAULT_ORG_DAILY_SPEND_BLOCK_MULTIPLE = 20;
 /**

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

@@ -1,4 +1,4 @@
-export declare const OXYGEN_VERSION = "1.844.8";
+export declare const OXYGEN_VERSION = "1.846.0";
 export declare const OXYGEN_MINIMUM_CLI_VERSION = "1.181.0";
 export declare const MANAGED_INBOX_MINIMUM_CLI_VERSION = "1.326.2";
 export declare const SUPPORT_AGENT_REPLY_MINIMUM_CLI_VERSION = "1.747.0";

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

@@ -1,4 +1,4 @@
-export const OXYGEN_VERSION = "1.844.8";
+export const OXYGEN_VERSION = "1.846.0";
 // The GLOBAL CLI compatibility floor: the oldest CLI allowed to call any
 // operational route. Raising it hard-rejects every older CLI from the entire
 // product, so it obeys one law, enforced by scripts/ci/cli-min-version-gate.mjs:

package/package.json

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