@myapihq/cli 1.3.4 → 1.3.5

package/dist/commands/domain.js

@@ -114,23 +114,44 @@ export async function importCmd(domainArg, flags) {
     }
     success(`Imported ${res.domain} (status: ${res.status})`);
     info('');
-    info(`Nameservers (set these at your current registrar):`);
-    for (const ns of res.nameservers)
-        info(`  ${ns}`);
-    info('');
-    if (res.preserved_records.length > 0) {
-        info(`Preserved DNS records (${res.preserved_count} found — verify before the NS change):`);
-        printTable(res.preserved_records.map(r => ({ type: r.type, name: r.name, content: r.content, ttl: r.ttl })), { flags });
+    // Defensive — the backend has shipped this response with a non-array
+    // `nameservers` (the domain_id string mis-serialized into the field) and
+    // missing `preserved_records` in some states. JS iterating a string
+    // prints char-per-line and reading .length on undefined crashes; see
+    // docs/cross-repo-prompts/backend-domain-import-response-shape.md. Never
+    // trust the shape blindly — degrade to pointing at `domain status`,
+    // which is queryable for the real values.
+    if (Array.isArray(res.nameservers) && res.nameservers.length > 0) {
+        info(`Nameservers (set these at your current registrar):`);
+        for (const ns of res.nameservers)
+            info(`  ${ns}`);
+        info('');
+    }
+    else {
+        info(`⚠ Backend returned an unexpected nameservers shape (got ${typeof res.nameservers}).`);
+        info(`  The domain is imported — fetch the real nameservers with:`);
+        info(`    myapi domain status ${res.domain} --json`);
+        info('');
+    }
+    const preserved = Array.isArray(res.preserved_records) ? res.preserved_records : [];
+    const preservedCount = typeof res.preserved_count === 'number' ? res.preserved_count : preserved.length;
+    if (preserved.length > 0) {
+        info(`Preserved DNS records (${preservedCount} found — verify before the NS change):`);
+        printTable(preserved.map(r => ({ type: r.type, name: r.name, content: r.content, ttl: r.ttl })), { flags });
         info('');
     }
     else {
         info(`No DNS records detected via public probe — verify directly with your registrar before the NS change.`);
         info('');
     }
-    info(res.probe_warning);
-    info('');
-    info(res.next_step);
-    info('');
+    if (res.probe_warning) {
+        info(res.probe_warning);
+        info('');
+    }
+    if (res.next_step) {
+        info(res.next_step);
+        info('');
+    }
     info(`After changing nameservers, watch activation with:`);
     info(`  myapi domain status ${res.domain} --watch`);
 }

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

@@ -50,7 +50,7 @@ pixel_visit | webhook_received
 
 Agents cannot write events directly — the closed enum is intentional. If you need custom state, use **mydatabaseapi** (KV) keyed on the contact id; the curated timeline stays authoritative for engagement.
 
-**Engagement-event kinds bump `last_engagement_at`**: email_sent/opened/clicked/replied, pixel_visit, webhook_received. Admin kinds (created, promoted, stage_changed) don't. That's the right semantics — promoting a Goldfox lead into the CRM is not engagement.
+**Engagement-event kinds bump `last_engagement_at`**: email_sent/opened/clicked/replied, pixel_visit, webhook_received. Admin kinds (created, promoted, stage_changed) don't — promoting a Goldfox lead isn't engagement.
 
 ### Auto-ingest
 
@@ -157,8 +157,7 @@ myapi crm contacts events <id> --kind webhook_received
 ## Notes
 
 - **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.
-- **Event payloads carry an `external_id`** field used by the backend's idempotency index — same value as the natural id of the underlying action (`goldfox_person_id` for `promoted`, `delivery_id` for `webhook_received`, future `message_id` for `email_sent`). Read the semantic field (e.g. `goldfox_person_id`); `external_id` is a backend-internal duplicate. Old rows may still carry a legacy `message_id` field — same value as `external_id`; safe to ignore.
-- **Goldfox enrichment field deferred** — the live join lands once the BQ get-by-id helper is wired backend-side. CLI treats it as optional today.
+- **Event payloads carry an `external_id`** — the backend's idempotency key, equal to the underlying action's natural id (`goldfox_person_id` for `promoted`, `delivery_id` for `webhook_received`). Read the semantic field; `external_id` is a backend-internal duplicate. A legacy `message_id` on old rows holds the same value — safe to ignore.
 - **Email + Pixel auto-ingest not yet wired**. Only `webhook_received` events fire today. Email and pixel ingest are coming — the CLI surface stays unchanged when they land.
 - **Free in v1.** Metered later if usage shows a need.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@myapihq/cli",
   "license": "Apache-2.0",
-  "version": "1.3.4",
+  "version": "1.3.5",
   "description": "MyAPI command-line interface",
   "type": "module",
   "files": [
@@ -29,7 +29,7 @@
     "lint:changelog": "node ../../scripts/lint-changelog.js"
   },
   "dependencies": {
-    "@myapihq/sdk": "^1.3.4"
+    "@myapihq/sdk": "^1.3.5"
   },
   "devDependencies": {
     "@types/node": "^25.6.0",