@getdial/cli 0.44.1 → 0.45.0

package/dist/commands/lookup/lookup.js

@@ -4,7 +4,22 @@ import { printDialError } from "../../lib/cli-error.js";
 /** Channels in the order they are printed, with the label each one shows as. */
 const CHANNEL_LABELS = {
     imessage: "iMessage",
+    whatsapp: "WhatsApp",
 };
+/**
+ * How one channel's verdict reads.
+ *
+ * Three states, not two. `null` means Dial did not answer for that channel — today only because the
+ * account holds no WhatsApp number of its own — and printing it as `no` would say the number is
+ * unreachable, which is the one thing it does not mean. A `?? "no"` here is the whole bug.
+ */
+function verdictOf(supported) {
+    if (supported === true)
+        return "yes";
+    if (supported === false)
+        return "no";
+    return "unknown";
+}
 export async function runLookup(number, opts) {
     try {
         const result = await lookupNumber(number);
@@ -17,7 +32,7 @@ export async function runLookup(number, opts) {
             // A channel added to the API after this CLI shipped still prints, under its
             // raw key — reporting an unknown channel is better than hiding it.
             const label = CHANNEL_LABELS[channel] ?? channel;
-            console.log(`  ${label.padEnd(9)} ${supported ? "yes" : "no"}`);
+            console.log(`  ${label.padEnd(9)} ${verdictOf(supported)}`);
         }
         return 0;
     }

package/dist/lib/ops/lookup.js

@@ -9,7 +9,9 @@ import { DialError } from "./errors.js";
  *
  * A lookup Dial could not complete comes back as an error (502), never as a
  * negative verdict — so a `false` here always means the number genuinely is not
- * reachable on that channel, and callers can treat the two differently.
+ * reachable on that channel, and a `null` always means Dial did not answer for
+ * that channel. Neither ever means "we could not find out", and callers can
+ * treat all three differently.
  */
 export async function lookupNumber(number) {
     const auth = maybeAuth();

package/dist/mcp/tools/lookup-number.js

@@ -17,13 +17,22 @@ export const lookupNumberTool = {
             "are added over time. The answer is point-in-time, not a property of the number — someone who changes " +
             "device or turns the service off stops being reachable — so treat `true` as a strong signal for picking " +
             "a channel rather than a promise that the send will land. A lookup that fails is an error, never a " +
-            "`false`, so a `false` always means the number genuinely isn't reachable there.",
+            "`false` and never a `null`, so a `false` always means the number genuinely isn't reachable there. " +
+            "`whatsapp` is `null` when this account has no WhatsApp number of its own: a WhatsApp check is made " +
+            "from a WhatsApp line, so it is answered only for accounts that have one. `null` says something about " +
+            "the account, never about the number — do not report it as unreachable.",
         inputSchema,
         outputSchema: {
             number: z.string().describe("The number you asked about, normalized to E.164"),
             supports: z
                 .object({
                 imessage: z.boolean().describe("Whether the number can currently receive iMessage"),
+                whatsapp: z
+                    .boolean()
+                    .nullable()
+                    .describe("Whether the number can currently receive WhatsApp: true reachable, false not " +
+                    "reachable, null this account has no WhatsApp number so the check was not made. " +
+                    "null is never a failure and never means unreachable."),
             })
                 .describe("One key per channel, true when the number can be reached there"),
         },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getdial/cli",
-  "version": "0.44.1",
+  "version": "0.45.0",
   "description": "Dial CLI — install, sign up, and run the local listen service.",
   "license": "MIT",
   "repository": {