@myapihq/cli 2.23.0 → 2.23.2

package/dist/commands/account.d.ts

@@ -3,7 +3,7 @@ import type { Flags } from '../helpers.js';
 import type { Exposes } from '../exposes.js';
 export declare const EXPOSES: Exposes;
 export declare const SCHEMA: FlagSchema;
-export declare const HELP = "Usage: myapi account <subcommand>\n\nSubcommands:\n  api-keys        Manage API keys \u00B7 list / create / revoke\n  config          Manage CLI defaults (org, funnel, domain) \u00B7 supports set-org / set-funnel / set-domain\n  import-key      Import an existing API key non-interactively\n  install-skills  DEPRECATED \u2014 use `myapi install-skills` instead\n  keys            Alias for api-keys\n  link [email]    Upgrade anonymous account to registered (or add a second session)\n                  Use myapi account setup to create a completely new account\n  login           Sign in via your browser \u2014 Google or email code (preview: --mock)\n  mailing-address Get or set the account's mailing address (CAN-SPAM)\n  registrant      Manage stored WHOIS contact info for domain registration \u00B7 set / get / clear\n  resume-sending  Turn email sending back on after an automatic pause\n  sending         Whether this account can send email, and how close it is to the limits\n  setup           Configure your account\n  switch [index]  Switch active account by index or email\n  whoami          Show current account \u00B7 supports --json";
+export declare const HELP = "Usage: myapi account <subcommand>\n\nSubcommands:\n  api-keys        Manage API keys \u00B7 list / create / revoke\n  config          Manage CLI defaults (org, funnel, domain) \u00B7 supports set-org / set-funnel / set-domain\n  import-key      Import an existing API key non-interactively\n  install-skills  DEPRECATED \u2014 use `myapi install-skills` instead\n  keys            Alias for api-keys\n  link [email]    Upgrade anonymous account to registered (or add a second session)\n                  Use myapi account setup to create a completely new account\n  login           Sign in via your browser \u2014 Google or email code (preview: --mock)\n  mailing-address Get or set the account's mailing address (CAN-SPAM)\n  registrant      Manage stored WHOIS contact info for domain registration \u00B7 set / get / clear\n  resume-sending  Turn email sending back on after an automatic pause (account or org)\n  sending         Whether this account can send email, and how close it is to the limits\n  setup           Configure your account\n  switch [index]  Switch active account by index or email\n  whoami          Show current account \u00B7 supports --json";
 export declare const INSTALL_SKILLS_HELP = "Usage: myapi install-skills\n\nInstalls the MyAPI skills pack for AI coding agents (Claude, Codex, Gemini, \u2026).\n\nThis command writes skill definition files to:\n  ~/.agents/skills/myapi/\n\nAnd creates symlinks in the appropriate agent config directories:\n  ~/.claude/  (Claude)\n  ~/.gemini/  (Gemini)\n  ~/.cursor/  (Cursor, if detected)\n\nThese files teach agents how to use the MyAPI CLI and API directly.\nRun this command again to update existing skills to the latest version.\n\nNote: `myapi account install-skills` is deprecated and will be removed in the next minor.\nUse `myapi install-skills` going forward.";
 export declare const SUBCOMMAND_USAGE: Record<string, string>;
 export declare function link(flags?: Flags, emailArg?: string): Promise<void>;

package/dist/commands/account.js

@@ -56,7 +56,7 @@ Subcommands:
   login           Sign in via your browser — Google or email code (preview: --mock)
   mailing-address Get or set the account's mailing address (CAN-SPAM)
   registrant      Manage stored WHOIS contact info for domain registration · set / get / clear
-  resume-sending  Turn email sending back on after an automatic pause
+  resume-sending  Turn email sending back on after an automatic pause (account or org)
   sending         Whether this account can send email, and how close it is to the limits
   setup           Configure your account
   switch [index]  Switch active account by index or email
@@ -132,7 +132,9 @@ export const SUBCOMMAND_USAGE = {
   Under 100 sends in 24h the ratios are not judged, and the reply says so.`,
     'resume-sending': `myapi account resume-sending [--json]
 
-  Turn sending back on after an automatic pause.
+  Turn sending back on after an automatic pause — whether the pause is on the
+  account or on one of its orgs. It sits under account because one call lifts
+  both; an org-scoped twin would be a second name for the same endpoint.
 
   Refused with STILL_OVER_THRESHOLD while the last 24 hours are still over
   the limit — the numbers come back with the refusal, so you can see how far

package/dist/commands/email/campaign-source-flags.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/commands/email/campaign-source-flags.test.js

@@ -0,0 +1,52 @@
+import { describe, it, expect } from 'vitest';
+import { readFileSync } from 'node:fs';
+import { fileURLToPath } from 'node:url';
+import { SOURCE_FLAGS } from './campaign.js';
+import { SCHEMA } from './index.js';
+// `campaign update` decides whether the recipient source was touched by looking
+// at a list of flags. sourceFromFlags reads its own. When those two lists
+// disagree, the losing flag is parsed, printed in --help, documented in the
+// skill — and silently discarded: `campaign update --crm-audience <id>`
+// answered "Nothing to change" and made no call at all.
+//
+// They now share SOURCE_FLAGS. These tests keep that true by deriving the
+// answer from the code rather than restating it: a hand-copied list in a test
+// drifts exactly the way the thing it is testing drifted.
+const src = readFileSync(fileURLToPath(new URL('./campaign.ts', import.meta.url)), 'utf-8');
+/** Flag names read inside sourceFromFlags — the flags that actually build a source. */
+function flagsReadWhenBuildingASource() {
+    const start = src.indexOf('function sourceFromFlags');
+    expect(start, 'sourceFromFlags not found — this test is reading the wrong file').toBeGreaterThan(-1);
+    const end = src.indexOf('\nfunction ', start + 10);
+    const body = src.slice(start, end === -1 ? undefined : end);
+    const names = new Set();
+    for (const m of body.matchAll(/flags\['([^']+)'\]/g))
+        names.add(m[1]);
+    for (const m of body.matchAll(/flags\.([a-zA-Z][\w]*)/g))
+        names.add(m[1]);
+    return [...names];
+}
+describe('campaign source flags', () => {
+    it('every flag sourceFromFlags reads is one update() watches', () => {
+        const read = flagsReadWhenBuildingASource();
+        // The scan must find something; an empty list would make this pass while
+        // measuring nothing.
+        expect(read.length).toBeGreaterThanOrEqual(7);
+        const watched = new Set(SOURCE_FLAGS);
+        const unwatched = read.filter(f => !watched.has(f));
+        expect(unwatched, 'these build a source but update() would ignore them').toEqual([]);
+    });
+    it('every watched flag is declared on the email command', () => {
+        // A flag update() watches but the parser does not know is always
+        // undefined, so it silently never triggers.
+        const undeclared = SOURCE_FLAGS.filter(f => !(f in SCHEMA));
+        expect(undeclared, 'watched but not in the email SCHEMA').toEqual([]);
+    });
+    it('every watched flag actually builds part of a source', () => {
+        // The other direction: an entry nobody reads makes `update` call the API
+        // with a source that did not change.
+        const read = new Set(flagsReadWhenBuildingASource());
+        const unread = SOURCE_FLAGS.filter(f => !read.has(f));
+        expect(unread, 'watched by update() but never read when building a source').toEqual([]);
+    });
+});

package/dist/commands/email/campaign.d.ts

@@ -2,4 +2,5 @@ import { type Flags } from '../../helpers.js';
 import type { Exposes } from '../../exposes.js';
 export declare const EXPOSES: Exposes;
 export declare const HELP = "Usage: myapi email campaign <subcommand>\n\n  create      Create a draft (--template, --from, and a source)\n  list        Campaigns in this org\n  get <id>    One campaign\n  update <id> Edit a DRAFT's name or source\n  resolve <id>  Freeze who it reaches; reports the count and cost, sends nothing\n  start <id>  Begin sending a resolved campaign\n  pause <id>  Stop after the message in flight\n  resume <id> Continue a paused campaign\n  cancel <id> End it for good; queued recipients are dropped\n  recipients <id>  Who it resolved to, and what happened to each\n  stats <id>  Counts by state, sent today, and the daily limit\n\nA campaign drains at its per-day limit rather than sending at once, so it is\ncommonly still active tomorrow \u2014 that is the design, not a stall.\n\nRecipients come from a SOURCE, not a list you upload:\n  --crm-stage / --crm-origin / --crm-max-days   filter CRM contacts\n  --crm-audience <id>                           only people promoted from it\n  --addresses a@x.com,b@y.com                   an explicit short list";
+export declare const SOURCE_FLAGS: readonly ["addresses", "crm-stage", "crm-origin", "crm-company", "crm-audience", "crm-max-days", "crm-min-days", "all-contacts"];
 export declare function run(sub: string | undefined, args: string[], flags: Flags): Promise<void>;

package/dist/commands/email/campaign.js

@@ -37,6 +37,21 @@ Recipients come from a SOURCE, not a list you upload:
   --crm-stage / --crm-origin / --crm-max-days   filter CRM contacts
   --crm-audience <id>                           only people promoted from it
   --addresses a@x.com,b@y.com                   an explicit short list`;
+// Every flag that names part of a recipient source. Declared once because two
+// places need it and they must agree: sourceFromFlags READS them, and `update`
+// decides from them whether the source was touched at all. When those two
+// drifted, `campaign update --crm-audience <id>` answered "Nothing to change"
+// and made no call — the flag was parsed, documented, and then ignored.
+export const SOURCE_FLAGS = [
+    'addresses',
+    'crm-stage',
+    'crm-origin',
+    'crm-company',
+    'crm-audience',
+    'crm-max-days',
+    'crm-min-days',
+    'all-contacts',
+];
 // Building the source from flags is the one place the CLI has an opinion: a
 // campaign names where its people come from, and mixing two sources in one
 // command is a request nobody can mean.
@@ -136,9 +151,7 @@ async function update(id, flags) {
     const patch = {};
     if (typeof flags.name === 'string' && flags.name)
         patch.name = flags.name;
-    const wantsSource = flags.addresses || flags['crm-stage'] || flags['crm-origin']
-        || flags['crm-company'] || flags['crm-audience'] || flags['crm-max-days']
-        || flags['crm-min-days'] || flags['all-contacts'];
+    const wantsSource = SOURCE_FLAGS.some(f => flags[f] !== undefined);
     if (wantsSource)
         Object.assign(patch, sourceFromFlags(flags));
     if (Object.keys(patch).length === 0)

package/dist/commands/email/mailbox.js

@@ -30,8 +30,20 @@ async function create(addressArg, flags) {
         error('Missing required arguments.\nUsage: myapi email mailbox create <user@domain> [--display-name <name>]\n   or: myapi email mailbox create --username <u> --domain <d> [--display-name <name>]\n(Or set default: myapi config set-domain <domain>)');
     }
     const res = await sdkEmail.createMailbox(config.api_key, domain, username, flags['display-name']);
-    // Backend response sometimes omits address; we know it from the inputs.
-    success(`Mailbox created: ${res.address || `${username}@${domain}`}`);
+    // The address comes back as `mailbox`. It is not "sometimes omitted" — the
+    // previous comment here encoded a wrong theory, which turned a permanent
+    // contract mismatch into an imagined intermittent one and kept it patched
+    // instead of reported. Kept the fallback anyway: the address is derivable
+    // from the inputs, and a create that succeeded should still print what it
+    // made if the field ever moves again.
+    success(`Mailbox created: ${res.mailbox || `${username}@${domain}`}`);
+    // A warning on a 2xx means something is configured but incomplete — here, a
+    // missing CAN-SPAM mailing address, which refuses every send LATER rather
+    // than now. Printing it while the customer is set up in front of the
+    // terminal is the whole point of the backend adding it; dropping it silently
+    // meant the fix reached nobody using the CLI.
+    if (res.warning)
+        info(`› ${res.warning}`);
 }
 async function list(flags) {
     const config = requireConfig();

package/dist/commands/fn.js

@@ -316,7 +316,14 @@ export async function runs(id, flags) {
         error: r.error_message || '',
     })), {
         flags,
-        empty: 'No runs recorded yet for this function.',
+        // An empty list here means "we do not measure this", not "it did not
+        // happen": function_runs has one writer, the workflow engine. A direct call
+        // to the invocation URL is served at the edge and never reaches the backend
+        // to be recorded. ImmoPilot read the old sentence as proof the API was
+        // never called and ruled out the branch of a login investigation that was
+        // the actual problem — the function had run hundreds of times that day.
+        empty: 'No workflow-triggered runs. Direct calls to the invocation URL are served at the edge '
+            + 'and are not recorded here, so an empty list does NOT mean the function was not called.',
     });
 }
 // ── Dispatcher ───────────────────────────────────────────────────────────────

package/dist/errors.js

@@ -100,6 +100,31 @@ export function friendlyError(err) {
     if (err.code === 'REGISTRAR_RATE_LIMITED') {
         return 'Domain registration is busy right now — please wait a few minutes before trying again (avoid automatic retries).';
     }
+    // A paused account is told how to un-pause itself — and the backend says
+    // `POST /hq/account/resume-sending`, which is right for an API caller and
+    // wrong for this one. Rewrite the route, keep everything else.
+    //
+    // Rewriting rather than replacing the sentence: the figures in it are the
+    // ones that caused the pause and are per-account. A fixed string here would
+    // drop them, and they are the reason the message is worth reading.
+    //
+    // The backend added this instruction on 2026-08-22 (myapi-hq #159) after a
+    // customer waited six days on "contact support to review" while the resume
+    // endpoint already existed.
+    if (err.code === 'ACCOUNT_PAUSED' || err.code === 'ORG_PAUSED') {
+        const raw = (err.detail || ERROR_MESSAGES[err.code] || err.code).trim();
+        let out = raw.replace(/POST\s+\/hq\/account\/resume-sending/g, 'myapi account resume-sending');
+        // An older backend sends no instruction at all; add one rather than leaving
+        // the reader where that customer was.
+        if (!out.includes('resume-sending')) {
+            out += ' — fix the addresses that bounce, then: myapi account resume-sending';
+        }
+        // The figures in the message are frozen at the moment of the pause and do
+        // not move; `account sending` is the live picture, and reading the frozen
+        // ones as current is the whole confusion.
+        out += '\n  Current numbers: myapi account sending';
+        return withOrgContext(out, err);
+    }
     const base = ERROR_MESSAGES[err.code] || err.code;
     // Generic fallback: append the backend's `message` when it adds info beyond
     // the friendly mapping. Future per-service detail fields can be added here.

package/dist/errors.test.js

@@ -26,3 +26,45 @@ describe('friendlyError', () => {
         expect(friendlyError(new MyApiError('SOME_NEW_CODE', 400))).toBe('SOME_NEW_CODE');
     });
 });
+describe('paused sending points at the CLI, not an HTTP route', () => {
+    // Verbatim from the backend on 2026-08-22 (myapi-hq #159). The instruction is
+    // correct for an API caller and wrong for this one.
+    const ACCOUNT_TEXT = 'sending paused: bounce rate 7.83% > 4% (9 bounces / 115 sends) — the figures are from '
+        + 'when the pause was set and do not change. Fix the addresses that bounce, then POST '
+        + '/hq/account/resume-sending';
+    const ORG_TEXT = 'sending paused for this org: bounce rate 6.10% > 4% — fix the addresses that bounce, '
+        + 'then POST /hq/account/resume-sending';
+    it('ACCOUNT_PAUSED names the command instead of the endpoint', () => {
+        const msg = friendlyError(new MyApiError('ACCOUNT_PAUSED', 403, ACCOUNT_TEXT));
+        expect(msg).toContain('myapi account resume-sending');
+        // The whole point: a CLI user must not be told to make an HTTP POST for
+        // something this CLI already does.
+        expect(msg).not.toContain('POST /hq/account/resume-sending');
+    });
+    it('keeps the figures and the fact that they are frozen', () => {
+        const msg = friendlyError(new MyApiError('ACCOUNT_PAUSED', 403, ACCOUNT_TEXT));
+        // These are why the message is worth reading, and a fixed replacement
+        // string would have dropped them.
+        expect(msg).toContain('7.83%');
+        expect(msg).toContain('9 bounces / 115 sends');
+        expect(msg).toMatch(/do not change/);
+    });
+    it('points at the live numbers, which the frozen ones are not', () => {
+        const msg = friendlyError(new MyApiError('ACCOUNT_PAUSED', 403, ACCOUNT_TEXT));
+        expect(msg).toContain('myapi account sending');
+    });
+    it('ORG_PAUSED gets the same treatment and keeps its scope', () => {
+        const msg = friendlyError(new MyApiError('ORG_PAUSED', 403, ORG_TEXT));
+        expect(msg).toContain('myapi account resume-sending');
+        expect(msg).not.toContain('POST /hq/account/resume-sending');
+        // The reader must still be able to tell WHICH pause they hit — one command
+        // lifts both, but the scope changes what they go and fix.
+        expect(msg).toContain('for this org');
+    });
+    it('adds the instruction when an older backend sends none', () => {
+        // Before #159 the message ended at "contact support to review", which is
+        // where a customer sat for six days.
+        const msg = friendlyError(new MyApiError('ACCOUNT_PAUSED', 403, 'sending paused: bounce rate too high — contact support to review'));
+        expect(msg).toContain('myapi account resume-sending');
+    });
+});

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@myapihq/cli",
   "license": "Apache-2.0",
-  "version": "2.23.0",
+  "version": "2.23.2",
   "description": "MyAPI command-line interface",
   "repository": {
     "type": "git",
@@ -46,7 +46,7 @@
     "lint:skills:strict": "node scripts/copy-skills.js && node scripts/lint-skills.js --strict"
   },
   "dependencies": {
-    "@myapihq/sdk": "^2.23.0"
+    "@myapihq/sdk": "^2.23.2"
   },
   "devDependencies": {
     "@types/node": "^25.6.0",