@koda-sl/baker-cli 0.383.0-dev.2caa8a15e → 0.383.0

package/dist/cli.js

@@ -70,7 +70,7 @@ import {
   validateCanvasDeep,
   withoutCastName,
   ytDlpBlockSignal
-} from "./chunk-CHJOTJTZ.js";
+} from "./chunk-FGHMWBUD.js";
 import {
   NAME_CONTAINS_ARG,
   csvOrJson,
@@ -28398,10 +28398,19 @@ var metaMediaCommand = defineCommand68({
 
 // src/commands/ads/meta/pages.ts
 import { defineCommand as defineCommand69 } from "citty";
+function advertisablePages(data) {
+  return data.filter((p) => Array.isArray(p.tasks) && p.tasks.includes("ADVERTISE"));
+}
 function pageSelectionHints(data) {
-  if (data.length > 1) {
+  const advertisable = advertisablePages(data);
+  if (advertisable.length > 1) {
+    return [
+      "MULTIPLE Pages can run ads \u2014 do NOT guess. Confirm with the user which Page an ad should run from before passing --page to `creatives create`; a wrong Page publishes the ad under the wrong brand identity and staging will not catch it."
+    ];
+  }
+  if (data.length > 0 && advertisable.length === 0) {
     return [
-      "MULTIPLE Pages can run ads from the selected Meta ad accounts \u2014 do NOT guess. Confirm with the user which Page an ad should run from before passing --page to `creatives create`; a wrong Page publishes the ad under the wrong brand identity and staging will not catch it."
+      "NO Page can run ads \u2014 none of the connected user's Pages carry the ADVERTISE task. Ask the user to grant Advertise access to the right Page before creating an ad; a readable-but-non-advertising Page still passes staging and would fail or run under the wrong identity."
     ];
   }
   return [];
@@ -28409,7 +28418,7 @@ function pageSelectionHints(data) {
 var pagesCommand = defineCommand69({
   meta: {
     name: "pages",
-    description: `List the Facebook Pages that the selected Meta ad accounts can promote. Every Meta ad publishes from a Page, so use this to identify the Page an ad should run from. If more than one Page is listed, confirm with the user which Page to use \u2014 a wrong Page publishes under the wrong brand identity.
+    description: `List the Facebook Pages the connected user manages. Every Meta ad publishes from a Page, so use this to identify the Page an ad should run from. The 'tasks' field shows what the user can do on each Page (ADVERTISE means it can back ads). If exactly one Page can ADVERTISE, use it; if more than one can, confirm with the user which Page to use; if none can, ask the user to grant Advertise access \u2014 a wrong or non-advertising Page publishes under the wrong brand identity.
 
 Examples:
   baker ads meta pages`
@@ -28670,7 +28679,7 @@ Discovery:
   baker ads meta accounts                                \u2014 accounts in this company's connected scope
   baker ads meta accounts --include-all                  \u2014 every account the token can see
   baker ads meta businesses                              \u2014 Business Manager IDs
-  baker ads meta pages                                   \u2014 Facebook Pages the selected ad accounts can promote (an ad's identity)
+  baker ads meta pages                                   \u2014 Facebook Pages the user manages (an ad's identity)
   baker ads meta lead-forms --page-id 100635183117758    \u2014 instant (lead) forms on a Page, with lead counts
   baker ads meta leads --form-id 987654321               \u2014 the leads one form collected (contact details masked)