@koda-sl/baker-cli 0.455.0 → 0.456.0

package/README.md

@@ -221,10 +221,10 @@ baker ads google currency --customer-id 5904042878
 
 ### `baker ads google url-options`
 
-The UTM / tracking parameters in force on the account: the account-level Final URL Suffix and tracking template, plus every campaign that overrides them. Start here for any "add `utm_agency=…`" or agency-tag question.
+The UTM / tracking parameters in force on the account: the account-level Final URL Suffix and tracking template, plus every campaign, ad group and ad that overrides them. Start here for any "add `utm_agency=…`" or agency-tag question.
 
 ```bash
-baker ads google url-options --customer-id 1234567890          # overriding campaigns only
+baker ads google url-options --customer-id 1234567890          # overriding campaigns, ad groups and ads
 baker ads google url-options --customer-id 1234567890 --full   # every campaign read
 ```
 
@@ -235,15 +235,19 @@ Every value is a tagged union, never a bare string, so an unread level can never
   "ok": true,
   "data": {
     "account": { "final_url_suffix": { "state": "set", "value": "utm_source=google" } },
-    "campaigns": { "overriding": [], "omitted": 12 },
-    "levels_not_read": ["ad_group", "ad"]
+    "campaigns": { "overrides": [], "omitted": 12 },
+    "ad_groups": { "read": true, "overrides": [], "truncated": false },
+    "ads": { "read": true, "overrides": [], "truncated": false },
+    "levels_not_read": []
   }
 }
 ```
 
 `set` holds a value · `not_set` means Google carries none at that level · `not_read` means it was never observed. **Only `not_set` is a finding.**
 
-Writing it: `baker ads google campaigns update <id> --final-url-suffix "utm_source=google&utm_agency=baker"` stages a campaign-level override (it *replaces* the account value for that campaign, it does not merge). The **account** level is deliberately not stageable — Google writes it through `CustomerService`, outside the atomic publish batch, so it could not be published atomically nor reversed by discarding the chat. `--level account` stages nothing and returns a structured `error.fix` naming where to set it.
+Writing it: `baker ads google campaigns update <id> --final-url-suffix "utm_source=google&utm_agency=baker"` stages a campaign-level override (it *replaces* the account value for that campaign, it does not merge). The **account** level stages too: `baker ads google account update --customer-id … --final-url-suffix "utm_source=google&utm_agency=baker"` (or `campaigns update --level account --final-url-suffix …`, the same op) applies at publish with the rest of the draft; `""` clears it.
+
+**Account settings** — `baker ads google account update --customer-id …` stages the account's own settings: `--final-url-suffix`, `--tracking-template`, `--auto-tagging` / `--auto-tagging=false`, `--call-reporting`, `--call-conversions`, `--video-inventory EXPANDED|STANDARD|LIMITED`. One card per account (staging again amends it), shown before → after; a setting the account already holds is a no-op. Turning auto-tagging off stages with a warning (conversion tracking loses the gclid). The conversion action that counts calls is not writable through Google's API.
 
 ---
 
@@ -317,19 +321,19 @@ baker ads google query --list-presets
 
 Read it before interpreting any null. Field coverage is folded page by page on the `--out` path too, so the file summary reports it; `.resource_name` is never reported (the server strips it from every row).
 
-**A page is not the data set.** Without `--all`, a query returns one page capped by `--limit` (default 200, or the `LIMIT` in the statement, whichever is smaller). With `--all` every page is followed, but the statement's `LIMIT` still caps the read — and preflight adds one at `--limit` to any query that arrives without it, so `--all` on its own still stops at 200 rows. When the rows fill whichever cap is in force, or the API returns a cursor the run did not follow, the response carries a `TRUNCATED_RESULTS` warning:
+**A page is not the data set.** Every query is read a page at a time: without `--all` it returns one page of `--limit` rows (the preset's page size, else 200) and, when the account holds more, `pagination.cursor` — pass it back with `--cursor` (same query, same `--limit`) for the next page. `--all` follows every page until the account has no more rows; only a `LIMIT` written in the statement caps it. When the API returns a cursor the run did not follow, or the rows fill the statement's own `LIMIT`, the response carries a `TRUNCATED_RESULTS` warning:
 
 ```json
 {
   "ok": true,
   "warnings": [{ "code": "TRUNCATED_RESULTS", "message": "INCOMPLETE READ — ..." }],
-  "pagination": { "hasMore": true, "cursor": "eyJwYWdl..." },
+  "pagination": { "hasMore": true, "cursor": "skip:200.k3x9q2:" },
   "data": [...],
   "notice": "Read the \"warnings\" above before using these rows: TRUNCATED_RESULTS."
 }
 ```
 
-Never total or count from a response carrying it — re-run with `--all --limit 8192 --out data.csv` (one read returns at most 8,192 rows; split a bigger data set into narrower queries — a shorter date range or one campaign each) and check the re-run came back without the warning. A read that returns one row by construction — `FROM customer` with no segment selected, such as `--preset account-summary` — has no page to fill, so it never carries `TRUNCATED_RESULTS`, nor `CONVERSION_MIX`, since one account-wide row has no campaigns to total or compare. Warnings reach every output format, so no `--output` choice can hide one:
+Never total or count from a response carrying it — re-run with `--all --out data.csv` (it pages through every row, however many) and check the re-run came back without the warning. A read that returns one row by construction — `FROM customer` with no segment selected, such as `--preset account-summary` — has no page to fill, so it never carries `TRUNCATED_RESULTS`, nor `CONVERSION_MIX`, since one account-wide row has no campaigns to total or compare. Warnings reach every output format, so no `--output` choice can hide one:
 
 | `--output` | Where warnings land |
 |------------|---------------------|
@@ -370,9 +374,10 @@ The same lines also go to stderr. A read with nothing to report prints none of i
 | `--preset`      | Named query template (see presets below)                     |
 | `--date-range`  | Override preset date range: a Google literal (LAST_7_DAYS, LAST_30_DAYS, LAST_MONTH, etc.) or `BETWEEN 'YYYY-MM-DD' AND 'YYYY-MM-DD'` — there is no LAST_90_DAYS |
 | `--include-paused` | Include paused entities in preset results. Off by default: presets return only actually-serving entities (enabled campaign **and** ad group **and** ad). Google Ads has no single serving flag, so the whole chain must be `ENABLED` for an entity to serve. |
-| `--limit`       | Max rows per page (default 200, at most 8,192)               |
-| `--cursor`      | Pagination cursor from previous response                     |
-| `--all`         | Auto-paginate all results. Exhausts the pages, not the statement's `LIMIT` — pair it with a `LIMIT` in the statement above the expected row count (at most 8,192 — split bigger reads into narrower queries), and a read that still fills its cap is flagged `TRUNCATED_RESULTS` either way |
+| `--gaql`        | The GAQL statement as a flag, instead of the positional      |
+| `--limit`       | Rows per page (default: the preset's page size, else 200; at most 8,192). A page size, not a cap |
+| `--cursor`      | `pagination.cursor` from the previous page (same query, same `--limit`) |
+| `--all`         | Follow every page until the account has no more rows. Only a `LIMIT` written in the statement stops it early, and a read that fills that `LIMIT` is flagged `TRUNCATED_RESULTS` |
 | `--out`         | Write data to file (format from extension: .csv, .jsonl, .json) |
 | `--append`      | Append to existing file (skip CSV headers)                   |
 | `--output`      | Output format: `json` \| `csv` \| `jsonl` \| `md`           |
@@ -393,9 +398,21 @@ The same lines also go to stderr. A read with nothing to report prints none of i
 | `negative-list-attachments`| Which campaigns each shared list covers | ALL_TIME        |
 | `search-terms`         | Actual user queries triggering ads       | LAST_7_DAYS        |
 | `ad-copy-performance`  | Ad headline/description effectiveness    | LAST_30_DAYS       |
-| `asset-performance`    | PMax asset performance labels            | LAST_30_DAYS       |
+| `asset-performance`    | PMax assets: serving status + metrics    | LAST_30_DAYS       |
 | `shopping-products`    | Product-level shopping metrics           | LAST_30_DAYS       |
 | `account-summary`      | Account-level totals                     | LAST_30_DAYS       |
+| `pmax-channels`        | PMax spend/results per channel (Search, YouTube, Display, …) | LAST_30_DAYS |
+| `pmax-placements`      | Where PMax ads showed (impressions)      | LAST_30_DAYS       |
+| `placements`           | Display / Video / Demand Gen placements with cost and conversions | LAST_30_DAYS |
+| `rsa-assets`           | Each RSA headline/description: pin, approval, own metrics | LAST_30_DAYS |
+| `landing-pages`        | Final URLs with clicks, cost, speed score, mobile-friendly share | LAST_30_DAYS |
+| `geo-performance`      | Results by country and location type (in vs interested in) | LAST_30_DAYS |
+| `age-performance` / `gender-performance` | Results by age range / gender per ad group | LAST_30_DAYS |
+| `ai-max-search-terms`  | AI Max search terms with the headline and landing page used | LAST_30_DAYS |
+| `account-budget`       | Account budget: limit, served, pending change | —               |
+| `recommendations`      | Google's open recommendations with impact | —                 |
+| `campaign-simulations` / `keyword-bid-simulations` | Google's what-if points (budget, tCPA, tROAS, CPC bid) | — |
+| `campaigns`, `budgets`, `ad-groups`, `keywords`, `ads`, `assets`, `asset-groups`, `audiences`, `conversion-actions`, `bidding-strategies`, `labels`, `campaign-criteria`, `ad-group-criteria`, `ad-group-bid-modifiers`, `account-exclusions`, `shared-sets`, `campaign-negative-keywords`, `ad-group-negative-keywords` | Inventories behind the `<thing> list` commands | — |
 
 Every preset except the negatives lists and `account-summary` filters to **actually-serving entities** by default — the full status chain (`campaign.status = 'ENABLED' AND ad_group.status = 'ENABLED' AND ad_group_ad.status = 'ENABLED'`, as applicable) — and selects the status columns so you can see them. Pass `--include-paused` to widen to `!= 'REMOVED'` (keeps paused, still drops removed). Raw GAQL (no `--preset`) has no such default: a query over a serving-hierarchy resource without a status filter emits a `SERVING_SCOPE` warning reminding you to add the chain, because Google Ads has no single serving flag.
 
@@ -411,13 +428,12 @@ The CLI rejects or automatically corrects common GAQL mistakes before hitting th
 
 | Pattern | Behavior | Warning/error emitted |
 |---------|----------|-----------------------|
-| Missing LIMIT | Adds `LIMIT 200` | `"Added LIMIT 200. Use --limit to override."` |
 | Bare `keyword.text` / `keyword.match_type` | Rewrites to `ad_group_criterion.*` (resource-scoped forms like `shared_criterion.keyword.text` pass through untouched) | `"keyword.text → ad_group_criterion.keyword.text"` |
 | `shopping_performance_view.product_*` | Rewrites to `segments.product_*` | Field renamed |
 | `campaign.status = 'ACTIVE'` | Rewrites to `= 'ENABLED'` | Enum corrected |
 | `segments.conversion_action_name` with `metrics.cost_micros` | Rejects; split into separate conversion-action and spend queries | `INCOMPATIBLE_FIELDS` with `fix.action: "split_query"` |
 | `DURING` with a literal Google does not accept (`LAST_90_DAYS`, `LAST_12_MONTHS`, `THIS_YEAR` …) | Rejects before any request; `DURING` takes only `TODAY`, `YESTERDAY`, `LAST_7_DAYS`, `LAST_14_DAYS`, `LAST_30_DAYS`, `LAST_BUSINESS_WEEK`, `THIS_MONTH`, `LAST_MONTH`, `THIS_WEEK_SUN_TODAY`, `THIS_WEEK_MON_TODAY`, `LAST_WEEK_SUN_SAT`, `LAST_WEEK_MON_SUN` | `INVALID_DATE_RANGE`, with `fix.correctedCommand` spelling the same window as `BETWEEN 'YYYY-MM-DD' AND 'YYYY-MM-DD'` |
-| `--limit` outside 1–8,192, or a statement `LIMIT` above 8,192 | Rejects before any request — one read returns at most 8,192 rows | `VALIDATION_ERROR` naming the cap and how to split a bigger read; a statement `LIMIT` also gets `fix.correctedCommand` at `LIMIT 8192` |
+| `--limit` outside 1–8,192 | Rejects before any request — one page holds at most 8,192 rows | `VALIDATION_ERROR` pointing at `--all --out` for bigger reads |
 | `FROM ad_group_criterion` without `negative` field | Warns | `"ad_group_criterion returns BOTH positive and negative keywords. Use --preset positive-keywords or negative-keywords."` |
 
 Auto-fixed queries proceed normally. Warnings appear in the response:
@@ -456,7 +472,7 @@ Google keeps account history in two layers, and neither reaches past 90 days:
 
 | Scope       | Reach   | What you get                                                        |
 |-------------|---------|---------------------------------------------------------------------|
-| `detail`    | 30 days | What changed, old → new value, and who changed it                   |
+| `detail`    | 30 days | What changed — a `changes` list of `{ field, old, new }` per changed field — and who changed it |
 | `summary`   | 90 days | Which resources were added, changed or removed — no values, no user  |
 
 Beyond 90 days there is no API. Infer the change from a monthly spend trend per campaign
@@ -481,6 +497,43 @@ baker ads google changes --customer-id 1234567890 --days 60 --scope summary
 
 ---
 
+### `baker ads google keywords forecast` / `keywords themes`
+
+```bash
+baker ads google keywords forecast --customer-id 1234567890 --text "running shoes:PHRASE,trail shoes:EXACT" --max-cpc 1.2 --location 2724 --language 1003
+baker ads google keywords forecast --customer-id 1234567890 --text "crm software" --match-type BROAD --daily-spend 20 --strategy MAXIMIZE_CONVERSIONS --start 2026-11-01 --end 2026-11-30
+baker ads google keywords themes --customer-id 1234567890 --keywords "trail shoes,road shoes" --ad-groups 111,222
+```
+
+`forecast` returns Google's Keyword Planner forecast (v25) for the whole period under one bidding strategy: `{ source: "keyword_planner_forecast", period, forecast_clicks, forecast_cost_micros, forecast_conversions, forecast_average_cpc_micros, forecast_average_cpa_micros }`. `--max-cpc` alone is Manual CPC; `--daily-spend` is Maximize clicks (or Maximize conversions with `--strategy`). Without `--start/--end` it forecasts the 30 days from tomorrow. `themes` returns which existing ad group each keyword fits (`suggestions`) and the ad groups Google could not read a theme from (`unusable_ad_groups`).
+
+### `baker ads google previews` / `invoices` / `identity-verification` / `brands`
+
+```bash
+baker ads google previews --customer-id 1234567890 --asset-groups 6743268912        # Performance Max, Google's preview page
+baker ads google previews --customer-id 1234567890 --ads 111~222                     # a Video campaign's ad, live on YouTube
+baker ads google invoices --customer-id 1234567890 --month 2026-09
+baker ads google identity-verification --customer-id 1234567890
+baker ads google brands --customer-id 1234567890 --prefix nike                     # brand entity ids for a BRANDS list
+```
+
+Read-only. A refusal that is the account's situation comes back as a structured error the agent carries on from: `NOT_INVOICED` (not billed by monthly invoicing — no invoices through the API), `VERIFICATION_NOT_READABLE` (verification status is only readable through the API on monthly invoicing), `NO_PREVIEW_FOR_AD_TYPE` (only video ads of Video campaigns preview by ad). Each `error.fix` says where the answer lives instead.
+
+### `baker ads google <thing> list`
+
+What exists, with the id or resource name each write command takes — one inventory preset read through `query`, so it pages (`--limit`, `--cursor`, `--all --out`) and formats (`--output`) the same way. Paused entities are listed; removed ones are not; `--serving-only` narrows to what serves.
+
+```bash
+baker ads google campaigns list --customer-id 1234567890
+baker ads google keywords list --customer-id 1234567890 --all --out keywords.csv
+baker ads google negative-keywords list --customer-id 1234567890 --level adGroup
+baker ads google keyword-lists list --customer-id 1234567890 --members
+```
+
+Lists exist for `campaigns`, `budgets`, `ad-groups`, `keywords`, `negative-keywords` (`--level campaign|adGroup`), `keyword-lists` (`--members` for the terms), `ads`, `assets`, `asset-groups`, `audiences`, `conversions`, `bidding-strategies`, `labels`, `campaign-criteria`, `ad-group-criteria`, `ad-group-bid-modifiers` and `account-exclusions`.
+
+---
+
 ### `baker ads google keywords discover`
 
 Discover keyword ideas from seed keywords or URLs.
@@ -488,6 +541,7 @@ Discover keyword ideas from seed keywords or URLs.
 ```bash
 baker ads google keywords discover --customer-id 1234567890 --seeds "running shoes,athletic footwear"
 baker ads google keywords discover --customer-id 1234567890 --url "https://competitor.com" --limit 50
+baker ads google keywords discover --customer-id 1234567890 --seeds "running shoes" --cursor <next_page_token>   # next page
 ```
 
 **Response:**
@@ -601,6 +655,8 @@ Reference not-yet-created resources with `g_temp_*` refs returned by earlier `cr
 ```bash
 # Build a Search campaign bottom-up, chaining temp refs
 baker ads google budgets create --customer-id 1234567890 --name "Search budget" --amount 50
+# Delivery is always STANDARD: --delivery ACCELERATED is refused (Google stores such a budget but will
+# not attach it to a campaign).
 # → { ref: "g_temp_ab12", ... }
 baker ads google campaigns create --customer-id 1234567890 --name "Brand — Search" \
   --channel-type SEARCH --budget-ref g_temp_ab12 --bidding-strategy MANUAL_CPC \
@@ -633,6 +689,10 @@ baker ads google campaigns update <campaign-id> --customer-id 1234567890 \
 # --ai-max-url-expansion (final URL expansion, needs text customization). An omitted switch
 # keeps the campaign's value; a combination Google refuses is refused at staging.
 baker ads google campaigns update <campaign-id> --customer-id 1234567890 --ai-max --ai-max-text
+# Bidding is per campaign type — staging refuses a pair Google does not take and names the ones it does.
+# Target impression share (Search only) needs its whole goal on a new strategy:
+baker ads google campaigns update <campaign-id> --customer-id 1234567890 --bidding-strategy TARGET_IMPRESSION_SHARE \
+  --impression-share 70 --impression-share-location ABSOLUTE_TOP_OF_PAGE --max-cpc 2
 baker ads google ad-groups create --customer-id 1234567890 --name "Brand terms" --campaign-ref g_temp_<campaign>
 baker ads google keywords add --customer-id 1234567890 --ad-group-ref g_temp_<adgroup> --text "brand name" --match-type EXACT
 # Shared negative keyword list → attach to the campaign
@@ -666,7 +726,7 @@ baker ads google ads create --customer-id 1234567890 --ad-group-ref g_temp_<adgr
 # Video ad — the YouTube video is its own asset first, then referenced by --video-assets
 baker ads google assets create --customer-id 1234567890 --file '{"type":"youtubeVideo","youtubeVideoId":"dQw4w9WgXcQ"}'
 baker ads google ads create --customer-id 1234567890 --ad-group-ref g_temp_<adgroup> --format video \
-  --video-assets g_temp_<video> --final-url https://example.com
+  --video-assets g_temp_<video> --business-name "Acme" --logo-image-assets g_temp_<img_logo> --final-url https://example.com
 # Demand Gen ad — image refs the same way
 baker ads google ads create --customer-id 1234567890 --ad-group-ref g_temp_<adgroup> --format demandGen \
   --headlines "Discover the app" --descriptions "Try it free today" --business-name "Acme" --final-url https://example.com \
@@ -681,6 +741,8 @@ baker ads google ads create --customer-id 1234567890 --ad-group-ref g_temp_<adgr
 # App campaign ad — images are fields on the ad itself, same asset-ref flow
 baker ads google ads create --customer-id 1234567890 --ad-group-ref g_temp_<adgroup> --format app \
   --headlines "Insure your dog" --descriptions "Refunds in 2 hours" --image-assets g_temp_<img1>,g_temp_<img2>
+# Call ads are retired — Google's API has no call ad, so --format call is refused. Stage a responsive
+# search ad and have the user add the phone number as a call asset in Google Ads.
 # Change a live ad's content — every field you pass replaces its current value, so list what you want to keep
 baker ads google ads update <adId> --customer-id 1234567890 --format app \
   --headlines "Insure your dog" --descriptions "Refunds in 2 hours" \
@@ -702,9 +764,16 @@ baker ads google asset-groups attach --customer-id 1234567890 \
 baker ads google asset-groups detach customers/1234567890/assetGroupAssets/6718302454~402654762568~PORTRAIT_MARKETING_IMAGE \
   --customer-id 1234567890
 
+# Audiences — each type carries what Google builds it from (a type alone is refused)
+baker ads google audiences create --customer-id 1234567890 --file '{"name":"Pricing visitors","type":"RULE_BASED","rule":{"include":[{"conditions":[{"operator":"CONTAINS","value":"/pricing"}],"lookbackWindowDays":30}],"prefill":true}}'
+# BASIC takes "conversionActions", LOGICAL "logic", LOOKALIKE "lookalike" — each naming lists/actions
+# that already exist in the account (not g_temp_* refs). `baker ads google audiences create --help` has one example per type.
+
 # Review / undo / amend staged changes
 baker ads google draft list                  # readable campaign ▸ ad group ▸ ad tree + completeness advisories
 baker ads google draft list --json           # raw JSON envelope for scripting
+baker ads google draft validate              # dry run the whole draft against Google (validateOnly) — per-op verdicts
+baker ads google draft validate --full       # every op, with the built request and Google's raw answer
 baker ads google draft show g_temp_ab12      # full staged payload — the receipt before publish
 baker ads google draft amend g_temp_ab12 --patch '{"amountMicros": 60000000}'   # update in place, never remove+recreate
 baker ads google draft remove g_temp_ab12    # cascades to dependents
@@ -719,7 +788,17 @@ baker tag-manager draft show --chat <chat-id> gtm_temp_ab12
 baker actions draft --chat <chat-id>
 ```
 
-Command groups: `budgets`, `campaigns`, `ad-groups`, `keywords` (add/update/remove), `negative-keywords`, `keyword-lists`, `ads`, `assets` (create/update/attach/detach), `asset-groups` (create/update/attach/detach — Performance Max), `audiences`, `conversions` (create/update/goal/upload), `bidding-strategies`, `labels`, `campaign-criteria` (add/update/remove), and `draft`. Amounts are in major currency units (converted to micros). Money/bids: `--amount`, `--cpc-bid`, `--target-cpa`, `--target-cpc`, `--max-cpc` take major units; `--target-roas` a ratio. `--target-cpc` pairs with `--bidding-strategy TARGET_CPC` and is Demand Gen only. `--max-cpc` sets the max CPC bid ceiling for `TARGET_IMPRESSION_SHARE` / `TARGET_SPEND` / `PERCENT_CPC` and must be paired with `--bidding-strategy`. Less-common ops accept a `--file` payload — a path to a JSON file, or the JSON object written inline (flags override its keys). Updates target a resource name or bare id as the positional argument; a target that names an op staged earlier **amends it in place**.
+**Budgets and portfolios** — `budgets create --total 300` stages a total budget (one amount over the campaign's flight; Search, Performance Max and Demand Gen; the campaign needs `--end-date`; never shared) instead of `--amount`'s daily one, and `budgets update --total` moves it. `campaigns create|update --portfolio-ref <ref>` puts a campaign on a portfolio bid strategy (checked against the campaign type); staging a campaign's own `--bidding-strategy` while it is on a portfolio takes it off (with a warning). `budgets remove <id>` and `bidding-strategies remove <id>` remove a budget / portfolio once no campaign uses it — staging refuses while one does, unless the same draft removes or moves those campaigns; publish removes the campaigns first.
+
+**Shopping campaigns** — `campaigns create --channel-type SHOPPING --merchant-id <id>` (`merchant-center list` shows the Merchant Center accounts linked to the account; staging refuses any other) with optional `--feed-label`, `--shopping-priority low|medium|high` and `--local-inventory`; `campaigns update` changes those three (`--clear-feed-label`), never the Merchant Center. `ad-groups create --type SHOPPING_PRODUCT_ADS` creates the ad group with its "All products" listing group, and `ads create --format shoppingProduct` its product ad (no copy — the feed supplies it). A retail Performance Max campaign takes `--merchant-id` / `--feed-label` too.
+
+**App, Travel and Hotel campaigns** — App: `campaigns create --channel-type MULTI_CHANNEL --sub-type APP_CAMPAIGN|APP_CAMPAIGN_FOR_ENGAGEMENT --app-id <package or App Store id> --app-store google|apple --app-goal installs|installs-volume|in-app|in-app-install-cost|value [--app-conversions <ids>]` (each goal takes one bidding strategy; App ads are created enabled — Google refuses a paused one, so `ads create --format app` defaults to `ENABLED`). Travel: `--channel-type TRAVEL --travel-account-id <id>` on Maximize conversion value with `--target-roas`. Hotel: `--channel-type HOTEL --hotel-center-id <id>`. Staging asks Google (validate-only) whether the app, the travel account or Hotel Center is there and refuses with what to ask the user when it is not. Smart campaigns are refused (their business setting cannot be validated).
+
+**Dynamic Search Ads and frequency caps** — `campaigns create|update --dsa-domain <domain> --dsa-language <code> [--dsa-supplied-urls-only]` (Search only; an update may change one field; it cannot be removed) and `--frequency-cap <cap>/<day|week|month>[/<campaign|ad-group|ad>][/<impressions|video-views>]` (repeatable, replaces the campaign's caps; `--clear-frequency-caps`; Display and existing Video campaigns only).
+
+**Performance Max creative controls** — `campaigns create|update` take `--term-exclusion` / `--messaging-restriction` (text guidelines; a Search create needs `--ai-max --ai-max-text`), the generated-asset switches `--generated-text --url-expansion --video-enhancement --image-enhancement --image-extraction --image-design-versions` (each `=false` to turn off), `--brand-guidelines` on create (link the business name and a square logo to the campaign in the same draft) and `--main-color --accent-color --font`. `campaigns enable-brand-guidelines <id> --business-name-asset --logo-assets [--landscape-logo-assets] [--final-url-domain] | --auto-populate` turns brand guidelines on for an existing campaign at publish (no dry run: `draft validate` shows it unchecked).
+
+Command groups: `account` (update), `budgets` (create/update/remove), `campaigns`, `ad-groups`, `keywords` (add/update/pause/resume/remove), `negative-keywords` (add/update/remove — `update <resource name> --text --match-type` publishes as a replace of the live negative), `keyword-lists` (create/rename/delete a list — `--type NEGATIVE_KEYWORDS|NEGATIVE_PLACEMENTS|BRANDS|ACCOUNT_LEVEL_NEGATIVE_KEYWORDS`; add/remove its members — keywords, or `--placement/--app/--youtube-channel/--youtube-video/--brand`; attach/detach), `ads`, `assets` (create/update/attach/detach), `asset-groups` (create/update/attach/detach — Performance Max), `audiences`, `conversions` (create/update/goal/upload), `bidding-strategies` (create/update/remove), `labels` (create/update/remove; attach/detach on a campaign, ad group, ad or keyword — `--level --on --label-ref`), `campaign-criteria` (add/update/remove — locations, languages, schedule, devices, radius, carriers, operating systems, and exclusions of placements, apps, YouTube, topics, demographics, content types, IP addresses, web pages, brand lists), `ad-group-criteria` (add/update/remove — placements, topics, demographics, web pages, Demand Gen locations/languages/combined audience; `update --bid-modifier --max-cpc --status`), `ad-group-bid-modifiers` (add/update/remove — one ad group's own device bid), `account-exclusions` (add/remove — account-wide site, app, YouTube, content-type, IP and negative-keyword-list exclusions; `add --placement --youtube-channel --youtube-video --app --content-label --ip` comma-separated, or `--file`), `merchant-center` (list), and `draft`. `audiences attach` takes `--user-list`, `--interest` or `--custom-segment`. Amounts are in major currency units (converted to micros). Money/bids: `--amount`, `--cpc-bid`, `--target-cpa`, `--target-cpc`, `--max-cpc` take major units; `--target-roas` a ratio. `--target-cpc` pairs with `--bidding-strategy TARGET_CPC` and is Demand Gen only. `--max-cpc` sets the max CPC bid ceiling for `TARGET_IMPRESSION_SHARE` / `TARGET_SPEND` / `PERCENT_CPC` and must be paired with `--bidding-strategy`. Less-common ops accept a `--file` payload — a path to a JSON file, or the JSON object written inline (flags override its keys). Updates target a resource name or bare id as the positional argument; a target that names an op staged earlier **amends it in place**.
 
 **A device criterion can be added, but never removed** — `campaign-criteria add` with a device criterion works, but Google then rejects `campaign-criteria remove` on it forever, including on a criterion you added yourself (and Baker refuses the removal before publish). Adjust it instead with `campaign-criteria update customers/<cid>/campaignCriteria/<campaignId>~<criterionId> --bid-modifier <n>`: `1` for no adjustment, `1.25` to bid 25% more, `0.9` to bid 10% less, `0` to stop serving on that device. Locations, languages and ad schedules remove normally.
 
@@ -733,6 +812,8 @@ Command groups: `budgets`, `campaigns`, `ad-groups`, `keywords` (add/update/remo
 
 **Retiring a conversion action** — `status` accepts `ENABLED` and `REMOVED` only. Google denies `HIDDEN` on every conversion-action write, so to stop bidding toward an action while it keeps measuring use `--no-primary`, and to stop it counting at all use `"status": "REMOVED"`. Conversion actions **Google owns** cannot be changed at all — Smart campaign call/directions actions, the in-ad lead form's submit, YouTube subscriptions and follow-on views, Floodlight and Search Ads 360 imports, store visits, codeless webpage actions. Staging any edit to one, a rename included, is refused up front; there is no manual route either, since the Google Ads interface will not change them.
 
+**Validating the draft** — `baker ads google draft validate` sends the whole staged draft to Google exactly as publish would (same batching and order), with `validateOnly: true`, so nothing is applied. Each op comes back `accepted`, `refused` (with the reason publish would record), `blocked` (a change it depends on is refused), `unchecked` (only publish can check it — a new asset group, whose text assets are created first) or `applied` (an earlier publish did). Compact by default (counts plus the ops that need attention); `--full` lists every op with its request and Google's raw answer.
+
 **Reviewing the draft** — `baker ads google draft list` renders everything you've staged as a grouped campaign ▸ ad group ▸ ad tree (with non-blocking completeness advisories), the CLI counterpart to the dashboard's Google Ads tab. Pass `--json` for the raw envelope. Once the chat has published it reports the outcome instead — `published · N applied, M failed`, with a `✗` line naming each op that did not land and why. Aim for a fully built campaign — 2–4 ad groups, ≥5 keywords each, 2–4 RSAs with 8–12 headlines, ≥4 sitelinks / ≥3 callouts / ≥1 structured snippet, and ≥1 shared negative list; the advisories flag what's still thin.
 
 **Amending a staged op** — `draft amend <ref> (--file patch.json | --patch '<json>')` merges a JSON patch into an already-staged op's payload (objects deep-merge, `null` deletes a key, arrays/scalars replace) and re-validates it in full. Always prefer this over removing and re-staging — it preserves the op's ref (so dependents don't break) and its position in the draft. `draft show <ref>` prints the full staged payload (including warnings/annotations) so you can verify a change looks right before publish.
@@ -745,6 +826,8 @@ Command groups: `budgets`, `campaigns`, `ad-groups`, `keywords` (add/update/remo
 
 **Batch keyword adds** — `keywords add`, `negative-keywords add`, and `keyword-lists add` take a whole batch in one command: comma-separate `--text` entries and/or pass `--file <list.txt>` (one keyword per line). A `:EXACT`/`:PHRASE`/`:BROAD` suffix per entry overrides the `--match-type` default. Batches stage all-or-nothing as one request (limit 500); each keyword still lands as its own draft op, so it stays individually removable/amendable.
 
+**Bulk changes — one file, one call** — `draft stage --file ops.json [--customer-id <id>]` stages up to 500 ops of any mix of kinds in one request: the file is a JSON array (or JSON Lines) of whole ops `{"kind","customerId"?,"target"?,"payload"?}`; `--customer-id` fills ops that leave it out. All-or-nothing on validity (an error names `ops[i]`); ops the account already satisfies come back as `skipped`. An op may name a `g_temp_*` ref from an earlier call, not one from the same file. `draft amend --file amends.json` (no ref) amends many staged ops at once from `[{"ref","patch"}, …]`, all or none. The `--file` create commands (`assets create|attach`, `audiences create`, `conversions create`, `bidding-strategies create`, `labels attach`, `campaign-criteria add`, `ad-group-criteria add`) take a JSON array of payloads too. `keywords pause|resume <target>…` (or `--file`, one resource name per line) change many keywords' status in one call, and `keyword-lists remove --list-ref <id> --text "a,b:EXACT"` takes terms out of a shared negative list — the CLI reads the list to find each member (no `:MATCH_TYPE` = every match type), or takes members by resource name / `listId~criterionId`. Five single stages of one kind in a row on a chat earn a `LOOP:` hint pointing at these. A chat's draft holds any number of ops (each is its own record); only one op over `GOOGLE_DRAFT_OP_MAX_BYTES` (512 KB) is refused — the stage or amend stages nothing and answers `OP_TOO_LARGE` with an `error.fix` (split that change).
+
 **Pausing or removing a keyword returns a per-ad-group hint** — `keywords update --status PAUSED|REMOVED` and `keywords remove` come back with hints telling you to base the decision on `keyword_view` rows carrying `ad_group.id` + `ad_group_criterion.criterion_id`, never on campaign totals. A keyword's criterion id is derived from its text + match type, so every copy of the same keyword across ad groups shares one id and any aggregate blends the copy holding the history with the copies that never served. The `keyword-analysis` and `positive-keywords` presets select both ids so one query identifies each copy. A bid or URL edit gets no hint — only a pause/removal can strand history.
 
 ---

package/dist/{account-2OBWFPRG.js → account-AO6PNNPO.js}

@@ -2,7 +2,7 @@ import {
   csvOrJson,
   handleLinkedinError,
   resolveAccountIdArg
-} from "./chunk-YWK4UBVU.js";
+} from "./chunk-V5QJBDBC.js";
 import {
   writeAdsJson,
   writeAdsOutput
@@ -10,11 +10,11 @@ import {
 import {
   NO_CACHE_ARG
 } from "./chunk-X7ZODEXJ.js";
-import "./chunk-RZTNH2TX.js";
+import "./chunk-45OQOUJA.js";
 import "./chunk-GXDLWBOY.js";
 import "./chunk-TEINLN64.js";
-import "./chunk-ZJWUBJYQ.js";
-import "./chunk-NE4F3FHN.js";
+import "./chunk-XQIOCIDO.js";
+import "./chunk-ML7DLFFY.js";
 import {
   apiGet
 } from "./chunk-XBOK23HI.js";
@@ -68,7 +68,7 @@ Examples:
   },
   subCommands: {
     detail: accountDetailCommand,
-    "url-params": () => import("./write-commands-2XFNH4BW.js").then((m) => m.accountUrlParamsCommand)
+    "url-params": () => import("./write-commands-VXL5QKMT.js").then((m) => m.accountUrlParamsCommand)
   },
   args: accountDetailCommand.args,
   default: "detail"
@@ -76,4 +76,4 @@ Examples:
 export {
   accountCommand
 };
-//# sourceMappingURL=account-2OBWFPRG.js.map
+//# sourceMappingURL=account-AO6PNNPO.js.map

package/dist/account-reads-W3XO7CIW.js

@@ -0,0 +1,218 @@
+import {
+  exitWithServiceReadError
+} from "./chunk-QM6T4BFA.js";
+import {
+  failWriteValidation,
+  listFlag,
+  requireCustomerId
+} from "./chunk-4KCKNAVW.js";
+import "./chunk-ERSX3MKH.js";
+import "./chunk-XY7BZSDQ.js";
+import "./chunk-4NZ47VXO.js";
+import "./chunk-D5FY4FAK.js";
+import "./chunk-F2S5BLPE.js";
+import "./chunk-7VHPAGPK.js";
+import {
+  getManagerIdForCustomer,
+  writeJsonEnvelope
+} from "./chunk-VFIOJD5M.js";
+import "./chunk-WTOYCUKH.js";
+import "./chunk-DZSIUEGH.js";
+import "./chunk-VAJBWA2U.js";
+import "./chunk-HRYOZUSK.js";
+import "./chunk-VVZBBKRC.js";
+import "./chunk-YBMVHGY3.js";
+import "./chunk-XQIOCIDO.js";
+import "./chunk-ML7DLFFY.js";
+import {
+  apiPost
+} from "./chunk-XBOK23HI.js";
+import "./chunk-IFWP3ZDO.js";
+import "./chunk-NAWWC5I3.js";
+import {
+  registerSchema
+} from "./chunk-NU7JSWVA.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-W3XO7CIW.js.map

package/dist/account-reads-W3XO7CIW.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/commands/ads/google/account-reads.ts"],"sourcesContent":["/**\n * `baker ads google invoices | identity-verification | previews` — read-only service calls that\n * are not GAQL. A refusal that is the account's situation degrades with an `error.fix` (see\n * `service-read-errors.ts`) instead of failing the job.\n */\nimport type {\n  GoogleBrandSuggestionsResponse,\n  GoogleIdentityVerificationResponse,\n  GoogleInvoicesResponse,\n  GoogleShareablePreviewsResponse,\n} from \"@baker/api/ads-google\";\nimport { defineCommand } from \"citty\";\nimport { apiPost } from \"../../../client.ts\";\nimport { registerSchema } from \"../../../schemas.ts\";\nimport { getManagerIdForCustomer } from \"../cache.ts\";\nimport { writeJsonEnvelope } from \"../output.ts\";\nimport { exitWithServiceReadError } from \"./service-read-errors.ts\";\nimport { failWriteValidation, listFlag, requireCustomerId } from \"./write-shared.ts\";\n\ntype ArgDefs = Record<string, { type: \"string\" | \"boolean\"; description: string }>;\n\nfunction register(command: string, description: string, args: ArgDefs): void {\n  registerSchema({\n    command,\n    description,\n    args: Object.fromEntries(\n      Object.entries(args).map(([name, arg]) => [\n        name,\n        { type: arg.type, description: arg.description, required: false },\n      ]),\n    ),\n  });\n}\n\nasync function serviceRead<T>(path: string, customerId: string, body: Record<string, unknown>): Promise<T> {\n  const managerId = getManagerIdForCustomer(customerId);\n  const { data } = await apiPost<{ ok: true; data: T }>(path, {\n    customerId,\n    ...(managerId ? { managerId } : {}),\n    ...body,\n  });\n  return data;\n}\n\nconst CUSTOMER_ARG = {\n  \"customer-id\": { type: \"string\", description: \"Google Ads customer ID (10 digits, no dashes)\" },\n} as const;\n\nconst INVOICE_ARGS = {\n  ...CUSTOMER_ARG,\n  month: { type: \"string\", description: \"Issue month, YYYY-MM (default: last month)\" },\n} as const;\n\nregister(\n  \"ads.google.invoices\",\n  \"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 — the error's fix says where its receipts are; carry on.\",\n  INVOICE_ARGS,\n);\n\nexport const invoicesCommand = defineCommand({\n  meta: {\n    name: \"invoices\",\n    description: `List one month's invoices (monthly-invoicing accounts only). Read-only.\n\nExample:\n  baker ads google invoices --customer-id 1234567890 --month 2026-09`,\n  },\n  args: INVOICE_ARGS,\n  run: async ({ args }) => {\n    const customerId = requireCustomerId(args);\n    try {\n      const data = await serviceRead<GoogleInvoicesResponse>(\"/api/ads/google/invoices\", customerId, {\n        ...(args.month ? { month: args.month } : {}),\n      });\n      const hints =\n        data.invoices.length === 0\n          ? [`No invoice was issued in ${data.month}. Try the month before with --month.`]\n          : [\n              \"Amounts are micros in each invoice's currency_code (divide by 1,000,000). pdf_url needs the user's Google sign-in.\",\n            ];\n      writeJsonEnvelope({ ok: true, data, hints });\n    } catch (err) {\n      exitWithServiceReadError(err);\n    }\n  },\n});\n\nregister(\n  \"ads.google.identity-verification\",\n  \"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 — otherwise the error's fix says where the user reads it; carry on.\",\n  CUSTOMER_ARG,\n);\n\nexport const identityVerificationCommand = defineCommand({\n  meta: {\n    name: \"identity-verification\",\n    description: `Advertiser identity verification status and deadlines. Read-only.\n\nExample:\n  baker ads google identity-verification --customer-id 1234567890`,\n  },\n  args: CUSTOMER_ARG,\n  run: async ({ args }) => {\n    const customerId = requireCustomerId(args);\n    try {\n      const data = await serviceRead<GoogleIdentityVerificationResponse>(\n        \"/api/ads/google/identity-verification\",\n        customerId,\n        {},\n      );\n      const pending = data.programs.filter((program) => program.status === \"PENDING_USER_ACTION\");\n      const hints =\n        pending.length > 0\n          ? [\n              `Verification is waiting on the advertiser${pending[0]?.completion_deadline ? ` (deadline ${pending[0].completion_deadline})` : \"\"}: give the user the action_url — ads stop serving if it lapses.`,\n            ]\n          : [];\n      writeJsonEnvelope(hints.length > 0 ? { ok: true, data, hints } : { ok: true, data });\n    } catch (err) {\n      exitWithServiceReadError(err);\n    }\n  },\n});\n\nconst PREVIEW_ARGS = {\n  ...CUSTOMER_ARG,\n  ads: {\n    type: \"string\",\n    description:\n      \"Comma-separated video ads of Video campaigns as {adGroupId}~{adId} (from `ads list`) — previewed live on YouTube\",\n  },\n  \"asset-groups\": {\n    type: \"string\",\n    description:\n      \"Comma-separated Performance Max asset group ids (from `asset-groups list`) — previewed on Google's preview page\",\n  },\n} as const;\n\nregister(\n  \"ads.google.previews\",\n  \"Shareable preview links for Performance Max asset groups (Google's preview page) and video ads (live on YouTube) that already exist in the account — 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.\",\n  PREVIEW_ARGS,\n);\n\nexport const previewsCommand = defineCommand({\n  meta: {\n    name: \"previews\",\n    description: `Shareable preview links for existing Performance Max asset groups and video ads. Read-only.\n\nExamples:\n  baker ads google previews --customer-id 1234567890 --asset-groups 6743268912\n  baker ads google previews --customer-id 1234567890 --ads 195752489650~826812181091   # a video ad, live on YouTube`,\n  },\n  args: PREVIEW_ARGS,\n  run: async ({ args }) => {\n    const customerId = requireCustomerId(args);\n    const ads = listFlag(args.ads);\n    const assetGroups = listFlag(args[\"asset-groups\"]);\n    if (!ads?.length && !assetGroups?.length) failWriteValidation(\"pass --ads and/or --asset-groups\");\n    try {\n      const data = await serviceRead<GoogleShareablePreviewsResponse>(\"/api/ads/google/previews\", customerId, {\n        ...(ads ? { ads } : {}),\n        ...(assetGroups ? { assetGroups } : {}),\n      });\n      writeJsonEnvelope({\n        ok: true,\n        data,\n        hints: [\n          \"Each link expires (expires_at). It shows what is live in the account now, not anything staged in this chat.\",\n        ],\n      });\n    } catch (err) {\n      exitWithServiceReadError(err);\n    }\n  },\n});\n\nconst BRAND_ARGS = {\n  ...CUSTOMER_ARG,\n  prefix: { type: \"string\", description: \"The start of the brand's name (at least 2 letters)\" },\n} as const;\n\nregister(\n  \"ads.google.brands\",\n  \"Find a brand's Google entity id — what a BRANDS list member names (`keyword-lists add --brand /g/…`). Start here: `baker ads google brands --customer-id 1234567890 --prefix nike`. Several brands can share a name: pick by the URL. Read-only.\",\n  BRAND_ARGS,\n);\n\nexport const brandsCommand = defineCommand({\n  meta: {\n    name: \"brands\",\n    description: `Find brand entity ids for a brand list (BRANDS). Read-only.\n\nExample:\n  baker ads google brands --customer-id 1234567890 --prefix nike`,\n  },\n  args: BRAND_ARGS,\n  run: async ({ args }) => {\n    const customerId = requireCustomerId(args);\n    if (typeof args.prefix !== \"string\" || args.prefix.trim().length < 2) {\n      failWriteValidation(\"--prefix needs at least the first 2 letters of the brand\");\n    }\n    try {\n      const data = await serviceRead<GoogleBrandSuggestionsResponse>(\"/api/ads/google/brands\", customerId, {\n        prefix: args.prefix,\n      });\n      const hints =\n        data.brands.length > 0\n          ? [\n              \"Several brands can share a name — pick the one whose URL is the brand you mean, then `keyword-lists add --list-ref <BRANDS list> --brand <entity_id>`.\",\n            ]\n          : [\"No brand starts with that — try a shorter or different prefix.\"];\n      writeJsonEnvelope({ ok: true, data, hints });\n    } catch (err) {\n      exitWithServiceReadError(err);\n    }\n  },\n});\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAWA,SAAS,qBAAqB;AAU9B,SAAS,SAAS,SAAiB,aAAqB,MAAqB;AAC3E,iBAAe;AAAA,IACb;AAAA,IACA;AAAA,IACA,MAAM,OAAO;AAAA,MACX,OAAO,QAAQ,IAAI,EAAE,IAAI,CAAC,CAAC,MAAM,GAAG,MAAM;AAAA,QACxC;AAAA,QACA,EAAE,MAAM,IAAI,MAAM,aAAa,IAAI,aAAa,UAAU,MAAM;AAAA,MAClE,CAAC;AAAA,IACH;AAAA,EACF,CAAC;AACH;AAEA,eAAe,YAAe,MAAc,YAAoB,MAA2C;AACzG,QAAM,YAAY,wBAAwB,UAAU;AACpD,QAAM,EAAE,KAAK,IAAI,MAAM,QAA+B,MAAM;AAAA,IAC1D;AAAA,IACA,GAAI,YAAY,EAAE,UAAU,IAAI,CAAC;AAAA,IACjC,GAAG;AAAA,EACL,CAAC;AACD,SAAO;AACT;AAEA,IAAM,eAAe;AAAA,EACnB,eAAe,EAAE,MAAM,UAAU,aAAa,gDAAgD;AAChG;AAEA,IAAM,eAAe;AAAA,EACnB,GAAG;AAAA,EACH,OAAO,EAAE,MAAM,UAAU,aAAa,6CAA6C;AACrF;AAEA;AAAA,EACE;AAAA,EACA;AAAA,EACA;AACF;AAEO,IAAM,kBAAkB,cAAc;AAAA,EAC3C,MAAM;AAAA,IACJ,MAAM;AAAA,IACN,aAAa;AAAA;AAAA;AAAA;AAAA,EAIf;AAAA,EACA,MAAM;AAAA,EACN,KAAK,OAAO,EAAE,KAAK,MAAM;AACvB,UAAM,aAAa,kBAAkB,IAAI;AACzC,QAAI;AACF,YAAM,OAAO,MAAM,YAAoC,4BAA4B,YAAY;AAAA,QAC7F,GAAI,KAAK,QAAQ,EAAE,OAAO,KAAK,MAAM,IAAI,CAAC;AAAA,MAC5C,CAAC;AACD,YAAM,QACJ,KAAK,SAAS,WAAW,IACrB,CAAC,4BAA4B,KAAK,KAAK,sCAAsC,IAC7E;AAAA,QACE;AAAA,MACF;AACN,wBAAkB,EAAE,IAAI,MAAM,MAAM,MAAM,CAAC;AAAA,IAC7C,SAAS,KAAK;AACZ,+BAAyB,GAAG;AAAA,IAC9B;AAAA,EACF;AACF,CAAC;AAED;AAAA,EACE;AAAA,EACA;AAAA,EACA;AACF;AAEO,IAAM,8BAA8B,cAAc;AAAA,EACvD,MAAM;AAAA,IACJ,MAAM;AAAA,IACN,aAAa;AAAA;AAAA;AAAA;AAAA,EAIf;AAAA,EACA,MAAM;AAAA,EACN,KAAK,OAAO,EAAE,KAAK,MAAM;AACvB,UAAM,aAAa,kBAAkB,IAAI;AACzC,QAAI;AACF,YAAM,OAAO,MAAM;AAAA,QACjB;AAAA,QACA;AAAA,QACA,CAAC;AAAA,MACH;AACA,YAAM,UAAU,KAAK,SAAS,OAAO,CAAC,YAAY,QAAQ,WAAW,qBAAqB;AAC1F,YAAM,QACJ,QAAQ,SAAS,IACb;AAAA,QACE,4CAA4C,QAAQ,CAAC,GAAG,sBAAsB,cAAc,QAAQ,CAAC,EAAE,mBAAmB,MAAM,EAAE;AAAA,MACpI,IACA,CAAC;AACP,wBAAkB,MAAM,SAAS,IAAI,EAAE,IAAI,MAAM,MAAM,MAAM,IAAI,EAAE,IAAI,MAAM,KAAK,CAAC;AAAA,IACrF,SAAS,KAAK;AACZ,+BAAyB,GAAG;AAAA,IAC9B;AAAA,EACF;AACF,CAAC;AAED,IAAM,eAAe;AAAA,EACnB,GAAG;AAAA,EACH,KAAK;AAAA,IACH,MAAM;AAAA,IACN,aACE;AAAA,EACJ;AAAA,EACA,gBAAgB;AAAA,IACd,MAAM;AAAA,IACN,aACE;AAAA,EACJ;AACF;AAEA;AAAA,EACE;AAAA,EACA;AAAA,EACA;AACF;AAEO,IAAM,kBAAkB,cAAc;AAAA,EAC3C,MAAM;AAAA,IACJ,MAAM;AAAA,IACN,aAAa;AAAA;AAAA;AAAA;AAAA;AAAA,EAKf;AAAA,EACA,MAAM;AAAA,EACN,KAAK,OAAO,EAAE,KAAK,MAAM;AACvB,UAAM,aAAa,kBAAkB,IAAI;AACzC,UAAM,MAAM,SAAS,KAAK,GAAG;AAC7B,UAAM,cAAc,SAAS,KAAK,cAAc,CAAC;AACjD,QAAI,CAAC,KAAK,UAAU,CAAC,aAAa,OAAQ,qBAAoB,kCAAkC;AAChG,QAAI;AACF,YAAM,OAAO,MAAM,YAA6C,4BAA4B,YAAY;AAAA,QACtG,GAAI,MAAM,EAAE,IAAI,IAAI,CAAC;AAAA,QACrB,GAAI,cAAc,EAAE,YAAY,IAAI,CAAC;AAAA,MACvC,CAAC;AACD,wBAAkB;AAAA,QAChB,IAAI;AAAA,QACJ;AAAA,QACA,OAAO;AAAA,UACL;AAAA,QACF;AAAA,MACF,CAAC;AAAA,IACH,SAAS,KAAK;AACZ,+BAAyB,GAAG;AAAA,IAC9B;AAAA,EACF;AACF,CAAC;AAED,IAAM,aAAa;AAAA,EACjB,GAAG;AAAA,EACH,QAAQ,EAAE,MAAM,UAAU,aAAa,qDAAqD;AAC9F;AAEA;AAAA,EACE;AAAA,EACA;AAAA,EACA;AACF;AAEO,IAAM,gBAAgB,cAAc;AAAA,EACzC,MAAM;AAAA,IACJ,MAAM;AAAA,IACN,aAAa;AAAA;AAAA;AAAA;AAAA,EAIf;AAAA,EACA,MAAM;AAAA,EACN,KAAK,OAAO,EAAE,KAAK,MAAM;AACvB,UAAM,aAAa,kBAAkB,IAAI;AACzC,QAAI,OAAO,KAAK,WAAW,YAAY,KAAK,OAAO,KAAK,EAAE,SAAS,GAAG;AACpE,0BAAoB,0DAA0D;AAAA,IAChF;AACA,QAAI;AACF,YAAM,OAAO,MAAM,YAA4C,0BAA0B,YAAY;AAAA,QACnG,QAAQ,KAAK;AAAA,MACf,CAAC;AACD,YAAM,QACJ,KAAK,OAAO,SAAS,IACjB;AAAA,QACE;AAAA,MACF,IACA,CAAC,qEAAgE;AACvE,wBAAkB,EAAE,IAAI,MAAM,MAAM,MAAM,CAAC;AAAA,IAC7C,SAAS,KAAK;AACZ,+BAAyB,GAAG;AAAA,IAC9B;AAAA,EACF;AACF,CAAC;","names":[]}

package/dist/{accounts-TDTME6RQ.js → accounts-4TM4UZEJ.js}

@@ -1,7 +1,7 @@
 import {
   csvOrJson,
   handleLinkedinError
-} from "./chunk-YWK4UBVU.js";
+} from "./chunk-V5QJBDBC.js";
 import {
   connectedResourceHints
 } from "./chunk-P4NSJS54.js";
@@ -16,11 +16,11 @@ import {
 import {
   NO_CACHE_ARG
 } from "./chunk-X7ZODEXJ.js";
-import "./chunk-RZTNH2TX.js";
+import "./chunk-45OQOUJA.js";
 import "./chunk-GXDLWBOY.js";
 import "./chunk-TEINLN64.js";
-import "./chunk-ZJWUBJYQ.js";
-import "./chunk-NE4F3FHN.js";
+import "./chunk-XQIOCIDO.js";
+import "./chunk-ML7DLFFY.js";
 import {
   apiGet
 } from "./chunk-XBOK23HI.js";
@@ -74,4 +74,4 @@ Examples:
 export {
   accountsCommand
 };
-//# sourceMappingURL=accounts-TDTME6RQ.js.map
+//# sourceMappingURL=accounts-4TM4UZEJ.js.map