@dench.com/cli 2.6.0 → 2.7.0

package/cron.ts

@@ -18,11 +18,9 @@
  * both formats; we just pass whichever bearer the parent runtime
  * resolved through `sessionToken`.
  *
- * Convex calls go direct via `ConvexHttpClient` (same pattern as
- * `cli/crm.ts`); `run-now` is the one operation that goes through
- * the REST API hop (`POST /api/cron/jobs/<id>/run-now`) because it
- * needs to start a Vercel Workflow which can only be done from a
- * Next.js route.
+ * Convex calls generally go direct via `ConvexHttpClient` (same pattern as
+ * `cli/crm.ts`). Run-now and delete go through REST: run-now starts a Vercel
+ * Workflow, while delete coordinates upstream app-event cleanup.
  *
  * Subcommands:
  *   list                                 List all cron jobs in the org.
@@ -166,6 +164,28 @@ async function getJson(
   return json;
 }
 
+async function deleteJson(
+  url: string,
+  headers: Record<string, string>,
+): Promise<unknown> {
+  const response = await fetch(url, { method: "DELETE", headers });
+  const text = await response.text();
+  let json: unknown;
+  try {
+    json = text ? JSON.parse(text) : null;
+  } catch {
+    json = { raw: text };
+  }
+  if (!response.ok) {
+    const detail =
+      json && typeof json === "object" && "error" in json
+        ? String((json as Record<string, unknown>).error)
+        : JSON.stringify(json);
+    throw new CronCliError(`${url} failed (${response.status}): ${detail}`);
+  }
+  return json;
+}
+
 async function callQuery(
   ctx: CronCliContext,
   fn: Parameters<ConvexHttpClient["query"]>[0],
@@ -339,9 +359,6 @@ const createCronTriggerRef = makeFunctionReference<"mutation">(
 const updateCronTriggerRef = makeFunctionReference<"mutation">(
   "functions/triggers:updateCronTrigger",
 );
-const deleteCronTriggerRef = makeFunctionReference<"mutation">(
-  "functions/triggers:deleteCronTrigger",
-);
 const setCronEnabledRef = makeFunctionReference<"mutation">(
   "functions/triggers:setCronEnabled",
 );
@@ -709,7 +726,10 @@ async function runUpdate(ctx: CronCliContext): Promise<void> {
 
 async function runDelete(ctx: CronCliContext): Promise<void> {
   const jobId = shift(ctx.args, "job id");
-  const result = await callMutation(ctx, deleteCronTriggerRef, { jobId });
+  const result = await deleteJson(
+    `${getApiBase()}/api/cron/jobs/${encodeURIComponent(jobId)}`,
+    apiKeyHeaders(ctx.sessionToken ?? ""),
+  );
   out(ctx, result);
 }
 

package/email.ts

@@ -197,6 +197,8 @@ Usage:
   dench email identity disable --identity <identityId|email|domain> [--json]
   dench email identity restore --identity <identityId|email|domain> [--json]
   dench email identity delete --identity <identityId|email|domain> [--json]
+  dench email identity forward --identity <identityId|email> --to inbox@you.com [--json]   # forward this sender's sequence replies
+  dench email identity forward --identity <identityId|email> --off [--json]                # turn forwarding off
   dench email send --from founder@example.com --to "Ada <ada@x.com>,bob@y.com" --subject "Hi" (--html-file body.html | --text "...") [--cc ...] [--bcc ...] [--from-name "Ada"] [--reply-to support@x.com] [--reply-message-id <messageId|rfc-id>] [--json]
   dench email message status --message <messageId> [--json]
   dench email message list [--limit 25] [--json]
@@ -500,6 +502,7 @@ async function runIdentity(ctx: EmailCliContext) {
                 `${identity.identityId}  ${identity.fromEmail}  type=${identity.type}` +
                 `${identity.domain ? ` domain=${identity.domain}` : ""}` +
                 `  delivery=${identity.deliveryVerificationStatus}  workspace=${identity.denchVerificationStatus}` +
+                `${identity.forwardRepliesTo ? `  forward=${identity.forwardRepliesTo}` : ""}` +
                 `${identity.disabled ? "  DISABLED" : ""}`,
             )
             .join("\n");
@@ -545,6 +548,34 @@ async function runIdentity(ctx: EmailCliContext) {
     out(ctx, payload, text);
     return;
   }
+  if (sub === "forward") {
+    // Configure where a sender's managed sequence replies are forwarded.
+    // `--to <email>` turns it on (composed from the verified sender, Reply-To =
+    // the prospect); `--off` clears it. Replies are always still captured
+    // in-app regardless — forwarding is an extra copy to a chosen inbox.
+    const identity = requiredFlag(ctx.args, "--identity");
+    const off = hasFlag(ctx.args, "--off");
+    const to = off ? "" : (getFlag(ctx.args, "--to")?.trim() ?? "");
+    if (!off && !to) {
+      throw new Error(
+        "Provide --to <email> to forward this sender's replies, or --off to turn forwarding off.",
+      );
+    }
+    const payload = (await callMutation(
+      ctx,
+      "functions/emailCampaigns:setSenderReplyForward",
+      { identity, forwardRepliesTo: to },
+    )) as JsonRecord;
+    const forwardTo =
+      typeof payload.forwardRepliesTo === "string"
+        ? payload.forwardRepliesTo
+        : null;
+    const text = forwardTo
+      ? `Replies to ${identity}'s sequences will be forwarded to ${forwardTo}.`
+      : `Reply forwarding turned off for ${identity}.`;
+    out(ctx, { ok: true, ...payload }, text);
+    return;
+  }
   if (sub === "dns") {
     const identity = requiredFlag(ctx.args, "--identity");
     if (!identity.includes("@") && !identity.includes(".")) {

package/lib/command-registry.ts

@@ -29,6 +29,7 @@ export type CustomOperation = {
     | "commandsList"
     | "chatSpawn"
     | "chatFollow"
+    | "cronDelete"
     | "cronRunNow"
     | "billingTopup"
     | "upgrade"
@@ -1895,7 +1896,7 @@ const rawApiOperations = [
     path: "/routines/{jobId}",
     requestSchema: anyObject,
     responseSchema: anyResponse,
-    backend: convex("mutation", "functions/triggers:deleteCronTrigger"),
+    backend: custom("cronDelete", "bearer"),
   }),
   op({
     id: "cron.enable",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dench.com/cli",
-  "version": "2.6.0",
+  "version": "2.7.0",
   "description": "Dench agent workspace CLI. v2 unifies auth behind `dench signin`; the legacy `dench login` / `dench onboard` / `dench setup` / `dench what-can-i-do` / `dench register` commands now error with a redirect.",
   "type": "module",
   "bin": {