@koda-sl/baker-cli 0.192.1 → 0.192.2

package/README.md

@@ -789,7 +789,7 @@ baker ads meta pixels --pixel-id 9988 --stats --days 7
 
 Meta writes mirror the Google/LinkedIn model: they **never hit the Graph API when you run them**. Each op is validated at stage time (field shapes, budget rules, page/Instagram identity ownership, CBO/ABO exclusivity, status-transition legality), shows in the dashboard chat as a pending Meta change, and applies only when the chat is published. Meta has no atomic batch mutate, so ops apply **sequentially** on publish — one failure skips its dependents but the publish completes.
 
-If the company's `metaAdsWriteEnabled` flag is off (the default), publish runs the identical lifecycle **simulated** — fake `sim_meta_*` ids, zero Meta calls. The stage response and `baker ads meta draft` show `mode: "simulated"`.
+**That publish reaches the real ad account for every company** — Meta writes are generally available, with no per-company flag and no simulated mode to turn on. Discarding the chat before it completes is what undoes a staged change.
 
 Chain a full ad from scratch with `meta_temp_*` refs (each create returns one):
 
@@ -999,7 +999,7 @@ draft [list|remove <ref>|clear|amend <ref>|show <ref>]   # review/undo/amend sta
 
 Write commands never call the LinkedIn API at stage time. Each stages an op on the current chat's draft, fully validated at staging (field limits, enums, budget minimums, URN shapes, parent existence, Baker media readiness, status-transition legality). Validation errors are structured per-field; non-blocking warnings (Maximum Delivery when no `--bid`, budget below playbook floor, audience under 300 rows, >4 lead-form questions, audience expansion/LAN on) come back in the stage envelope. Ops apply when the chat is published.
 
-If the company's LinkedIn-write flag is off (the default), publish runs the identical lifecycle **simulated** — fake `urn:li:simulated:*` results, zero LinkedIn calls. The stage response and `baker ads linkedin draft` show `mode: "simulated"`.
+**That publish reaches the real ad account for every company** — LinkedIn writes are generally available, with no per-company flag and no simulated mode to turn on. Discarding the chat before it completes is what undoes a staged change.
 
 ```bash
 # Chain creates via li_temp_* refs — group → campaign → creative in one chat

package/dist/cli.js

@@ -2477,7 +2477,7 @@ var CAPABILITY_SURFACE_SPECS = {
     label: "Google Ads",
     provider: "google-ads",
     resourceNoun: "ad account",
-    writePath: "staged-gated",
+    writePath: "staged-live",
     writeScopes: ["https://www.googleapis.com/auth/adwords"],
     commands: "baker ads google"
   },
@@ -2486,7 +2486,7 @@ var CAPABILITY_SURFACE_SPECS = {
     label: "Meta Ads",
     provider: "meta",
     resourceNoun: "ad account",
-    writePath: "staged-gated",
+    writePath: "staged-live",
     writeScopes: ["ads_management"],
     commands: "baker ads meta"
   },
@@ -2495,7 +2495,7 @@ var CAPABILITY_SURFACE_SPECS = {
     label: "LinkedIn Ads",
     provider: "linkedin",
     resourceNoun: "ad account",
-    writePath: "staged-gated",
+    writePath: "staged-live",
     writeScopes: ["rw_ads"],
     commands: "baker ads linkedin"
   },
@@ -2575,7 +2575,7 @@ var capabilityLimitViewSchema = z6.object({
   cause: z6.enum(["not_built", "provider_forbids", "no_permission"]),
   detail: z6.string()
 });
-var capabilityWriteModeSchema = z6.enum(["live", "simulated", "applies-at-publish", "none"]);
+var capabilityWriteModeSchema = z6.enum(["live", "applies-at-publish", "none"]);
 var capabilitySurfaceReportSchema = z6.object({
   surface: capabilitySurfaceSchema,
   label: z6.string(),
@@ -12525,7 +12525,7 @@ registerSchema({
 });
 registerSchema({
   command: "ads.linkedin.draft.list",
-  description: "Show every LinkedIn write op staged in this chat: ref, summary, dependencies, warnings, mode (simulated = publish will NOT hit LinkedIn), and post-publish results (applied/simulated/failed/skipped). Ops are invisible to the read commands until publish \u2014 check here before finishing.",
+  description: "Show every LinkedIn write op staged in this chat: ref, summary, dependencies, warnings, and post-publish results. Ops are invisible to the read commands until publish, and publishing reaches the real ad account \u2014 check here before finishing.",
   args: {
     json: {
       type: "boolean",
@@ -15270,7 +15270,7 @@ Performance \u2014 the workhorse (3 axes):
 
 Staged writes (NEVER hit LinkedIn directly \u2014 ops stage on this chat's draft,
 show in the dashboard as pending LinkedIn changes, and apply when the chat is
-published; if the company's LinkedIn-write flag is off the publish is simulated):
+published, at which point they reach the real ad account):
   baker ads linkedin campaign-groups create|update|pause|resume|duplicate
   baker ads linkedin campaigns create|update|pause|resume|archive|duplicate
   baker ads linkedin creatives create|update|pause|resume|duplicate
@@ -17260,7 +17260,7 @@ async function listDraft2(chat) {
 var listCommand9 = defineCommand62({
   meta: {
     name: "list",
-    description: "Show every Meta write op staged in this chat, its mode (simulated = publish will NOT hit Meta), dependencies, and post-publish results. Example: baker ads meta draft"
+    description: "Show every Meta write op staged in this chat, its dependencies, and post-publish results. Publishing reaches the real ad account, so review this before you finish. Example: baker ads meta draft"
   },
   args: { chat: CHAT_READ_ARG },
   run: async ({ args }) => {
@@ -26535,7 +26535,7 @@ Full guide: __tooling__/docs/tools/baker/canvas.md`
 import { defineCommand as defineCommand100 } from "citty";
 registerSchema({
   command: "capabilities",
-  description: "Start here, before promising the user anything on an ad platform, in Analytics, or in Tag Manager. Answers three questions in one call: what is connected and with what access, whether writes are LIVE or SIMULATED for this company, and what CANNOT be done here and why. Run it with no arguments for every surface; name one surface to also get the exact fields every change on it accepts.",
+  description: "Start here, before promising the user anything on an ad platform, in Analytics, or in Tag Manager. Answers three questions in one call: what is connected and with what access, what a write on each surface actually does when it lands, and what CANNOT be done here and why. Run it with no arguments for every surface; name one surface to also get the exact fields every change on it accepts.",
   args: {
     surface: {
       type: "positional",
@@ -26552,12 +26552,6 @@ registerSchema({
 });
 function capabilityHints(surfaces) {
   const hints = [];
-  const simulated = surfaces.filter((surface) => surface.writeMode === "simulated");
-  if (simulated.length > 0) {
-    hints.push(
-      `SIMULATED: ${simulated.map((s) => s.label).join(", ")} \u2014 staging and publishing complete in full and nothing reaches the platform. Do the work, but never tell the user it is live.`
-    );
-  }
   const immediate = surfaces.filter((surface) => surface.writeMode === "applies-at-publish");
   if (immediate.length > 0) {
     hints.push(
@@ -26586,7 +26580,7 @@ var runCapabilities = defineCommand100({
     name: "capabilities",
     description: `What Baker can and cannot do for this company, before any work starts.
 
-Reports, per surface: what is connected and with what access, whether writes are live or simulated, the entities that can be changed, and \u2014 the part nothing else tells you \u2014 what cannot be changed and why.
+Reports, per surface: what is connected and with what access, what a write there does when it lands, the entities that can be changed, and \u2014 the part nothing else tells you \u2014 what cannot be changed and why.
 
 Examples:
   baker capabilities