@myapihq/cli 2.23.2 → 2.24.0

package/dist/commands/container-patch-coverage.test.d.ts

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

package/dist/commands/container-patch-coverage.test.js

@@ -0,0 +1,111 @@
+// Every field PATCH accepts must be one a CLI verb can actually send.
+//
+// A container setting that can be given at creation and not changed afterwards
+// is not a missing convenience — it is a delete-and-recreate, and recreating a
+// container loses its URL, its scoped key and its custom domain binding.
+//
+// That has now happened twice. `env` was create-only, and a customer recreated
+// containers three times in a week to edit variables. Then `health_check` was
+// create-only, and a customer paid for a production swap to adopt a probe.
+// Both times the backend widened PATCH and the CLI did not follow, so the fix
+// reached nobody: the route accepted a field that no client ever sent, and
+// nothing on either side was red.
+//
+// So this is driven from the schema snapshot rather than a hand-kept list, and
+// it asserts on what arrives at the SDK boundary rather than on the shape of
+// our source — testing the parser proves the flag parses, not that it is sent.
+// When the backend adds a field to this PATCH body, this fails until a verb
+// can send it.
+import { describe, it, expect, vi, beforeEach, afterEach } from 'vitest';
+import { readFileSync } from 'node:fs';
+const ORG = '11111111-1111-4111-8111-111111111111';
+const sdk = vi.hoisted(() => ({
+    container: {
+        updateContainer: vi.fn(),
+        updateContainerEnv: vi.fn(),
+    },
+    withFundsRetry: vi.fn(async (f) => f()),
+    MyApiError: class MyApiError extends Error {
+        code = '';
+        status = 0;
+    },
+}));
+vi.mock('@myapihq/sdk', () => sdk);
+vi.mock('../config.js', () => ({
+    requireConfig: () => ({ api_key: 'hq_live_test', default_org: ORG }),
+    loadConfig: () => ({ api_key: 'hq_live_test', default_org: ORG }),
+    CONFIG_DIR: '/tmp/nowhere',
+}));
+const SNAPSHOT = JSON.parse(readFileSync(new URL('../../schema-snapshot.json', import.meta.url), 'utf8'));
+const PATCH_ROUTE = '/container/orgs/{org_id}/containers/{id}';
+function patchBodyFields() {
+    const op = SNAPSHOT.paths?.[PATCH_ROUTE]?.patch;
+    const props = op?.requestBody?.content?.['application/json']?.schema?.properties;
+    return props ? Object.keys(props) : [];
+}
+const APPLIED = { set: [], removed: [], applied: true, env: {}, revision: 'rev-2' };
+beforeEach(async () => {
+    vi.clearAllMocks();
+    sdk.container.updateContainer.mockResolvedValue(APPLIED);
+    sdk.container.updateContainerEnv.mockResolvedValue(APPLIED);
+    const output = await import('../output.js');
+    vi.spyOn(output, 'error').mockImplementation(((m) => {
+        throw new Error('__EXIT__');
+    }));
+    vi.spyOn(output, 'info').mockImplementation(() => { });
+    vi.spyOn(output, 'success').mockImplementation(() => { });
+    vi.spyOn(output, 'printJson').mockImplementation(() => { });
+});
+afterEach(() => vi.restoreAllMocks());
+async function run(fn) {
+    try {
+        await fn();
+    }
+    catch (e) {
+        if (e?.message !== '__EXIT__')
+            throw e;
+    }
+}
+// Drives each verb that patches a container and collects the body keys that
+// actually reach the SDK.
+async function fieldsTheCliCanSend() {
+    const container = await import('./container.js');
+    const sent = new Set();
+    await run(() => container.run('env', ['c1'], { env: 'A=1', org: ORG }));
+    await run(() => container.run('health-check', ['c1', '/livez'], { org: ORG }));
+    for (const call of sdk.container.updateContainer.mock.calls) {
+        Object.keys(call[3] ?? {}).forEach(k => sent.add(k));
+    }
+    // The env shorthand takes the map itself rather than a patch object.
+    if (sdk.container.updateContainerEnv.mock.calls.length)
+        sent.add('env');
+    return sent;
+}
+describe('container PATCH coverage', () => {
+    it('the snapshot still describes this route (or the test measures nothing)', () => {
+        // Without this, a renamed route upstream would leave an empty field list
+        // and a permanently, silently green test.
+        expect(patchBodyFields().length).toBeGreaterThan(0);
+    });
+    it('every field PATCH accepts is one a CLI verb actually sends', async () => {
+        const sent = await fieldsTheCliCanSend();
+        const unreachable = patchBodyFields().filter(f => !sent.has(f));
+        expect(unreachable, `PATCH ${PATCH_ROUTE} accepts ${unreachable.join(', ')}, but no CLI ` +
+            'verb sends it. Until one does, changing that setting means deleting the ' +
+            'container and creating another — which loses the URL, the scoped key and ' +
+            'the custom domain.').toEqual([]);
+    });
+    it('clearing the probe sends the empty string the API defines for it', async () => {
+        // '' is how the API says "no probe". The verb spells it --clear so nobody
+        // has to discover that an empty string is the meaningful value, but the
+        // wire form still has to be right.
+        const container = await import('./container.js');
+        await run(() => container.run('health-check', ['c1'], { clear: true, org: ORG }));
+        expect(sdk.container.updateContainer).toHaveBeenCalledWith('hq_live_test', ORG, 'c1', { health_check: '' });
+    });
+    it('refuses /healthz before it costs a round trip', async () => {
+        const container = await import('./container.js');
+        await run(() => container.run('health-check', ['c1', '/healthz'], { org: ORG }));
+        expect(sdk.container.updateContainer).not.toHaveBeenCalled();
+    });
+});

package/dist/commands/container.d.ts

@@ -12,7 +12,9 @@ export declare function splitEnvEntries(raw: string): string[];
 export declare function create(nameArg: string | undefined, flags: Flags): Promise<void>;
 export declare function list(flags: Flags): Promise<void>;
 export declare function get(id: string, flags: Flags): Promise<void>;
+export declare function healthCheck(id: string, flags: Flags): Promise<void>;
 export declare function del(id: string, flags: Flags): Promise<void>;
+export declare function _checkProbePath(hc: string): string;
 export declare function _isTarball(p: string): boolean;
 export declare function deploy(id: string, image: string, flags: Flags): Promise<void>;
 export declare function _parseSmoke(raw: string): sdkContainer.SmokeCheck;

package/dist/commands/container.js

@@ -34,6 +34,7 @@ export const SCHEMA = {
     scope: 'string',
     'no-promote': 'boolean',
     'health-check': 'string',
+    clear: 'boolean',
     smoke: 'string',
     remove: 'boolean',
     source: 'string',
@@ -147,15 +148,7 @@ export async function create(nameArg, flags) {
     if (typeof flags.port === 'number')
         payload.port = flags.port;
     if (typeof flags['health-check'] === 'string') {
-        const hc = flags['health-check'];
-        // The API refuses /healthz, but say so here rather than round-tripping:
-        // the reason is specific and worth stating where the user typed it.
-        if (/^\/?healthz\/?$/i.test(hc)) {
-            error('The runtime intercepts /healthz, so a probe against it never reaches your container —\nit would report healthy no matter what your code does. Use /livez, or any other path.');
-        }
-        if (!hc.startsWith('/'))
-            error(`--health-check must be a path starting with "/" — got "${hc}".`);
-        payload.health_check = hc;
+        payload.health_check = _checkProbePath(flags['health-check']);
     }
     // Repeatable, and create must agree with `container env` on what --env means.
     // If they disagree, a variable settable at creation cannot be changed
@@ -218,6 +211,7 @@ export async function get(id, flags) {
     if (c.port)
         info(`Port:            ${c.port}`);
     info(`URL:             ${c.url || '(not deployed)'}`);
+    info(`Startup probe:   ${c.health_check || '(none)'}`);
     if (c.egress)
         info(`Egress:          ${c.egress}`);
     if (c.custom_domain)
@@ -225,6 +219,39 @@ export async function get(id, flags) {
     info(`Created:         ${c.created_at}`);
     info(`Updated:         ${c.updated_at}`);
 }
+export async function healthCheck(id, flags) {
+    const config = requireConfig();
+    const orgId = requireOrg(flags, config, 'myapi container health-check <id> <path> [--clear]');
+    if (!id)
+        error('Missing id.\nUsage: myapi container health-check <id> /livez   (or --clear to remove it)');
+    const pathArg = typeof flags._probePath === 'string' ? flags._probePath : undefined;
+    if (flags.clear && pathArg) {
+        error('Pass a path or --clear, not both.');
+    }
+    if (!flags.clear && !pathArg) {
+        error('Nothing to change.\nUsage: myapi container health-check <id> /livez   (or --clear to remove the probe)');
+    }
+    // '' is how the API says "no probe" — the verb spells that --clear so nobody
+    // has to discover that an empty string is meaningful.
+    const value = flags.clear ? '' : _checkProbePath(pathArg);
+    info(value ? `› Setting startup probe to ${value}…` : '› Clearing the startup probe…');
+    const res = await sdkContainer.updateContainer(config.api_key, orgId, id, { health_check: value });
+    if (flags.json) {
+        printJson(res);
+        return;
+    }
+    // Same distinction `container env` draws: stored and live are different
+    // states, and only one of them is what the caller asked for.
+    if (res.applied) {
+        success(`Redeployed on the same image — the probe is live${res.revision ? ` (${res.revision})` : ''}.`);
+    }
+    else {
+        info('  Stored. This container has no deployment yet, so it applies on your first deploy.');
+    }
+    info(value
+        ? `  The runtime now waits for ${value} to answer before sending traffic to a new revision.`
+        : '  No startup probe: a new revision takes traffic as soon as the runtime reports it started.');
+}
 export async function del(id, flags) {
     const config = requireConfig();
     const orgId = requireOrg(flags, config, 'myapi container delete <id> [--yes] [--org <id>]');
@@ -234,6 +261,22 @@ export async function del(id, flags) {
     await sdkContainer.deleteContainer(config.api_key, orgId, id);
     success(`Deleted container ${id} (org ${orgId})`);
 }
+// The probe path is validated in exactly one place because `create` and
+// `health-check` must agree on what a valid one is. When a setting is accepted
+// at creation and rejected (or unreachable) afterwards, changing it becomes a
+// delete-and-recreate — which costs the URL, the scoped key and the custom
+// domain. That is the bug this verb exists to close; it should not reappear as
+// a validation mismatch.
+export function _checkProbePath(hc) {
+    // The API refuses /healthz, but say so here rather than round-tripping:
+    // the reason is specific and worth stating where the user typed it.
+    if (/^\/?healthz\/?$/i.test(hc)) {
+        error('The runtime intercepts /healthz, so a probe against it never reaches your container —\nit would report healthy no matter what your code does. Use /livez, or any other path.');
+    }
+    if (!hc.startsWith('/'))
+        error(`A health check must be a path starting with "/" — got "${hc}".`);
+    return hc;
+}
 // _isTarball returns true if the path looks like an already-built tar archive
 // (so we upload it as-is instead of tarring a directory).
 export function _isTarball(p) {
@@ -711,6 +754,18 @@ domain's MyAPI-managed parent domain must already be registered.
 
 Example:
   myapi container domain <id> app.synthesisdaily.com`,
+    'health-check': `myapi container health-check <id> <path> [--clear] [--org <id>]
+
+Set or clear the startup probe on an existing container, rolling a new
+revision on the SAME image. No rebuild.
+
+The runtime waits for this path to answer before sending traffic to a new
+revision, so a bad deploy is caught before it takes any. Not /healthz — the
+runtime answers that before it reaches your container, so the probe would
+pass while your app is down.
+
+  myapi container health-check <id> /livez
+  myapi container health-check <id> --clear`,
     'delete': 'myapi container delete <id> [--org <id>]',
 };
 export async function run(subcommand, args, flags) {
@@ -814,6 +869,7 @@ All commands accept --org <id> (or set default: myapi config set-org <id>).`);
         case 'revisions': return revisions(args[0], flags);
         case 'promote': return promote(args[0], args[1], flags);
         case 'domain': return domain(args[0], args[1], flags);
+        case 'health-check': return healthCheck(args[0], { ...flags, _probePath: args[1] });
         case 'delete': return del(args[0], flags);
         case 'rollback': return rollback(args[0], flags);
         default: error(`Unknown subcommand: ${subcommand}. Run "myapi container --help" for a list of valid subcommands.`);

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

@@ -50,3 +50,13 @@ describe('campaign source flags', () => {
         expect(unread, 'watched by update() but never read when building a source').toEqual([]);
     });
 });
+describe('campaign delete', () => {
+    // The backend shipped DELETE and the CLI did not, so the only way to remove a
+    // campaign was a raw HTTP call. A verb that exists on one side of the wire
+    // and not the other is invisible until someone needs it.
+    it('is dispatched and declared', async () => {
+        const mod = await import('./campaign.js');
+        expect(mod.HELP).toContain('delete <id>');
+        expect(mod.EXPOSES).toContain('DELETE /email/orgs/{org_id}/campaigns/{campaign_id}');
+    });
+});

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

@@ -1,6 +1,6 @@
 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 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  delete <id> Remove it and its recipient rows; what was sent stays in the log\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

@@ -7,6 +7,7 @@ export const EXPOSES = [
     'POST /email/orgs/{org_id}/campaigns',
     'GET /email/orgs/{org_id}/campaigns',
     'GET /email/orgs/{org_id}/campaigns/{campaign_id}',
+    'DELETE /email/orgs/{org_id}/campaigns/{campaign_id}',
     'PATCH /email/orgs/{org_id}/campaigns/{campaign_id}',
     'POST /email/orgs/{org_id}/campaigns/{campaign_id}/resolve',
     'POST /email/orgs/{org_id}/campaigns/{campaign_id}/start',
@@ -29,6 +30,7 @@ export const HELP = `Usage: myapi email campaign <subcommand>
   cancel <id> End it for good; queued recipients are dropped
   recipients <id>  Who it resolved to, and what happened to each
   stats <id>  Counts by state, sent today, and the daily limit
+  delete <id> Remove it and its recipient rows; what was sent stays in the log
 
 A campaign drains at its per-day limit rather than sending at once, so it is
 commonly still active tomorrow — that is the design, not a stall.
@@ -203,6 +205,19 @@ async function transition(verb, id, flags) {
         info(`It sends up to its daily limit and continues tomorrow — check with: myapi email campaign stats ${id}`);
     }
 }
+async function remove(id, flags) {
+    const config = requireConfig();
+    const orgId = requireOrg(flags, config, 'myapi email campaign delete <id>');
+    const r = await sdkEmail.deleteCampaign(config.api_key, orgId, id);
+    if (flags.json) {
+        printJson(r);
+        return;
+    }
+    success(`Deleted campaign ${r.id}`);
+    // People reach for delete to undo a send. It does not undo one, and saying
+    // so here is cheaper than letting them find out from a reply.
+    info('Messages already sent stay in the send log — this removed the campaign, not the mail.');
+}
 async function recipients(id, flags) {
     const config = requireConfig();
     const orgId = requireOrg(flags, config, 'myapi email campaign recipients <id> [--state queued|sent|failed|excluded]');
@@ -252,6 +267,7 @@ export async function run(sub, args, flags) {
         case 'cancel': return transition('cancel', need('myapi email campaign cancel <id>'), flags);
         case 'recipients': return recipients(need('myapi email campaign recipients <id>'), flags);
         case 'stats': return stats(need('myapi email campaign stats <id>'), flags);
+        case 'delete': return remove(need('myapi email campaign delete <id>'), flags);
         default: error(`Unknown subcommand: email campaign ${sub}. Run "myapi email campaign --help".`);
     }
 }

package/dist/skills/my-container-api/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: my-container-api
-version: 1.1.1
+version: 1.1.2
 description: >
   Run containers on demand — long-running services, background workers, and scheduled jobs. The heavier-duty sibling of edge functions, for native deps and long execution.
 triggers: [container, cloud run, dynamic app, custom domain app, service, worker, scheduled job, deploy container, docker image]
-checksum: sha256-80d64f6086e3d16549e530464b8188d9b9db2db5b54696e85c9ddde60d5b40a0
+checksum: sha256-0e1702e51e8d501edf48bdc4da92728d52e79c4273f534ba5ed41511b4803271
 ---
 
 # MyContainerAPI
@@ -19,9 +19,8 @@ The lifecycle is **create → deploy → (optionally) bind a custom domain**.
 - `deploy` takes **either** a pre-built image reference **or** a source
   directory. `--source ./dir` tars the directory, builds it server-side
   (typically ~4 minutes) and deploys the result — **no Docker on your machine,
-  no registry account, no image to push**. If you can write a Dockerfile you
-  can deploy; you do not need to be able to run one.
-- `domain` puts the container on a **custom domain** — how you serve a dynamic app at `app.yourbrand.com`.
+  no registry account, no image to push**.
+- `domain` puts the container on a **custom domain** — a dynamic app at `app.yourbrand.com`.
 
 ### Deploying safely
 
@@ -36,8 +35,8 @@ myapi container deploy <id> --source ./app --smoke 'GET / contains assets/'
 ```
 
 **Assert on content, not status.** A build whose frontend never bundled still
-binds its port and answers `200` — that is how a placeholder page reached
-production and served a dead page for fifteen minutes.
+binds its port and answers `200` — that is how a placeholder page served a dead
+page for fifteen minutes. Same reasoning as the startup probe below.
 
 **`--no-promote`** holds the revision back and prints a URL to test yourself,
 then `myapi container promote <id> <revision>`. Use it when the check is more
@@ -47,9 +46,10 @@ traffic is not withheld and the output says so.
 **`myapi container rollback <id>`** returns traffic to the previous ready
 revision in seconds, no rebuild.
 
-`--health-check /livez` at create makes the startup probe an HTTP request
-rather than a bare TCP connect. `/healthz` is refused — the runtime intercepts
-it, so the probe would never reach your container.
+`--health-check /livez` makes the startup probe an HTTP request, not a bare TCP
+connect — at create, or later with `myapi container health-check <id> /livez`
+(`--clear` removes it), which rolls a new revision on the same image.
+`/healthz` is refused: the runtime answers it before your container does.
 
 ### Custom domains (dynamic apps)
 

package/dist/skills/my-email-api/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: my-email-api
-version: 1.2.0
+version: 1.2.1
 description: >
   Send transactional and bulk email from your own domain. Create mailboxes, send/receive messages, generate AI templates, and manage warmup.
 triggers: [email, mailbox, send email, transactional email, template, warmup, inbox, outbox, ses, sender reputation]
-checksum: sha256-897cf3dbc843ca06d02aecf298151e8635890852a5db8ab4035ee59df8db0aa9
+checksum: sha256-b458699a69c15d02d33dab6bc00445f05fb6e55ee844d35d8b745a13a6533b9e
 ---
 
 # MyEmailAPI
@@ -28,7 +28,7 @@ A registered domain via **mydomainapi** is the prerequisite — mailboxes need a
 | `email message` | `send`, `status`, `sent`, `inbox`, `outbox`, `get` | Transactional send + read |
 | `email warmup` | `start`, `stats`, `pause`, `resume`, `stop` | IP/domain warmup for sending reputation |
 | `email template` | `generate`, `list`, `get`, `preview`, `edit`, `send-test`, `delete` | AI-generated HTML templates |
-| `email campaign` | `create`, `list`, `get`, `update`, `resolve`, `start`, `pause`, `resume`, `cancel`, `recipients`, `stats` | Scheduled bulk send that drains at a daily limit |
+| `email campaign` | `create`, `list`, `get`, `update`, `resolve`, `start`, `pause`, `resume`, `cancel`, `recipients`, `stats`, `delete` | Scheduled bulk send that drains at a daily limit |
 <!-- generated:end -->
 
 ## Examples
@@ -120,7 +120,9 @@ Four things that decide how you use it:
 
 `pause` stops after the message in flight; `resume` continues; `cancel` ends it
 and drops what was queued. Status `paused_insufficient_funds` means the account
-could not pay — top up or enable auto-recharge, then `resume`.
+could not pay — top up or enable auto-recharge, then `resume`. `delete` removes
+the campaign and its recipients, never the send log — it tidies up, it does not
+unsend, and it refuses while a campaign is active.
 
 ## Notes
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@myapihq/cli",
   "license": "Apache-2.0",
-  "version": "2.23.2",
+  "version": "2.24.0",
   "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.2"
+    "@myapihq/sdk": "^2.24.0"
   },
   "devDependencies": {
     "@types/node": "^25.6.0",