@koda-sl/baker-cli 0.471.0 → 0.472.0-dev.607524e67

package/README.md

@@ -128,6 +128,19 @@ envelope to narrow; without it a note on stderr says the flag changed nothing. A
 that prints its result beside `ok` rather than under `data` (`canvas validate`,
 `canvas critique`) comes back whole, with a hint saying `--fields` was not applied.
 
+### Reading another company: `--company <id>`
+
+Only an organization's workspace (where its Reports across every company are built) may name a company. Any read takes `--company <id>` and runs as that company of the same organization; a write, stage or generate naming a company is refused, and so is any credential of an ordinary company. The ids come from:
+
+```bash
+baker organization companies     # every company: id, name, domain, timezone, suspended, connected platforms
+baker organization pull          # what each company made, as published, into ~/companies/<company>/ (read-only) + INDEX.md
+```
+
+`baker organization pull [--company <id>] [--dir <path>] [--force]` downloads each company's knowledge, landing pages, Forms, brand, documents, custom agents and checks and Reports, as published, one read-only folder per company, and writes `INDEX.md`. A second run only fetches companies that published since.
+
+On the organization workspace's Runtime (`BAKER_WORKSPACE_KIND=organization`) the CLI offers only reads, plus research and judgment run as the workspace itself (not `research customers` or `winning-ads fit`, which work on one company's own workspace); any other command is left out of `--help` and `baker schema` and refused before it is sent. Everywhere else the `organization` family is left out of help.
+
 ### Fresh reads: `--no-cache`
 
 Every command that caches takes `--no-cache`, and it skips **both** cache layers — the
@@ -1527,11 +1540,8 @@ baker analytics sources --map --source <id> --field email={{contact.email}} --fi
 baker analytics sources --create-hubspot --property lifecyclestage --value customer   # an event HubSpot keeps for Baker each time the property changes
 baker analytics sources --create-hubspot --property deal_value --operator greaterThan --value 1000   # any condition a Form's filter can say
 baker analytics sources --map --source <id> --field email={{work_email}} --field value={{deal_value}} --field currency=EUR   # repoint a HubSpot read
-baker analytics sources --create-activecampaign --events subscribe,deal_update   # ActiveCampaign's webhook sends these; each is an activecampaign.<event>
 ```
 
-**ActiveCampaign events.** `--create-activecampaign [--events …] [--name …] [--account <id>]` makes a source that ActiveCampaign's own webhook sends to — set up on the account when the chat is published (at once outside a chat), deleted when the source is removed. Each arrival is an event named `activecampaign.<event>` (`activecampaign.subscribe`, `activecampaign.deal_update`, …), about its contact, with the rest of the payload as `properties.*` — the name a scheduled agent on `event.received` is narrowed to.
-
 **Sources: where events reach Baker from a server.** Measure → Sources is three built-in doors — the Baker landings, the website tag, and **the client's own server** — plus the connections Baker reads (HubSpot today). `--server` prints the server's one address: made once, the same for ever, `counting` at once, Baker's own format (`sending-events` is the contract; `X-Baker-Mode: test` rehearses). A HubSpot event is a trigger in HubSpot's own words, kept by HubSpot's journal each time the property changes and counted within a minute. `--create --name <tool>` still makes an address for a tool that cannot be told what to send — its first send is a masked sample counted as nothing until `--map` confirms the rows — but the dashboard no longer offers those; a tool worth reading is a connection, requested from the Sources page. Each `--field` is a **template**: text with `{{path}}` mentions, one thing per mention (`--field currency=EUR` types a value, `--field first_name="{{who.first}} {{who.last}}"` joins two; there is no `{{a|b}}` fallback); a bare path is read as its mention when the sample has it. From then on every arrival is an ordinary event carrying `baker_source: <name>`, listed by `feed --source <name>`, and `--pause`, `--resume` and `--remove` are by `--source <id>`.
 
 **`--preview` then `--create-hubspot --property <name> [--operator <op>] --value <value>… [--name <name>] [--field <field>=<template>…] [--amount-property <n> --currency <c>]`: a HubSpot event.** HubSpot keeps each change to the property for Baker, filtered to the condition — on any plan, nothing to set up in HubSpot, an account of any size — and every contact whose new value satisfies the condition is one event, within a minute, named after the source (default: the trigger's words). The condition is any a Form's filter can say, by the property's kind: `is` / `isNot` (a dropdown, `--value` repeated for several), `contains` / `startsWith` / `endsWith` (text), `greaterThan` / `lessThanOrEqual` … (numbers), `isAfter` / `isBetween` (dates, `YYYY-MM-DD`), `isEmpty` / `isNotEmpty` (any); `--operator` is `is` when unsaid. Names, kinds and operators come from `baker hubspot contacts properties` and row properties from `baker hubspot contacts fields`; `--preview --property … [--operator …] --value … [--field …] [--contact <id or email>]` says how many contacts satisfy it today (NOT counted — only contacts that come to satisfy it from now on are) and returns `preview.record`, the one most recently there or the one asked for, to check every row against before making anything. `--set-trigger --source <id> --property … [--operator …] --value …` changes what an event watches later: the rows stay and `countingSince` moves to now. The connection must be allowed to read contacts, and a refusal names the reconnect. `counting` at once, no URL; the source carries `hubspot { property, propertyLabel, kind, operator, values, valueLabels }`, `countingSince`, `listening` (whether HubSpot has been told to keep its changes: `listening`, `not_configured` or `failed`, with a `detail`), `lastError` and `mapping` — the same field → template table as an address, over the contact's properties plus `{{id}}`, defaulting to HubSpot's standard ones (email, phone, the contact id, name, address, `hs_google_click_id`, `hs_facebook_click_id`); a `--field` row at creation replaces the default it names, `--map --field` replaces the whole set later, and `--amount-property … --currency …` is the short spelling for the `value` and `currency` rows. `--field properties.<name>=<template>` adds an extra property of the event (`--field properties.plan={{plan_tier}}`): it breaks the event down on Measure → Events and a send reads it back as `{{properties.<name>}}`. A deal is watched the same way with `--object deal`, and a lead with `--object lead` (`baker hubspot leads properties|fields`) — where HubSpot records qualification and disqualification as the lead's stage. A deal's or a lead's event is about its contacts (`--contacts every|first`), read as `{{contact.<name>}}`; a lead has no amount. Leads need Sales Hub Professional or Enterprise. Where the event is sent on (Meta, Google Ads…) is `sends`, edited on the event's own card on the Sources page.
@@ -1861,38 +1871,6 @@ baker ga4 draft clear
 
 ---
 
-### ActiveCampaign reads (`baker activecampaign`)
-
-Read the connected ActiveCampaign account live; nothing is stored and nothing in ActiveCampaign changes.
-
-```bash
-baker activecampaign account                                   # contacts, site tracking on/off + tracking account id, allowed domains, event tracking
-baker activecampaign campaigns [--status completed] [--since 2026-09-01] [--limit 20]   # email reports, most recently sent first
-baker activecampaign automations [--active-only]               # on/off, entered/exited, what starts each one
-baker activecampaign contacts [--id <contact id> | --email a@b.com | --tag <id|name> | --list <id|name> | --search <text>] [--limit 20]
-baker activecampaign deals [--pipeline <id|title>] [--stage <id|title>] [--status open|won|lost] [--owner <id|username|email>]
-baker activecampaign pipelines | lists | tags [--search <text>] | fields | users
-```
-
-A contact looked up by `--id` or `--email` also carries its `tags` and its `activity`: custom events, page visits, campaign emails sent, opened and clicked, automation runs and list subscriptions. Campaign rows carry `sends`, `opens`, `uniqueOpens`, `clicks`, `uniqueClicks`, `unsubscribes`, `hardBounces`, `softBounces` and `rates` (`open`, `click`, `unsubscribe` and `bounce` as shares of sends; `clickToOpen` as unique clicks over unique opens; `null` before anything is sent). Deal values are in the currency's major units, and `totals` sums every matching deal per currency. Every command takes `--account <id>` when the company has more than one ActiveCampaign connection, and `--full` adds each row's untouched ActiveCampaign payload as `raw`. Nothing connected answers `NO_ACTIVECAMPAIGN_CONNECTION`, a key ActiveCampaign stopped accepting `ACTIVECAMPAIGN_RECONNECT_REQUIRED` — both with a `request_connection` fix.
-
-### ActiveCampaign changes (`baker activecampaign stage` / `unstage` / `drafts`)
-
-Stage a custom contact field, list, tag or deal pipeline on the connected ActiveCampaign account. Nothing changes in ActiveCampaign until the chat is published; then each change is created — or, when the account already has it (a field by its personalization tag, the rest by name), reused rather than duplicated.
-
-```bash
-baker activecampaign stage field --utm                                   # UTM_SOURCE, UTM_MEDIUM, UTM_CAMPAIGN, UTM_CONTENT, UTM_TERM
-baker activecampaign stage field --title "Plan" --type dropdown --options "Basic,Pro"
-baker activecampaign stage list --name "Webinar sign-ups"
-baker activecampaign stage tag --name "hot-lead"
-baker activecampaign stage pipeline --title "Inbound" --stages "New lead,Qualified,Won" --currency usd
-baker activecampaign drafts [--chat <id>]                                # what is staged; after Publish, what happened to each
-baker activecampaign unstage <ref|name|perstag>                          # drop one staged change
-baker activecampaign unstage --all                                       # drop every staged change
-```
-
-A field is put on every list. Field types: `text`, `textarea`, `date`, `datetime`, `dropdown`, `listbox`, `radio`, `checkbox`, `hidden`; `dropdown`, `listbox`, `radio` and `checkbox` need `--options`. A new pipeline gets exactly `--stages`; an existing one only gains the stages it lacks. Every `stage` takes `--account <id>` when the company has more than one ActiveCampaign connection.
-
 ### Google Search Console (`baker gsc`)
 
 GSC commands for PPC-SEO arbitrage, brand halo analysis, and negative keyword discovery.
@@ -3916,14 +3894,13 @@ baker flows options calendly                        # what a step/destination ca
 baker flows connect contact --node book --resource <id>          # fill a Calendly/SavvyCal/GoHighLevel step yourself
 baker flows connect contact --side-effect se-gsheet-1 --resource <spreadsheetId>   # a sheet Baker can reach (--tab to pick the tab)
 baker flows connect contact --side-effect se-gsheet-1 --new-sheet "Contact leads" --columns "Name,Email"   # create one and wire it
-baker flows connect contact --side-effect se-pipedrive-1         # Pipedrive / GoHighLevel / ActiveCampaign contact: the account is the destination
+baker flows connect contact --side-effect se-pipedrive-1         # Pipedrive / GoHighLevel contact: the account is the destination
 baker flows connect contact --side-effect se-email-1 --email "ana@x.com, luis@x.com" --subject "New lead — Contact"   # an email destination: the agent states it, never a card
 baker flows connect contact --side-effect se-httpWebhook-1 --url https://hooks.example.com/lead   # a webhook that needs no token
 baker flows connect contact --all --type googleSpreadsheet --same-as madrid:se-gsheet-1   # copy another Form's destination
 baker flows map contact --from map.json --write     # a whole mapping at once — past ~3 fields, use this
 baker flows map contact --map A=nombre --write      # one or two fields
 baker flows map contact --hubspot-form <guid> --from map.json --write   # HubSpot: field types read off the form
-baker flows map contact --map email=email --map 'tags="withbaker-"+tracking:page_path' --write   # ActiveCampaign: fields read off the account; tag each lead with its page
 baker flows map contact --side-effect <id> --hubspot-form <guid> --prune-missing --write   # drop dead mappings
 baker flows map contact --from map.json --replace --write   # the slot becomes exactly this; drops everything not named
 baker flows normalize contact --write              # repairs a nulled optional; runs pre-commit anyway
@@ -3933,13 +3910,13 @@ Notes:
 
 - **`schema` takes the kind as an argument because `hubspot` is both** — a node type (embeds a form on the page) and a side-effect type (fires a behavioural event). They are different things with one name.
 - **`connect` wires a HubSpot form without asking the user.** When HubSpot is connected and the agent knows which form is meant, `baker flows connect <slug> --hubspot-form <formId> [--side-effect <id>]` attaches the account and the form to a `hubspotForm` side effect (`--all`: every one in the Form still missing it, never repointing one already wired) — the same thing the chat card writes, sealed by Baker so the config never passes through the agent. It refuses a form with spam prevention (captcha) on, and returns `destination.formGuid` for `map --hubspot-form`. The card (`request_flow_input`) stays for an unconnected account or an ambiguous choice.
-- **`options` + `connect` do the same for every other connected platform.** `baker flows options <kind>` lists what the connected account holds (Calendly events, SavvyCal links, GoHighLevel calendars and forms, the Google spreadsheets Baker can reach); `connect --node|--side-effect <id> --resource <id>` writes exactly what the card would. Pipedrive, a GoHighLevel contact and an ActiveCampaign contact take no resource. `--new-sheet` creates a spreadsheet in the connected Google account (Google only lets Baker reach sheets it created or the user chose), `--same-as <slug>:<id>` copies another Form's wired destination, `--all --type <kind>` fills every unwired one of a kind. Nothing connected answers `NOT_CONNECTED` with the `request_connection` fix; several accounts connected need `--account <id>`.
+- **`options` + `connect` do the same for every other connected platform.** `baker flows options <kind>` lists what the connected account holds (Calendly events, SavvyCal links, GoHighLevel calendars and forms, the Google spreadsheets Baker can reach); `connect --node|--side-effect <id> --resource <id>` writes exactly what the card would. Pipedrive and a GoHighLevel contact take no resource. `--new-sheet` creates a spreadsheet in the connected Google account (Google only lets Baker reach sheets it created or the user chose), `--same-as <slug>:<id>` copies another Form's wired destination, `--all --type <kind>` fills every unwired one of a kind. Nothing connected answers `NOT_CONNECTED` with the `request_connection` fix; several accounts connected need `--account <id>`.
 - **`--email` / `--url` replace a destination whole, so they leave alone what only the user can set.** `--all --email` passes over an email that replies to the visitor's own answer (and says so in its hints); naming one is refused. A webhook that sends a credential keeps its address until the user re-enters both through `request_flow_input`. Unreadable settings are also left alone by default. For one unreadable email, `--replace-unreadable --email <complete list> --subject <text>` replaces the old setup when the user intends replacement, without revealing it. Never use this to add to an unknown recipient list; it cannot override `--all`, a known visitor reply, or a webhook. `flows show` reads back only destinations sealed for this company.
 - **Configure the destination before you map.** `columnMapping`/`fieldMapping` describe a *specific* destination — sheet columns, a portal's field names — that only `connect` or `request_flow_input` can set, and both return it. A mapping written first is valid JSON that ships and drops every submission; `verify` blocks the half-wired result.
-- **`map` reads the record shape off the side effect's type.** One property name, four record shapes: a Sheet is addressed by column letter, HubSpot by property name, Pipedrive and GoHighLevel by field key, ActiveCampaign by field key (`email`, `firstName`, a custom field's id, `tags`, `lists`, `automations`, `note`, or a qualified `deal.title` / `account.name` / `event.name`), Crmble by field id. That is why there is no `--key`, and why `--entity` and `--custom`/`--standard` are required rather than defaulted for Pipedrive and GoHighLevel.
+- **`map` reads the record shape off the side effect's type.** One property name, four record shapes: a Sheet is addressed by column letter, HubSpot by property name, Pipedrive and GoHighLevel by field key, Crmble by field id. That is why there is no `--key`, and why `--entity` and `--custom`/`--standard` are required rather than defaulted.
 - **A mapping is usually eight to fifteen fields, so `--from` is the main door.** It takes `{ "map": { "<destField>": "<value>" } }` from a file or stdin; `--map` flags are for one or two. Both produce identical output.
 - **Most CRM fields are not fed by a form field.** The value grammar is a bare form field (`nombre`), `field:Step.name` when two steps share a name, `tracking:utm_source`, `global:Name`, `code:exposed_value`, a `"literal"`, or any of those joined with `+`. Tracking names are validated against the engine's own `TRACKING_FIELD_IDS`, read out of the workspace rather than copied — attribution columns are the most common CRM mapping there is, and they were unexpressible before.
-- **A CRM mapping's field type is derived from the destination, never defaulted.** Every CRM record types `fieldType` as required, and it is the account's answer, not the agent's — HubSpot builds its submission key as `<objectTypeId>.<fieldType>.<fieldName>`, so a wrong type on a date property skips the `YYYY-MM-DD` coercion and the value is dropped. `--hubspot-form <formGuid>` (or `"hubspotForm"` in the mapping file) reads every property's type and object type off the form, so nothing has to state one. An `activeCampaignContact` mapping reads the connected ActiveCampaign account's field list on every call — no flag — so its types (`standard`, `custom`, `tags`, `lists`, `automations`, `deal`, `account`, `note`, `event`) are derived too, a custom field may be named by its id, personalization tag or label (stored as the id) — or as `custom.<TAG>` for one that is only staged so far, resolved when each lead is sent — and a name the account does not have is refused with the list of the ones it does. Its `tags`, `lists` and `automations` mappings are comma-separated names or ids that may mix text and variables, e.g. `tags="withbaker-"+tracking:page_path`; `deal.title` or `deal.pipeline` creates a deal (`deal.value` in major units, `deal.stage` / `deal.owner` by name or id), `account.name` finds or creates the lead's company, `note` leaves a note and `event.name` records an event (it needs the account's event key on the connection). The answer's `hints` name a list, automation, pipeline, stage or user the account does not have, a deal nothing creates, and an event with no event key. Where a destination cannot be read, put the type on the LEFT — `c0ffee:varchar=email` — which leaves `:` on the right for the value kinds. A mapping with no type from either route is refused, never written without one.
+- **A CRM mapping's field type is derived from the destination, never defaulted.** Every CRM record types `fieldType` as required, and it is the account's answer, not the agent's — HubSpot builds its submission key as `<objectTypeId>.<fieldType>.<fieldName>`, so a wrong type on a date property skips the `YYYY-MM-DD` coercion and the value is dropped. `--hubspot-form <formGuid>` (or `"hubspotForm"` in the mapping file) reads every property's type and object type off the form, so nothing has to state one. Where a destination cannot be read, put the type on the LEFT — `c0ffee:varchar=email` — which leaves `:` on the right for the value kinds. A mapping with no type from either route is refused, never written without one.
 - **`email` maps like anything else**, into `body.fields`, while `body.format` is `"json"`. A `"body"`-format email is one written message with no keys to address, and `map` refuses it rather than reshaping the body.
 - **A Form can look finished and be losing every lead.** HubSpot refuses a submission that names a property it does not have — the whole submission, not the field — and the visitor still reaches the thank-you screen. Baker re-checks each Form's destination and `baker flows show <slug>` reports what it found: `data.drift[]` carries **one entry per drifted destination** — a Form with two HubSpot side effects has two mappings, two form ids and two repairs — each with the severity, a sentence naming the fields, the side-effect id and that destination's HubSpot form id; the hints carry one repair command per entry. `drift: null` means the check could not be made and is not the same answer as `[]`.
 - **`--prune-missing` is the repair; `--replace` is not.** With `--side-effect <id>` and `--hubspot-form <guid>`, `--prune-missing` drops exactly the mappings whose destination field is absent from that form's live field list, names each one in `dropped`, and leaves every other mapping alone. It needs no `--map` and runs on its own. `--replace` drops everything the call does not name, so using it to remove three dead mappings means first restating the ten good ones correctly.
@@ -3949,7 +3926,7 @@ Notes:
 - **`normalize` exists so authoring a Form does not require remembering an exception.** `oauthProviderId` is an optional `string`, so a `null` there fails typecheck one build later — it is repaired and staged instead of rejected.
 
 - **Secrets never travel through this CLI or the chat.** `show` reports only whether each field is configured (`[set]`/`[missing]`, `[connected]`/`[needs connection]`, selected/not selected) — never a value. Configured secrets appear only as `[configured]` ciphertext markers.
-- Confidential side-effect types: `httpWebhook`, `zapier`, `crmble` (typed credentials); `pipedrive`, `googleSpreadsheet`, `hubspotForm`, `goHighlevelContact`, `activeCampaignContact` (connected account + resource); `email`. Widget node types needing a resource pick: `calendly`, `savvycal`, `hubspot`, `hubspotMeeting`, `highlevel`, `highlevelForm`.
+- Confidential side-effect types: `httpWebhook`, `zapier`, `crmble` (typed credentials); `pipedrive`, `googleSpreadsheet`, `hubspotForm`, `goHighlevelContact` (OAuth connection + resource); `email`. Widget node types needing a resource pick: `calendly`, `savvycal`, `hubspot`, `hubspotMeeting`, `highlevel`, `highlevelForm`.
 - `request_flow_input` changes stage on the chat's branch and apply when the chat is published; discarding the chat drops them.
 
 ### Action Items (`baker actions`)

package/dist/account-K34PAC77.js

@@ -0,0 +1,49 @@
+import {
+  handleMetaError,
+  resolveAccountIdArg
+} from "./chunk-XKJNDYD3.js";
+import {
+  writeAdsJson
+} from "./chunk-G3TL63X5.js";
+import {
+  NO_CACHE_ARG
+} from "./chunk-M5G6QOR4.js";
+import {
+  apiGet
+} from "./chunk-AGIX3HNF.js";
+import "./chunk-NY3LDKO4.js";
+import "./chunk-PBI5PQEZ.js";
+import "./chunk-MV3PVKTU.js";
+import "./chunk-YQSBHWOI.js";
+
+// src/commands/ads/meta/account.ts
+import { defineCommand } from "citty";
+var accountCommand = defineCommand({
+  meta: {
+    name: "account",
+    description: `Show single Meta ad account detail (currency, timezone, balance, business).
+
+Examples:
+  baker ads meta account --account-id act_123
+  BAKER_META_AD_ACCOUNT_ID=act_123 baker ads meta account`
+  },
+  args: {
+    "account-id": { type: "string", description: "Meta ad account ID (act_...)" },
+    "no-cache": NO_CACHE_ARG
+  },
+  run: async ({ args }) => {
+    const accountId = resolveAccountIdArg(args);
+    try {
+      const params = { "account-id": accountId };
+      if (args["no-cache"]) params["skip-cache"] = "true";
+      const data = await apiGet("/api/ads/meta/account", params);
+      writeAdsJson({ ok: true, data });
+    } catch (err) {
+      handleMetaError(err);
+    }
+  }
+});
+export {
+  accountCommand
+};
+//# sourceMappingURL=account-K34PAC77.js.map

package/dist/account-KKYBE6KV.js

@@ -0,0 +1,80 @@
+import {
+  CHATGPT_ADS_REFERENCE,
+  runChatgptRead
+} from "./chunk-LA3P65JZ.js";
+import "./chunk-G3TL63X5.js";
+import {
+  apiGet
+} from "./chunk-AGIX3HNF.js";
+import "./chunk-NY3LDKO4.js";
+import "./chunk-PBI5PQEZ.js";
+import {
+  registerSchema
+} from "./chunk-MV3PVKTU.js";
+import "./chunk-YQSBHWOI.js";
+
+// src/commands/ads/chatgpt/account.ts
+import { defineCommand } from "citty";
+registerSchema({
+  command: "ads.chatgpt.account",
+  description: "The connected ChatGPT Ads account: name, currency, timezone, status, and the brand and account reviews that decide whether anything in it can serve.",
+  args: {
+    full: { type: "boolean", description: "Return ChatGPT Ads' own account object", required: false }
+  }
+});
+function accountHints(account) {
+  const hints = [];
+  if (account.brandReview.status !== "approved") {
+    const reason = account.brandReview.reason ? ` (${account.brandReview.reason})` : "";
+    hints.push(
+      `Brand review is ${account.brandReview.status}${reason}: nothing in this account serves until it is approved. Fix it in ChatGPT Ads Manager before changing campaigns.`
+    );
+  }
+  if (account.accountReview && account.accountReview.status !== "approved") {
+    hints.push(`A separate account review is ${account.accountReview.status}; delivery can wait on it too.`);
+  }
+  if (account.status === "paused") {
+    hints.push("The whole account is paused, so no campaign in it serves whatever its own status says.");
+  }
+  return hints;
+}
+var SHOW_ARGS = {
+  full: { type: "boolean", description: "Return ChatGPT Ads' own account object", required: false }
+};
+var accountShowCommand = defineCommand({
+  meta: {
+    name: "show",
+    description: "The connected ChatGPT Ads account. Example: baker ads chatgpt account"
+  },
+  args: SHOW_ARGS,
+  run: async ({ args }) => {
+    await runChatgptRead(
+      CHATGPT_ADS_REFERENCE.account,
+      () => apiGet("/api/ads/chatgpt/account", args.full ? { full: "true" } : void 0),
+      (account) => args.full ? [] : accountHints(account)
+    );
+  }
+});
+var accountCommand = defineCommand({
+  meta: {
+    name: "account",
+    description: `The connected ChatGPT Ads account. Start here: currency and timezone for every figure, and whether reviews let anything serve.
+
+Examples:
+  baker ads chatgpt account
+  baker ads chatgpt account --full
+  baker ads chatgpt account update --favicon-url https://example.com/icon.png   \u2014 staged; applies on publish`
+  },
+  subCommands: {
+    show: accountShowCommand,
+    update: () => import("./account-writes-FVRHSUYP.js").then((m) => m.accountUpdateCommand)
+  },
+  // A parent must never declare `run`: citty falls through to it after the matched subcommand.
+  args: SHOW_ARGS,
+  default: "show"
+});
+export {
+  accountCommand,
+  accountHints
+};
+//# sourceMappingURL=account-KKYBE6KV.js.map

package/dist/account-NKEMDY2U.js

@@ -0,0 +1,79 @@
+import {
+  csvOrJson,
+  handleLinkedinError,
+  resolveAccountIdArg
+} from "./chunk-NHFX7CBM.js";
+import {
+  writeAdsJson,
+  writeAdsOutput
+} from "./chunk-G3TL63X5.js";
+import {
+  NO_CACHE_ARG
+} from "./chunk-M5G6QOR4.js";
+import "./chunk-RPJYEJDQ.js";
+import "./chunk-GXDLWBOY.js";
+import "./chunk-GIWHHCD6.js";
+import "./chunk-XQIOCIDO.js";
+import "./chunk-I2DNBEV6.js";
+import {
+  apiGet
+} from "./chunk-AGIX3HNF.js";
+import "./chunk-NY3LDKO4.js";
+import "./chunk-PBI5PQEZ.js";
+import "./chunk-MV3PVKTU.js";
+import "./chunk-YQSBHWOI.js";
+
+// src/commands/ads/linkedin/account.ts
+import { defineCommand } from "citty";
+var accountDetailCommand = defineCommand({
+  meta: {
+    name: "detail",
+    description: `Single LinkedIn ad account detail (currency, status, type).
+
+Examples:
+  baker ads linkedin account --account-id 503001492
+  baker ads linkedin account --account-urn urn:li:sponsoredAccount:503001492 --output md`
+  },
+  args: {
+    "account-id": { type: "string", description: "Numeric account ID or urn:li:sponsoredAccount:N" },
+    "account-urn": { type: "string", description: "Alias for --account-id" },
+    "no-cache": NO_CACHE_ARG,
+    output: { type: "string", description: "json|csv|jsonl|md", default: "json" }
+  },
+  run: async ({ args }) => {
+    const accountId = resolveAccountIdArg(args);
+    try {
+      const params = { "account-id": accountId };
+      if (args["no-cache"]) params["skip-cache"] = "true";
+      const data = await apiGet("/api/ads/linkedin/account", params);
+      const fmt = csvOrJson(args);
+      if (fmt !== "json") {
+        writeAdsOutput([data], fmt);
+        return;
+      }
+      writeAdsJson({ ok: true, data });
+    } catch (err) {
+      handleLinkedinError(err);
+    }
+  }
+});
+var accountCommand = defineCommand({
+  meta: {
+    name: "account",
+    description: `LinkedIn ad account: its detail, and the settings that apply across every ad set in it.
+
+Examples:
+  baker ads linkedin account --account-id 503001492                          \u2014 currency, status, type
+  baker ads linkedin account url-params --param utm_source=linkedin          \u2014 UTMs for every ad in the account`
+  },
+  subCommands: {
+    detail: accountDetailCommand,
+    "url-params": () => import("./write-commands-D5X6N7Q4.js").then((m) => m.accountUrlParamsCommand)
+  },
+  args: accountDetailCommand.args,
+  default: "detail"
+});
+export {
+  accountCommand
+};
+//# sourceMappingURL=account-NKEMDY2U.js.map

package/dist/account-reads-6IFA5UYY.js

@@ -0,0 +1,218 @@
+import {
+  exitWithServiceReadError
+} from "./chunk-EBMS5SW3.js";
+import {
+  failWriteValidation,
+  listFlag,
+  requireCustomerId
+} from "./chunk-EXXCDFEM.js";
+import "./chunk-ERSX3MKH.js";
+import "./chunk-P6STUJ22.js";
+import "./chunk-4NZ47VXO.js";
+import "./chunk-D5FY4FAK.js";
+import "./chunk-5BMPVG43.js";
+import "./chunk-SEPPFM5S.js";
+import {
+  getManagerIdForCustomer,
+  writeJsonEnvelope
+} from "./chunk-G3TL63X5.js";
+import "./chunk-KOMLRHVH.js";
+import "./chunk-M22GYDBE.js";
+import "./chunk-JVRA7EGL.js";
+import "./chunk-3BLSLGVH.js";
+import "./chunk-B3C5RXM4.js";
+import "./chunk-KLVHEGSW.js";
+import "./chunk-XQIOCIDO.js";
+import "./chunk-I2DNBEV6.js";
+import {
+  apiPost
+} from "./chunk-AGIX3HNF.js";
+import "./chunk-NY3LDKO4.js";
+import "./chunk-PBI5PQEZ.js";
+import {
+  registerSchema
+} from "./chunk-MV3PVKTU.js";
+import "./chunk-YQSBHWOI.js";
+
+// src/commands/ads/google/account-reads.ts
+import { defineCommand } from "citty";
+function register(command, description, args) {
+  registerSchema({
+    command,
+    description,
+    args: Object.fromEntries(
+      Object.entries(args).map(([name, arg]) => [
+        name,
+        { type: arg.type, description: arg.description, required: false }
+      ])
+    )
+  });
+}
+async function serviceRead(path, customerId, body) {
+  const managerId = getManagerIdForCustomer(customerId);
+  const { data } = await apiPost(path, {
+    customerId,
+    ...managerId ? { managerId } : {},
+    ...body
+  });
+  return data;
+}
+var CUSTOMER_ARG = {
+  "customer-id": { type: "string", description: "Google Ads customer ID (10 digits, no dashes)" }
+};
+var INVOICE_ARGS = {
+  ...CUSTOMER_ARG,
+  month: { type: "string", description: "Issue month, YYYY-MM (default: last month)" }
+};
+register(
+  "ads.google.invoices",
+  "List the invoices Google issued in one month (accounts on monthly invoicing only): id, dates, service period, subtotal/tax/total in micros, PDF link. Start here: `baker ads google invoices --customer-id 1234567890 --month 2026-09`. An account that pays automatically has no invoices \u2014 the error's fix says where its receipts are; carry on.",
+  INVOICE_ARGS
+);
+var invoicesCommand = defineCommand({
+  meta: {
+    name: "invoices",
+    description: `List one month's invoices (monthly-invoicing accounts only). Read-only.
+
+Example:
+  baker ads google invoices --customer-id 1234567890 --month 2026-09`
+  },
+  args: INVOICE_ARGS,
+  run: async ({ args }) => {
+    const customerId = requireCustomerId(args);
+    try {
+      const data = await serviceRead("/api/ads/google/invoices", customerId, {
+        ...args.month ? { month: args.month } : {}
+      });
+      const hints = data.invoices.length === 0 ? [`No invoice was issued in ${data.month}. Try the month before with --month.`] : [
+        "Amounts are micros in each invoice's currency_code (divide by 1,000,000). pdf_url needs the user's Google sign-in."
+      ];
+      writeJsonEnvelope({ ok: true, data, hints });
+    } catch (err) {
+      exitWithServiceReadError(err);
+    }
+  }
+});
+register(
+  "ads.google.identity-verification",
+  "Advertiser identity verification status: each program's status (PENDING_USER_ACTION, PENDING_REVIEW, SUCCESS, FAILURE), deadlines and the link where the user completes it. Start here: `baker ads google identity-verification --customer-id 1234567890`. Google only answers for accounts on monthly invoicing \u2014 otherwise the error's fix says where the user reads it; carry on.",
+  CUSTOMER_ARG
+);
+var identityVerificationCommand = defineCommand({
+  meta: {
+    name: "identity-verification",
+    description: `Advertiser identity verification status and deadlines. Read-only.
+
+Example:
+  baker ads google identity-verification --customer-id 1234567890`
+  },
+  args: CUSTOMER_ARG,
+  run: async ({ args }) => {
+    const customerId = requireCustomerId(args);
+    try {
+      const data = await serviceRead(
+        "/api/ads/google/identity-verification",
+        customerId,
+        {}
+      );
+      const pending = data.programs.filter((program) => program.status === "PENDING_USER_ACTION");
+      const hints = pending.length > 0 ? [
+        `Verification is waiting on the advertiser${pending[0]?.completion_deadline ? ` (deadline ${pending[0].completion_deadline})` : ""}: give the user the action_url \u2014 ads stop serving if it lapses.`
+      ] : [];
+      writeJsonEnvelope(hints.length > 0 ? { ok: true, data, hints } : { ok: true, data });
+    } catch (err) {
+      exitWithServiceReadError(err);
+    }
+  }
+});
+var PREVIEW_ARGS = {
+  ...CUSTOMER_ARG,
+  ads: {
+    type: "string",
+    description: "Comma-separated video ads of Video campaigns as {adGroupId}~{adId} (from `ads list`) \u2014 previewed live on YouTube"
+  },
+  "asset-groups": {
+    type: "string",
+    description: "Comma-separated Performance Max asset group ids (from `asset-groups list`) \u2014 previewed on Google's preview page"
+  }
+};
+register(
+  "ads.google.previews",
+  "Shareable preview links for Performance Max asset groups (Google's preview page) and video ads (live on YouTube) that already exist in the account \u2014 a link the user can open or forward. Start here: `baker ads google previews --customer-id 1234567890 --asset-groups 6743268912`. Returns { previews: [{ target, url, youtube_tv_url, expires_at }] }. Only video ads of Video campaigns can be previewed by ad (search, display and Demand Gen ads have no shareable preview); staged (unpublished) changes cannot be previewed.",
+  PREVIEW_ARGS
+);
+var previewsCommand = defineCommand({
+  meta: {
+    name: "previews",
+    description: `Shareable preview links for existing Performance Max asset groups and video ads. Read-only.
+
+Examples:
+  baker ads google previews --customer-id 1234567890 --asset-groups 6743268912
+  baker ads google previews --customer-id 1234567890 --ads 195752489650~826812181091   # a video ad, live on YouTube`
+  },
+  args: PREVIEW_ARGS,
+  run: async ({ args }) => {
+    const customerId = requireCustomerId(args);
+    const ads = listFlag(args.ads);
+    const assetGroups = listFlag(args["asset-groups"]);
+    if (!ads?.length && !assetGroups?.length) failWriteValidation("pass --ads and/or --asset-groups");
+    try {
+      const data = await serviceRead("/api/ads/google/previews", customerId, {
+        ...ads ? { ads } : {},
+        ...assetGroups ? { assetGroups } : {}
+      });
+      writeJsonEnvelope({
+        ok: true,
+        data,
+        hints: [
+          "Each link expires (expires_at). It shows what is live in the account now, not anything staged in this chat."
+        ]
+      });
+    } catch (err) {
+      exitWithServiceReadError(err);
+    }
+  }
+});
+var BRAND_ARGS = {
+  ...CUSTOMER_ARG,
+  prefix: { type: "string", description: "The start of the brand's name (at least 2 letters)" }
+};
+register(
+  "ads.google.brands",
+  "Find a brand's Google entity id \u2014 what a BRANDS list member names (`keyword-lists add --brand /g/\u2026`). Start here: `baker ads google brands --customer-id 1234567890 --prefix nike`. Several brands can share a name: pick by the URL. Read-only.",
+  BRAND_ARGS
+);
+var brandsCommand = defineCommand({
+  meta: {
+    name: "brands",
+    description: `Find brand entity ids for a brand list (BRANDS). Read-only.
+
+Example:
+  baker ads google brands --customer-id 1234567890 --prefix nike`
+  },
+  args: BRAND_ARGS,
+  run: async ({ args }) => {
+    const customerId = requireCustomerId(args);
+    if (typeof args.prefix !== "string" || args.prefix.trim().length < 2) {
+      failWriteValidation("--prefix needs at least the first 2 letters of the brand");
+    }
+    try {
+      const data = await serviceRead("/api/ads/google/brands", customerId, {
+        prefix: args.prefix
+      });
+      const hints = data.brands.length > 0 ? [
+        "Several brands can share a name \u2014 pick the one whose URL is the brand you mean, then `keyword-lists add --list-ref <BRANDS list> --brand <entity_id>`."
+      ] : ["No brand starts with that \u2014 try a shorter or different prefix."];
+      writeJsonEnvelope({ ok: true, data, hints });
+    } catch (err) {
+      exitWithServiceReadError(err);
+    }
+  }
+});
+export {
+  brandsCommand,
+  identityVerificationCommand,
+  invoicesCommand,
+  previewsCommand
+};
+//# sourceMappingURL=account-reads-6IFA5UYY.js.map

package/dist/account-writes-FVRHSUYP.js

@@ -0,0 +1,66 @@
+import {
+  compact,
+  schemaArgs,
+  stageChatgptOp
+} from "./chunk-5FDRGIIV.js";
+import {
+  CHATGPT_ADS_REFERENCE,
+  chatgptFailure
+} from "./chunk-LA3P65JZ.js";
+import {
+  writeJsonEnvelope
+} from "./chunk-G3TL63X5.js";
+import {
+  apiGet
+} from "./chunk-AGIX3HNF.js";
+import "./chunk-NY3LDKO4.js";
+import "./chunk-PBI5PQEZ.js";
+import {
+  registerSchema
+} from "./chunk-MV3PVKTU.js";
+import "./chunk-YQSBHWOI.js";
+
+// src/commands/ads/chatgpt/account-writes.ts
+import { defineCommand } from "citty";
+var REFERENCE = CHATGPT_ADS_REFERENCE.account;
+var UPDATE_ARGS = {
+  name: { type: "string", description: "The advertiser name shown on every card" },
+  "favicon-url": { type: "string", description: "https:// square icon, at least 128 \xD7 128 px" }
+};
+registerSchema({
+  command: "ads.chatgpt.account.update",
+  description: "Stage a change to the advertiser's brand name or icon. It applies when the chat is published and starts a new brand review; nothing in the account serves until it is approved.",
+  args: schemaArgs(UPDATE_ARGS)
+});
+var accountUpdateCommand = defineCommand({
+  meta: {
+    name: "update",
+    description: `Stage a change to the brand name or icon (applies when the chat is published).
+
+Examples:
+  baker ads chatgpt account update --favicon-url https://example.com/icon.png
+  baker ads chatgpt account update --name "GreenLeaf Energy"`
+  },
+  args: UPDATE_ARGS,
+  run: async ({ args }) => {
+    let account;
+    try {
+      account = await apiGet("/api/ads/chatgpt/account");
+    } catch (err) {
+      writeJsonEnvelope({ ...chatgptFailure(err, REFERENCE) });
+      process.exit(1);
+    }
+    await stageChatgptOp(
+      {
+        kind: "account.update",
+        target: account.id,
+        payload: compact({ name: args.name, faviconUrl: args["favicon-url"] })
+      },
+      REFERENCE
+    );
+  }
+});
+export {
+  accountUpdateCommand
+};
+//# sourceMappingURL=account-writes-FVRHSUYP.js.map