@myapihq/cli 2.6.1 → 2.7.0

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

@@ -4,7 +4,7 @@ version: 1.0.0
 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-d25fff35df7bf67bebabb6cc228f322b108d8472035cbda70756d720b8db502d
+checksum: sha256-4847ab675fa971bbd0fdd83f0039d9110ba4c38e406860fe9265dd540b7f299e
 ---
 
 # MyContainerAPI
@@ -19,6 +19,23 @@ The lifecycle is **create → deploy → (optionally) bind a custom domain**.
 - `deploy` ships a pre-built image reference to the runtime and makes the container live at a generated URL.
 - `domain` puts the container on a **custom domain** — how you serve a dynamic app at `app.yourbrand.com`.
 
+### Deploying safely
+
+A deploy takes 100% of traffic the moment it lands, so a broken build is live
+before you can look at it. Two ways to avoid that:
+
+- `--smoke 'GET / contains assets/'` — the platform deploys the revision with
+  NO traffic, runs the assertion, and promotes only if it holds. A failure
+  leaves the previous revision serving. **Assert on content, not status**:
+  "returns 200" is true of a placeholder page too.
+- `--no-promote` — build the revision and hold it back. You get a URL to
+  exercise it, then `myapi container promote <id> <revision>`.
+
+`--health-check /livez` at create time makes the startup probe an HTTP request
+instead of a bare TCP connect. `/healthz` is refused: the runtime intercepts
+it, so the probe would never reach your container and would report success
+regardless.
+
 ### Custom domains (dynamic apps)
 
 `myapi container domain <id> <domain>` binds a custom domain to a **deployed** container, served over HTTPS automatically. This is the path for a dynamic backend on a real domain — distinct from `my-funnel-api`, which serves static sites.
@@ -36,7 +53,9 @@ Get it right:
 | Command | What it does |
 |---|---|
 | `myapi container create --name <name> [--type service\|worker\|job] [--cron <expr>] [--cpu <n>] [--memory <size>] [--port <n>] [--env K=V,...]` | Register a container, get its scoped API key (once) |
-| `myapi container deploy <id> <image-ref>` | Ship a pre-built image and go live (rotates the scoped key) |
+| `myapi container deploy <id> <image-ref> [--no-promote] [--smoke '<assertion>']` | Ship a pre-built image (rotates the scoped key) |
+| `myapi container revisions <id>` | List revisions and the traffic each takes |
+| `myapi container promote <id> <revision>` | Move all traffic to a revision (seconds, no rebuild) |
 | `myapi container list` | List containers in your org |
 | `myapi container get <id>` | Inspect a container (status, URL, custom domain) |
 | `myapi container logs <id> [--tail <n>] [--scope all]` | Recent runtime logs, newest first (`--scope all` adds platform audit records) |
@@ -47,13 +66,26 @@ Get it right:
 ## Examples
 <!-- llm:start -->
 ```bash
-# 1. Register a service container
-myapi container create --name api --type service --port 8080
+# 1. Register a service container. --health-check makes the startup probe an
+#    HTTP request instead of a bare TCP connect.
+myapi container create --name api --type service --port 8080 --health-check /livez
 # → prints a scoped API key ONCE — save it if your code needs it
 
-# 2. Deploy a pre-built image
+# 2a. Deploy. Plain form takes 100% of traffic immediately.
 myapi container deploy <id> registry.example.com/my-app:v1
 
+# 2b. SAFER: assert before any traffic moves. The revision is deployed with no
+#     traffic, checked, and promoted only if the check holds. Assert on
+#     CONTENT — a broken build still returns 200.
+myapi container deploy <id> registry.example.com/my-app:v1 \
+  --smoke 'GET / contains assets/'
+
+# 2c. Or hold it back and look yourself.
+myapi container deploy <id> registry.example.com/my-app:v1 --no-promote
+# → prints a revision URL serving 0% of traffic
+myapi container revisions <id>
+myapi container promote <id> <revision>
+
 # 3. Serve it on a custom domain. The parent domain must already be
 #    registered: myapi domain register synthesisdaily.com
 myapi container domain <id> app.synthesisdaily.com

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

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   The canonical store of engaged contacts + companies for an org. Auto-ingests from inbound webhooks via a configurable dot-path. Fixed lifecycle_stage enum (cold | warm | qualified | customer | churned). Append-only event timeline with reserved kinds. Soft delete + restore. Promote-from-Goldfox closes the discovery → engagement loop.
 triggers: [crm, contact, company, lead, engagement, pipeline, lifecycle, qualified, customer, webhook ingest, promote]
-checksum: sha256-085cb990a292ba815d7c59a58fb25816d52bf33ad5019a7d90abf4123383a67c
+checksum: sha256-50cbdd28ed2a901b7a75f1a6c1df1c225d256a8d281ad86cf1e3b42511edc2fe
 ---
 
 # MyCRMAPI
@@ -91,7 +91,7 @@ A contact promoted from Goldfox carries a `goldfox_person_id`. In v2 the GET res
 ### Contacts
 | Command | What it does |
 |---|---|
-| `myapi crm contacts list [--limit N]` | List all contacts (newest engagement first) |
+| `myapi crm contacts list [--limit N] [--offset N]` | List all contacts (newest engagement first) |
 | `myapi crm contacts search [--stage ...] [--source ...] [--email ...] [--min/max-last-engagement-days N]` | Filter contacts |
 | `myapi crm contacts create <email> [--first-name ...] [--last-name ...] [--stage ...] [--custom-json ...]` | Manually create (source='manual') |
 | `myapi crm contacts get <id>` | Fetch one contact (with embedded Goldfox enrichment when available) |
@@ -158,11 +158,10 @@ myapi crm contacts events <id> --kind webhook_received
 
 ## Notes
 
-- **No pagination. Do not build a paging loop.** The API ignores `offset`
-  (every page repeats page one), there is no cursor, and `total` is the page
-  size, not the match count. The CLI rejects `--offset` rather than lie. If
-  exactly `--limit` rows come back, assume more exist: raise `--limit` or
-  narrow with filters.
+- **Paginate with `--limit` + `--offset`.** `total` is the true match count
+  and the response carries `has_more`; branch on `has_more` rather than doing
+  arithmetic against `total`. (Both were broken until 2026-07-28. Cached
+  guidance saying the CRM cannot paginate is stale.)
 - **Reserved event kinds — no custom events in v1.** If an agent needs custom state per contact, use `myapi database` keyed by contact id. The curated timeline stays the authoritative engagement record.
 - **`external_id` on an event payload** is the backend's idempotency key — a duplicate of the action's natural id (`goldfox_person_id`, `delivery_id`). Read the semantic field instead; legacy `message_id` rows hold the same value.
 - **Only `webhook_received` fires today.** Email and pixel auto-ingest are coming; the CLI surface will not change.

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

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Register new domains and manage edge settings. Required before a funnel can go live on a custom URL.
 triggers: [domain, register domain, dns, custom domain, edge, cdn, security level, browser check, renew, namecheap]
-checksum: sha256-067ab2cc412c1f1f34aaeeec5890f9eb77f680f5b2d1c847e376336702cd8344
+checksum: sha256-8f96d19c11c3591af71e9d73b2cea6d83f40abbfa1c58c5674dbe15db02efa3c
 ---
 
 # MyDomainAPI
@@ -88,7 +88,7 @@ myapi domain update-settings example.com \
 myapi domain import example.com
 # → Returns nameservers; set them at your current registrar.
 myapi domain status example.com --watch
-# → Polls until active. Backend live-checks Cloudflare each poll.
+# → Polls until active. Backend live-checks the DNS provider each poll.
 
 # Fix a record after import (e.g. clean up SPF)
 myapi domain records list example.com --type TXT

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

@@ -2,26 +2,26 @@
 name: my-function-api
 version: 1.0.0
 description: >
-  Deploy JavaScript functions to the MyAPI edge runtime (Cloudflare Workers). Register a function, upload a single-file JS bundle, get a live HTTP invocation URL or run it on a cron schedule. Each function gets a scoped capability key for cross-slot calls.
+  Deploy JavaScript functions to the MyAPI edge runtime. Register a function, upload a single-file JS bundle, get a live HTTP invocation URL or run it on a cron schedule. Each function gets a scoped capability key for cross-slot calls.
 triggers: [function, deploy function, edge function, serverless, cloudflare worker, cron, scoped api key, capability key, invocation url, bundle]
-checksum: sha256-ada0a52fdd9c0ba14ca86496e1c5c42e8b018155c3e8c83edba071fa6bd0b7e9
+checksum: sha256-610e16c931e44d43ee6ac94a32e6d852bb900cdf6f5eea61aaeae7bb95a0814e
 ---
 
 # MyFunctionAPI
 
-Deploy backend code without running a server. Register a function, upload a single-file JS bundle, and it goes live on the MyAPI edge runtime (Cloudflare Workers) with a public invocation URL — or runs on a cron schedule. Each function carries a scoped capability key so it can call other MyAPI slots with its own authority.
+Deploy backend code without running a server. Register a function, upload a single-file JS bundle, and it goes live on the MyAPI edge runtime with a public invocation URL — or runs on a cron schedule. Each function carries a scoped capability key so it can call other MyAPI slots with its own authority.
 
 The full loop is live: **create → deploy → invoke → inspect runs → set secrets**.
 
 ## Capabilities
 <!-- llm:start -->
-**Two-step lifecycle: register, then deploy.** `myapi fn create --name <slug>` persists the function record and mints a `scoped_api_key`, returned **exactly once** (save it if you need it). `myapi fn deploy <id> <bundle.js>` uploads a single-file JavaScript bundle (≤4MB); the backend wraps it with the MYAPI shim and ships it to Cloudflare Workers. After deploy the function has a live `invocation_url`.
+**Two-step lifecycle: register, then deploy.** `myapi fn create --name <slug>` persists the function record and mints a `scoped_api_key`, returned **exactly once** (save it if you need it). `myapi fn deploy <id> <bundle.js>` uploads a single-file JavaScript bundle (≤4MB); the backend wraps it with the MYAPI shim and ships it to the edge runtime. Propagation is typically 4-45s, so poll the invocation URL rather than redeploying. After deploy the function has a live `invocation_url`.
 
 **Scoped key = capability key.** It is **org-locked**. By default it inherits the deployer's slot grants; narrow it at create time with `--scope <slot>[,<slot>...]` (comma-separated, e.g. `--scope email,storage`) — the primary way to deploy a deliberately narrow function. Grants can never exceed the caller's, so a function never out-reaches the credential that created it. It is rejected with `403 SCOPE_FORBIDDEN` at `/hq/*`, `/admin/*`, `/internal/*`. **Deploy rotates this key** — the fresh value is printed once on every deploy. (Minting a narrow account key first — `myapi keys create --grant ...` — is only needed when the *deploy credential itself* must be constrained, e.g. handing deploy rights to another system.)
 
 **HTTP or cron triggers.** Default is `http` — the function gets a public invocation URL once deployed. Pass `--cron "<expr>"` at create time to run on a schedule (e.g. `"0 8 * * *"`) instead.
 
-**Secrets via Worker Secrets.** `myapi fn env <id> <name> <value>` sets a secret (Stripe key, API token, …) as a Cloudflare Worker Secret on a deployed function. The value is encrypted at rest by Cloudflare and never stored or echoed by MyAPI. The function must already be deployed.
+**Secrets are encrypted at rest.** `myapi fn env <id> <name> <value>` sets a secret (Stripe key, API token, …) on a deployed function. The value is encrypted at rest by the edge runtime and never stored or echoed by MyAPI. The function must already be deployed.
 
 **Inspect invocations.** `myapi fn runs <id>` lists recent invocation records (most recent first, up to 100) with status, duration, and any error message.
 
@@ -36,7 +36,7 @@ Name rules (validated client- and server-side, kept identical):
 |---|---|
 | `myapi fn create --name <name> [--cron <expr>] [--scope <slot>[,<slot>...]]` | Register a function record + receive scoped API key (returned once). `--scope` narrows the key's slot grants |
 | `myapi fn deploy <id> <bundle.js>` | Upload a single-file JS bundle (≤4MB) and go live; rotates the scoped key |
-| `myapi fn env <id> <name> <value>` | Set a Worker Secret on a deployed function |
+| `myapi fn env <id> <name> <value>` | Set an encrypted secret on a deployed function |
 | `myapi fn runs <id>` | List recent invocation records (status, duration, errors) |
 | `myapi fn list` | List functions in your org |
 | `myapi fn get <id>` | Inspect a function (name, trigger, invocation URL) |
@@ -58,7 +58,7 @@ myapi fn deploy fn_abc123 ./dist/bundle.js
 #   Invocation URL:  https://fn-abc123.<...>.workers.dev
 #   Scoped API key was rotated. New value (returned once): hq_live_...
 
-# Set a secret (encrypted at rest by Cloudflare; never echoed)
+# Set a secret (encrypted at rest; never echoed)
 myapi fn env fn_abc123 STRIPE_KEY sk_live_...
 
 # Inspect recent invocations

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@myapihq/cli",
   "license": "Apache-2.0",
-  "version": "2.6.1",
+  "version": "2.7.0",
   "description": "MyAPI command-line interface",
   "repository": {
     "type": "git",
@@ -35,12 +35,13 @@
     "lint:help-order": "node scripts/lint-help-order.js",
     "lint:exposes": "node scripts/lint-exposes.js",
     "lint:request-fields": "node scripts/lint-request-fields.js",
+    "audit:doctor": "npm run build && node scripts/audit-doctor.js",
     "lint:docs": "node scripts/lint-docs.js",
     "lint:skills": "node scripts/copy-skills.js && node scripts/lint-skills.js",
     "lint:skills:strict": "node scripts/copy-skills.js && node scripts/lint-skills.js --strict"
   },
   "dependencies": {
-    "@myapihq/sdk": "^2.6.1"
+    "@myapihq/sdk": "^2.7.0"
   },
   "devDependencies": {
     "@types/node": "^25.6.0",