@koda-sl/baker-cli 0.489.0 → 0.491.0

package/README.md

@@ -1059,6 +1059,8 @@ baker ads meta lead-forms --page-id 100635183117758 --full           # also each
 baker ads meta leads --form-id 987654321 --since 2026-08-01 --until 2026-08-31
 baker ads meta leads --form-id 987654321 --after <nextCursor>        # results are PAGED — follow the cursor
 baker ads meta leads --form-id 987654321 --full                      # raw contact details (CRM hand-off only)
+baker ads meta leads --adset-id 6123456780                            # every ad in an ad set (also --ad-id, --campaign-id)
+baker ads meta lead-forms spec 987654321 > form.json                  # a live form as a create --file payload
 
 # "What are we running right now?"
 baker ads meta campaigns --account-id act_123                        # ACTIVE only by default
@@ -1092,7 +1094,30 @@ baker ads meta pixels --pixel-id 9988 --stats --days 7
 # "Why isn't it using MY conversions?"
 baker ads meta custom-conversions --account-id act_123          # id, event category, pixel, and the rule as a phrase
 baker ads meta custom-conversions --account-id act_123 --full   # raw rule JSON, retention, timestamps
-```
+
+# "Target people interested in solar, in Madrid, who speak Spanish" — targeting takes ids, never names
+baker ads meta targeting search --account-id act_123 --q "solar energy"        # interests, behaviors, employers, job titles… with their spec key
+baker ads meta targeting geo --account-id act_123 --q Madrid --country ES       # location keys
+baker ads meta targeting locales --account-id act_123 --q Spanish               # locale numbers
+baker ads meta targeting categories --account-id act_123 --class life_events    # a whole class
+baker ads meta targeting suggest --account-id act_123 --id interests:6003437140731
+baker ads meta targeting validate --account-id act_123 --targeting-file t.json  # every id valid under its key? retiring?
+baker ads meta targeting estimate --account-id act_123 --targeting-file t.json --optimization-goal LEAD_GENERATION
+
+# "Can this account run ads at all?" / identities and libraries
+baker ads meta account --account-id act_123                    # hint: disabled, no payment method, or Meta reconnect owed (bakerPermissions)
+baker ads meta instagram-accounts --account-id act_123         # the --instagram-user a creative can use
+baker ads meta apps --account-id act_123                       # apps it can promote
+baker ads meta dsa-recommendations --account-id act_123        # EU DSA beneficiary/payor names
+baker ads meta images --account-id act_123                     # image hashes already on Meta
+baker ads meta labels --account-id act_123
+baker ads meta catalogs --business-id 601050769212882          # --catalog-id <id> for its product sets
+baker ads meta instant-experiences --page-id 904238019441800   # a Page's Instant Experiences, published or not
+baker ads meta studies --account-id act_123                    # Meta A/B tests and their state; --study-id <id> for versions and results
+baker ads meta high-demand-periods --campaign-id 6123          # budget boosts
+```
+
+Search results come back with a paste-ready fragment in `hints`; each row's `type` is the key its id goes under. Staging an ad set refuses an id Meta does not list under its key, and warns when the audience is at Meta's 1,000-person floor or when anything is set ACTIVE on an account that cannot deliver.
 
 Use a Page only with an ad account listed in its `promotingAccountIds`. Instant-form reads need `hasPageAccessToken: true` on that Page and the company's lead-ads permissions.
 
@@ -1100,6 +1125,37 @@ Use a Page only with an ad account listed in its `promotingAccountIds`. Instant-
 
 `custom-conversions create` stages a new one (`--name`, `--pixel-id`, `--custom-event-type`, plus `--url-contains "/gracias"` or `--rule-file`). A rule is a tree of `and`/`or` over `{"<field>":{"<operator>":<value>}}` leaves, where the field is `URL`, `event`, `referrer` or any event parameter the pixel sends (`value`, `content_category`, or your own), so `--url-contains` is only the single-URL shortcut and `--rule-file` reaches the rest. Meta accepts an unmatchable rule and reports success, so staging refuses unknown operators, bare values, empty branches and two conditions written side by side where `and` was meant, before the op is staged. A case-sensitive `contains` is a real operator and gets through — on a URL always write `i_contains`. It is create-only, because Meta's edge offers neither update nor a delete that removes — which is also why staging refuses a create whose pixel, event category and rule already exist, live on the account or staged earlier in the same chat, or one that would pass Meta's cap of 100 per account. An ad set in the same chat can chain to it with `--custom-conversion-id meta_temp_*`.
 
+**Automated rules** — Meta's own automation (Ads Manager → Automated rules), which runs on Meta with no Baker involvement once published.
+
+```bash
+baker ads meta rules --account-id act_123                                   # every rule, what it does in words
+baker ads meta rules --rule-id 1132635173044914 > rule.json                  # one rule with its specs; edit and pass back:
+baker ads meta rules update 1132635173044914 --file rule.json                # id, timestamps and on/off switch are left out
+baker ads meta rules history --rule-id 1132635173044914 --hide-no-changes    # what it did and when
+baker ads meta rules preview 1132635173044914                                # what it would act on now
+baker ads meta rules create --name "Stop expensive ads" --apply-to ad --when "cost_per_result>20" --action pause
+baker ads meta rules create --name "Scale winners" --apply-to adset --when "roas>3" --window LAST_3D --action raise-budget --by 20% --cap 500 --max-times 3
+baker ads meta rules create --name "CPM alarm" --apply-to campaign --when "cpm>15" --window TODAY --action notify --realtime
+baker ads meta rules create --name "Rotate" --ids <adset-id> --action rotate      # --ids are the ad sets whose ads take turns (adset.id)
+baker ads meta rules update|enable|disable|delete <rule-id>
+```
+
+Writes stage like every Meta change and apply at publish; a rule naming an ad, ad set or campaign the same chat creates (`--ids meta_temp_*`) is created after it. Money is in the account currency's major units. `update` replaces each part it touches (what it checks, what it does, when it runs) whole, and cannot turn a scheduled rule real-time or back (Meta keeps a rule's evaluation type — create a new rule). A rule staged in the same chat is dropped with `draft remove`, not `rules delete`. `--at`, `--between` and `--days` make a custom timetable: beside `--schedule daily|hourly|half-hourly` they are refused rather than dropped. Meta's dry run creates rules for real, so staging checks them against Meta's documented field, operator and pairing rules instead, reads every object a rule names, and refuses a cost condition on a pause/unpause/notify rule over ad sets in an Advantage campaign budget campaign (Meta error 2703).
+
+**A/B tests** — Meta's split tests (Ads Manager → Experiments): Meta splits one audience between versions — ad sets or campaigns — so each person sees one, and calls the winner. Not `baker experiment`, which tests landing pages.
+
+```bash
+baker ads meta studies --account-id act_123                                  # tests whose versions run here: state, what each compares
+baker ads meta studies --study-id 6123                                       # versions with cell ids, each measure with Meta's results
+baker ads meta studies create --name "Broad vs lookalike" --adsets 6123,meta_temp_ab12 --start 2026-10-20T08:00Z --days 14 \
+  --confidence 90 --measure-pixel 1275507706837548 --measure-event Lead
+baker ads meta studies update 6123 --end 2026-11-10T08:00Z                   # --name, --description, --start/--split before it starts
+baker ads meta studies end 6123                                              # stop now, keep the results
+baker ads meta studies delete 6123                                           # remove it, results and all
+```
+
+Writes stage and apply at publish, after any ad set or campaign the same chat creates (`--adsets meta_temp_*`). One version per ad set or campaign, split evenly unless `--split`; name them with `--version-names`, once per version (`--version-names Broad --version-names "Lookalike, 1%"` — a name may hold a comma); `--file` takes Meta's own shape for several ad sets per version. Meta's dry run creates tests for real, so staging checks Ads Manager's rules instead — at least 2 versions, shares adding up to 100%, each object in one version, one kind of object, 1–30 days, a start in the future, nothing in another test running at the same time (Meta error 1840001) — and a running test keeps its start and split (1840011). A new end may make an A/B test up to 30 days long, a lift study up to 90.
+
 
 **Instant-form leads** — `leads` returns **one page** plus a `nextCursor`; a response carrying one is not the whole set, so follow it before quoting any total. Email and phone answers come back masked unless `--full`. Both commands need Meta lead ads switched on for the company (`pages_manage_ads` + `leads_retrieval`, granted at connect time — a company switched on after connecting must reconnect Meta first); each says which of the two is missing.
 
@@ -1110,6 +1166,8 @@ Meta writes mirror the Google/LinkedIn model: they **never hit the Graph API whe
 
 Staging also refuses what LinkedIn would reject at publish: a campaign group created `PAUSED` (only `DRAFT`/`ACTIVE`), a group `--total-budget` without `--end`, a `PAUSED` campaign in a `DRAFT` group, archiving a `DRAFT` ad, and a library image that is not JPG, PNG or GIF. Every campaign carries `--political-intent` (`NOT_DECLARED` by default; `NOT_POLITICAL` or `POLITICAL` are the advertiser's declaration). A write to an ad account LinkedIn has not enabled for Baker fails with a message saying so.
 
+Staging then asks Meta itself: campaign, ad set and ad creates and updates, and new creatives, are sent as a Meta dry run (`validate_only`, nothing applied), so a change Meta would refuse at publish is refused while staging, in Meta's words. A change building on something the same chat creates is checked at publish. `ads retag` asks Meta whether the ad takes edits at all before staging anything, and `--set` may be repeated.
+
 **That publish reaches the real ad account for every company** — Meta writes are generally available, with no per-company flag. Discarding the chat before it completes is what undoes a staged change.
 
 Chain a full ad from scratch with `meta_temp_*` refs (each create returns one):
@@ -1122,6 +1180,13 @@ baker ads meta media upload --account-id act_123 --kind image --image-id <bakerI
 baker ads meta lead-forms create --account-id act_123 --page-id 555 --name "Free audit" \
   --questions FULL_NAME,EMAIL,PHONE --privacy-policy-url https://example.com/privacy \
   --follow-up-url https://example.com   # → meta_temp_form
+#    --question "Budget? => Under 1k | 1k+" (repeatable), --locale ES_LA, --headline, --higher-intent,
+#    --intro-title/--intro-text, --thank-you-title/-body/-button/-button-text/-url/-phone/-country,
+#    --sharing open, --sms-verification, --tracking name=value; or the whole spec with --file form.json.
+# A form never changes once published and is never deleted: copy it with changes, then retire the old one.
+# A duplicate changes only the intro and thank-you fields you name (--thank-you-title alone keeps the live text and button).
+baker ads meta lead-forms duplicate 987654321 --account-id act_123 --name "Free audit (ES)" --locale ES_LA
+baker ads meta lead-forms archive 987654321 --account-id act_123      # unarchive brings it back
 
 # 2. campaign → ad set → creative → ad
 baker ads meta campaigns create   --account-id act_123 --name "Q3 Prospecting" --objective OUTCOME_LEADS --daily-budget 50   # → meta_temp_camp
@@ -1142,7 +1207,104 @@ baker ads meta draft remove meta_temp_cr   # removing a create cascades to depen
 baker ads meta draft clear
 ```
 
-Status changes are `pause|resume|archive|delete` subcommands on `campaigns`/`adsets`/`ads`. `archive` keeps the entity readable in Ads Manager; `delete` removes it permanently (an archived entity can only be deleted). `duplicate` reconstructs a paused copy from the live snapshot (`--replace` also pauses the original once the copy publishes — write it attached, `--replace=false` or `--no-replace`, since the spaced form `--replace false` is rejected: a boolean flag written with a space is set to true and the word dropped). Carousel/dynamic creatives and complex targeting go via `--file` (creativeType `carousel`/`dynamic`; full Meta targeting spec). Advantage+ Creative enhancements: `--standard-enhancements on|off`, or per-feature toggles via a `--file` `enhancements.features` map.
+Delivery controls on `adsets create|update`: `--min-roas 2.5` (ROAS goal bidding, goal `VALUE`), `--frequency-cap 2/7` (REACH/THRUPLAY), `--schedule "Mon-Fri 09-18"` (repeatable dayparting; lifetime budget only) with `--schedule-timezone viewer|account`, `--pacing standard|no_pacing`, `--daily-min-spend`/`--daily-spend-cap`/`--lifetime-min-spend`/`--lifetime-spend-cap` (an ad set's share of a campaign budget), `--budget-boost` (repeatable high-demand periods on the ad set's own daily budget; on update Meta adds them beside the ad set's existing boosts, and `--remove-boost`/`--move-boost` take one away or re-time it), and on create only `--attribution 7d_click,1d_view` (conversion goals; `LINK_CLICKS`, `LANDING_PAGE_VIEWS` and `REACH` take `1d_click` alone — Meta refuses a change on a live ad set) and `--dynamic-creative`. A frequency cap counts impressions or 2- or 15-second video views (6-second ones on `REACH` only); a cap at least the account's smallest daily budget (× the ad set's days for lifetime limits) above the minimum spend is required. Campaigns take `--budget-boost START..END=+AMOUNT|+PERCENT%` (repeatable high-demand periods on a daily budget; on update restate `--daily-budget`; Meta adds them to the campaign's existing boosts). `adsets update --clear daily-min-spend,daily-spend-cap,lifetime-min-spend,lifetime-spend-cap,schedule,boosts` and `campaigns update --clear boosts` take controls away; a ROAS floor goes by switching `--bid-strategy`. `campaigns` listings hint which campaigns Meta counts as Advantage+ (`--fields id,name,advantage_state_info` for each lever).
+
+Catalog, collection, messaging and app ads:
+
+```bash
+# Click-to-message: the ad set opens a conversation with the Page, the creative's button names the app and greets
+baker ads meta adsets create --campaign <id> --name "Chat" --optimization-goal CONVERSATIONS --billing-event IMPRESSIONS \
+  --destination-type MESSENGER --page-id 555 --daily-budget 10 --targeting-file t.json
+baker ads meta creatives create --page 555 --message "Chat with us" --link https://example.com --image-hash <hash> \
+  --cta MESSAGE_PAGE --greeting "Hi! How can we help?" --ice-breaker "Prices? => From 99 EUR."   # WHATSAPP_MESSAGE, INSTAGRAM_MESSAGE
+# App ads: store link + optional deep link and how it opens
+baker ads meta adsets create … --optimization-goal APP_INSTALLS --app-id <id> --app-store-url https://apps.apple.com/…
+baker ads meta creatives create --page 555 --message "Get the app" --link https://apps.apple.com/… --image-hash <hash> \
+  --cta INSTALL_MOBILE_APP --deep-link myapp://home --app-id <id> --applink-treatment deeplink_with_appstore_fallback
+# Advantage+ catalog ads
+baker ads meta campaigns create --name "Catalog" --objective OUTCOME_SALES --catalog-id <catalog>
+baker ads meta adsets create … --optimization-goal OFFSITE_CONVERSIONS --product-set-id <set> --custom-event-type PURCHASE
+baker ads meta creatives create --type catalog --page 555 --product-set-id <set> --message "{{product.name}}" \
+  --headline "{{product.price}}" --link https://shop.example --format carousel|single|slideshow
+# Instant Experience (elements in flag order; published at publish) and an ad — or a collection ad — opening it
+baker ads meta instant-experiences create --account-id act_123 --page-id 555 --name "Spring" --video-id <id> \
+  --text "Our range" --button "Shop => https://shop.example" [--footer "Visit => https://…"] [--unpublished]
+baker ads meta instant-experiences update <id> --publish          # an unpublished one only
+baker ads meta creatives create --type instant_experience --canvas-id meta_temp_… --page 555 --message "Tap" --image-hash <hash> [--format collection]
+# Catalogs, products, product sets, feeds (Catalog permission for Meta; catalogs the account's own Business owns)
+baker ads meta catalogs create --account-id act_123 --name "Shop" --pixel <pixel>      # catalog ads need a pixel on the catalog
+baker ads meta catalogs update <id> [--name …] [--pixel <id>] [--unlink-pixel <id>]  |  catalogs delete <id>
+baker ads meta catalogs products --catalog-id <id> [--full] [--retailer-id SKU-1]
+baker ads meta catalogs products create --catalog-id <id|meta_temp_…> --retailer-id SKU-1 --name … --description … \
+  --price 19.99 --currency EUR --url https://… --image-url https://… [--sale-price …] [--availability …] [--brand …]
+baker ads meta catalogs products update|delete <id>
+baker ads meta catalogs sets create --catalog-id <id> --name … [--retailer-id SKU-1 …] [--filter '<Meta rule JSON>']
+baker ads meta catalogs sets update|delete <id>
+baker ads meta catalogs feeds create --catalog-id <id> --name … [--url https://… --interval DAILY|HOURLY|WEEKLY --hour 3 --day MONDAY]
+baker ads meta catalogs feeds update|delete <id>  |  catalogs feeds --catalog-id <id>  |  catalogs diagnostics --catalog-id <id>
+# A photo on a Page that is never posted — for Instant Experience photo elements (Page posts permission for Meta)
+baker ads meta page-photos upload --page-id 555 --image-id <library image> [--caption …]  |  page-photos delete <id>
+# A photo collection: the four pictures under the hero, by the live experience's element ids
+baker ads meta creatives create --type instant_experience --format collection --canvas-id <id> … --collection-thumbnail <element> (×4)
+# Account settings, brand safety, reach and frequency
+baker ads meta account-settings --account-id act_123 [--name …] [--spending-limit 5000 | --remove-spending-limit | --reset-spending-limit] [--default-eu-advertiser "…" --default-eu-payer "…" | --clear-default-eu]
+baker ads meta account-details --account-id act_123 --show users|recommendations|account-controls|playables|place-page-sets   # reads only
+baker ads meta block-lists --account-id act_123 [--full]  |  block-lists create --name … --url a.com --url b.com  |  add <id> --url …  |  delete <id>
+baker ads meta adsets create|update … [--block-list <id>] [--content-filter FEED_STRICT] [--exclude-publisher-category gambling]
+baker ads meta reach-frequency --account-id act_123  |  reach-frequency predict --page-id 555 --budget 1000 --start … --end … --targeting-file t.json
+baker ads meta reach-frequency predict … [--objective OUTCOME_AWARENESS --optimization-goal REACH --target-frequency 2] [--instream-package PREMIUM] [--schedule "Mon-Fri 09-18"]
+baker ads meta reach-frequency reserve <quote id>  |  reach-frequency cancel <reservation id>
+baker ads meta adsets create --campaign <RESERVED campaign> … --reservation <reservation id or meta_temp_…>
+# Boosts, partnership ads, multi-advertiser ads, conversion domain
+baker ads meta page-posts --page-id 555
+baker ads meta instagram-media --instagram-user <id>
+baker ads meta comments --ad-id <id>
+baker ads meta creatives create --type existing_post --post-id <page>_<post> | --instagram-media-id <id> --page 555 | --ad-code <code> --page 555
+baker ads meta creatives create … [--partner-page <id>] [--partner-instagram <id>] [--partner-format both|first_only|auto] [--multi-advertiser opt_out]
+baker ads meta ads create … [--conversion-domain example.com]
+# Budget boosts one at a time, a rule run now, a lookalike of conversions, the audience in words
+baker ads meta campaigns|adsets update <id> [--remove-boost <boost id>] [--move-boost <boost id>=START..END]
+baker ads meta adsets update <id> --budget-boost START..END=+50%          # a live ad set with its own daily budget
+baker ads meta rules run <rule id>                                         # once, at publish
+baker ads meta audiences create --subtype LOOKALIKE --lookalike-of-conversions <campaign id> --ratio 0.01 --country ES
+baker ads meta targeting describe --account-id act_123 --adset-id <id> | --targeting-file t.json
+# Lift studies and creative tests
+baker ads meta studies create --type lift --campaigns <id> --holdout 10 --start … --days 28 --measure-pixel <id> --measure-event Lead
+baker ads meta studies create --type creative --ads <ad>,<ad> --test-daily-budget 2 --start … --days 7 [--confidence 90 --measure-pixel <id> --measure-event Purchase --observe-until …]
+```
+
+A flag only another type of test takes (`--holdout` on an A/B test, `--adsets` on a creative test, `--ads` or `--split` on a lift study) is refused rather than dropped. Rule amounts (`--when`, `--by`, `--cap`) take a dot or a comma for decimals; a lone comma before three digits (`1,234`) is refused as ambiguous.
+
+A conversation destination needs `--page-id`, and `CONVERSATIONS` a conversation destination. A deep link needs the button to lead to the App Store / Google Play page (Meta refuses it beside a website, subcode 1885949). Catalog tokens name their catalog type (`{{product.price}}`, never `{{price}}`); product audiences go in the targeting file as `product_audience_specs`. Catalog changes and Page photos are refused with a plain message when the company is not switched on for them. A product picture must be a public image Meta can fetch (checked at staging). Meta deletes no Instant Experience and changes none once published, so one is made only at publish; a photo element takes a Page photo (`page-photos upload`, by its `meta_temp_*` ref), and an ad opens only a published experience. A collection ad needs an experience of header → product set → footer and a set with at least four showable products. `creatives create --shop-destination website_only` opts a shop advertiser's ad out of Meta's v26 website-and-shop default.
+
+Staging refuses a budget under the ad account's own minimum for what the ad set is billed on (`account` shows `minimum_daily_budgets`). The account spending limit counts from when it is set and stops every campaign on the account. A block list takes sites off Audience Network and in-stream only, and Meta neither renames one nor takes a site off it; on `adsets update` the brand-safety flags alone keep the rest of the live targeting. A reach-and-frequency quote is a forecast that holds nothing; a reservation holds the price and an ad set bought on it takes its budget, dates and goal from it. Partnership ads need the ad's own Instagram identity and a partner Page with a linked Instagram account, and run once the partner approves. Listing Instagram posts and reading comments on ads need Meta permissions the connection does not ask for: both answer a plain refusal.
+
+Customer lists, lookalikes and account assets:
+
+```bash
+baker ads meta audiences create --account-id act_123 --name "Customers" --subtype CUSTOM --customer-file-source USER_PROVIDED_ONLY [--value-based]
+baker ads meta audiences members add <audienceId|meta_temp_…> --file customers.csv [--country ES] [--value-column revenue] [--columns email,phone] [--date-format DMY|MDY]
+baker ads meta audiences members remove <audienceId> --file unsubscribed.csv
+baker ads meta audiences members replace <audienceId> --file customers.csv   # everyone not in the file leaves; runs alone
+baker ads meta audiences create --name "LAL 1-3%" --subtype LOOKALIKE --lookalike-of <id> --starting-ratio 0.01 --ratio 0.03 --countries ES,PT [--allow-international-seeds]
+baker ads meta audiences update <id> --description … --opt-out-link https://… --customer-file-source …
+baker ads meta audiences delete <id>                      # permanent; refused while a lookalike or live ad set uses it
+baker ads meta audiences saved --account-id act_123       # saved audiences (read-only); adsets create --saved-audience <id> copies one's targeting
+baker ads meta custom-conversions update <id> --name … --description … --value 25
+baker ads meta custom-conversions delete <id>             # Meta archives it
+baker ads meta creatives delete <id>                      # refused while a live ad runs it (delete/repoint the ad in the same chat)
+baker ads meta media delete --image-hash <hash>           # out of the image library
+baker ads meta labels create --name "Q4 launch"           # → meta_temp_label
+baker ads meta labels attach <label|meta_temp_…> --campaigns 6123,6124 --adsets … --ads … --creatives …
+baker ads meta labels detach <label> --campaigns 6123
+baker ads meta labels rename <label> --name …  /  labels delete <label>
+```
+
+A customer list's file is read in the workspace: every value is normalized and SHA-256 hashed on the machine running the CLI (Meta's normalization: emails lowercased, phones with their country code, names without punctuation, a US zip's first five digits, a birthday as year/month/day); only the hashes are uploaded, in batches of 10,000 (at most 20 per change — 200,000 people), and held by Baker until publish; only counts are printed. A US state is sent as its two-letter code; slashed birthdays are read in the order the file shows, else refused until `--date-format DMY|MDY`; a value-based list reads `1,250.00` and `1.250,00` alike and leaves out a person without a value. The whole change is checked before the first batch uploads, and batches no draft needs are deleted after a day. A replace runs alone — Meta refuses it while the list still processes an earlier upload — and one that fails part-way is closed at once and reported as a half-replaced list; publishing it again waits while Meta still processes it. A lookalike needs `--ratio` and a country, and its seed must already hold people (not a list this chat creates). Label changes stage the object's whole label set (Meta replaces it), read against the labels it has now and applied at publish to the labels it has then. Deletes run last at publish, child before parent, and staging refuses a delete that would strand something live the draft does not also handle.
+
+`copy <id>` on `campaigns`/`adsets`/`ads` stages Meta's own copy (`POST /{id}/copies`), which keeps everything Meta holds: `--deep` (a campaign's ad sets and ads, an ad set's ads; at most 51 ads), `--to-campaign` / `--to-adset <id|meta_temp_*>`, `--status PAUSED|ACTIVE|INHERITED` (default PAUSED), `--rename top|deep|none`, `--rename-prefix`, `--rename-suffix`, and `--start`/`--end` for the copied ad sets. The copy's `meta_temp_*` ref resolves to its new id at publish, so `adsets update <copy ref> …` in the same chat changes the copy once Meta has made it. A deep copy runs as an asynchronous Meta job the publish waits on.
+
+Status changes are `pause|resume|archive|delete` subcommands on `campaigns`/`adsets`/`ads`. `archive` keeps the entity readable in Ads Manager; `delete` removes it permanently (an archived entity can only be deleted). `duplicate` reconstructs a paused copy from the live snapshot (`--replace` also pauses the original once the copy publishes — write it attached, `--replace=false` or `--no-replace`, since the spaced form `--replace false` is rejected: a boolean flag written with a space is set to true and the word dropped). Carousel/dynamic creatives and complex targeting go via `--file` (creativeType `carousel`/`dynamic`; full Meta targeting spec). Advantage+ Creative enhancements: `--standard-enhancements on|off` switches Meta's text suggestions only; every feature that changes the picture or video is sent off unless named with `--visual-enhancement <feature>` (repeatable). A video's cover: `--thumbnail-ref <meta_temp_*>` (a staged picture upload) or `--thumbnail-hash`. Carousels: `--card-order fixed|optimized` (default fixed) and `--end-card on|off` (default off). `creativeType: placement` (via `--file`) shows a different asset per placement (`assets[].placements`: `feed`, `stories`, `reels`, `right_column`, one `default`).
 
 #### Smart defaults (so agents don't enumerate the API)
 
@@ -1184,9 +1346,9 @@ preview             # iframe HTML for a creative or ad in a given ad_format, or
                     # placement an insights breakdown reported (--placement, --list-formats)
 ```
 
-Placement diagnostics deliberately stop at evidence. `insights` names a suspect placement with its share of delivery, `preview` shows what Meta renders there, and neither asserts *why* — Meta documents an eligibility error for a video creative in a video-incompatible placement, not a silent fallback to the cover frame. Ad-set writes that pin placements warn about the learning-phase reset, and a placement set missing the `feed` Meta requires alongside `marketplace`/`search`/`profile_feed`/`notification` is rejected at stage time.
+Placement diagnostics deliberately stop at evidence. `insights` names a suspect placement with its share of delivery, `preview` shows what Meta renders there, and neither asserts *why* — Meta documents an eligibility error for a video creative in a video-incompatible placement, not a silent fallback to the cover frame. Ad-set writes that pin placements warn about the learning-phase reset, and a placement set missing the `feed` Meta requires alongside `marketplace`/`search`/`profile_feed`/`notification` is rejected at stage time. Placements Meta retired on Graph v26 — Instagram `explore`, Messenger `story`, Facebook `video_feeds` — are refused at stage time with the replacement named; Instagram `explore_home` now runs on its own. Market-level insights use `--breakdowns comscore_market` (`dma` is refused by Meta). A Housing, Employment or Financial products ad set that narrows its audience must set `targeting_automation.advantage_audience` to 1 or 0. Click-to-message ad sets and Instant Experiences are refused at stage time when the Meta connection recorded no `pages_manage_ads` (it comes with the per-company lead ads switch).
 
-The HTTP backend exposes more endpoints (catalogs, ad-studies, ad-images, labels, high-demand-periods, raw currency lookup). They're intentionally not surfaced as CLI commands because AI agents rarely need them. Hit them via curl against `/api/ads/meta/*` if needed.
+Ad images, labels and high-demand periods are CLI commands (`images`, `labels`, `high-demand-periods`). The one backend endpoint not surfaced as a command is the raw currency lookup, which agents rarely need; hit it via curl against `/api/ads/meta/*` if needed.
 
 #### Auth + caching
 
@@ -1206,7 +1368,7 @@ A `FORBIDDEN` from any Meta command is a permission refusal on a live connection
 - `spend` is a decimal string in account currency, not an integer.
 - `effective_status` ≠ `status`. The dashboard shows effective_status (e.g. `WITH_ISSUES`, `PENDING_REVIEW`, `DISAPPROVED`, `ADSET_PAUSED`).
 - Meta creatives are effectively immutable once attached. Editing copy/image/CTA = stage a new creative + `ads update <id> --creative <ref>` (or `creatives duplicate`), not an edit of the live creative — see [Staged writes](#staged-writes-baker-ads-meta-campaignsadsetsadscreativesaudiencesmediadraft) above.
-- Currency offsets are non-uniform (JPY/KRW = 1, KWD/BHD = 1000, most = 100). Read `account.currency` before doing budget math.
+- Currency offsets are non-uniform (JPY/KRW/IDR/CRC = 1, most — BHD and JOD included — = 100). Read `account.currency` before doing budget math.
 
 ---
 
@@ -1591,7 +1753,7 @@ Shared flags: `--days <n>` (default 30) or `--start-date` / `--end-date` (`YYYY-
 
 **`tracking` answers "can this account be reported on at all", and it reads the ad account to do it.** `analytics ads` can only describe parameters that have already arrived, which leaves two blind spots that mislead in the expensive direction: a platform with no traffic in the window looks exactly like a platform whose ads carry nothing, and a dimension arriving under a name nobody has mapped looks exactly like one nothing carries. `baker analytics tracking` reads the mapping, the traffic **and** the client's own Google tracking templates / Meta URL parameters, so it can answer for a platform that has not had a click yet. Every dimension comes back in one of four states, and they are four different jobs: `covered` is done; `unmapped` means the URLs already carry it under a name Baker does not read, so run the `mapCommand` in the response — free, and it repairs the traffic already collected; `missing` means nothing carries it; `unknown` means no visit arrived *and* the account could not be read, which is not a finding and must never be reported as untagged.
 
-**`fix` says which level to put the missing pairs at, and who can write it.** Not a field name — the levels that platform accepts tagging at, widest first (the widest is the one to prefer: it covers campaigns nobody has created yet), which of them Baker can stage and which the user has to do by hand, and how each field treats a value already in it. That last part is the one people skip and it differs per platform: a Google **campaign** final URL suffix *replaces* the account one rather than merging, LinkedIn's `url-params` call *sets the ad set's whole parameter set* and Baker cannot read back what is in it, and a Meta creative is immutable so a live ad cannot be retagged through Baker at all. `suffix` is only ever the **missing** pairs, so the rule everywhere is the same: read what is there, work out what is missing, write the union. Where `fix` says Baker has no write surface — Microsoft, TikTok, Reddit, Pinterest, Snapchat — that is a request to hand the user with the exact string and the exact screen, never a reason to stop on the platforms it can write. ChatGPT Ads is one Baker can write: its campaign and ad group `--tracking-template` (`baker ads chatgpt campaigns|ad-groups update`), which should carry `campaign_id={campaign_id}&ad_group_id={ad_group_id}&ad_id={ad_id}` — an id that only rides in `utm_campaign` or `utm_content` is reported as that UTM and never as the campaign or the ad, so `--platform chatgpt --role adgroup_id` has nothing to split by.
+**`fix` says which level to put the missing pairs at, and who can write it.** Not a field name — the levels that platform accepts tagging at, widest first (the widest is the one to prefer: it covers campaigns nobody has created yet), which of them Baker can stage and which the user has to do by hand, and how each field treats a value already in it. That last part is the one people skip and it differs per platform: a Google **campaign** final URL suffix *replaces* the account one rather than merging, LinkedIn's `url-params` call *sets the ad set's whole parameter set* and Baker cannot read back what is in it, and a Meta creative is immutable, so a live Meta ad is retagged by `baker ads meta ads retag` (a cloned creative plus a repoint). `suffix` is only ever the **missing** pairs, so the rule everywhere is the same: read what is there, work out what is missing, write the union. Where `fix` says Baker has no write surface — Microsoft, TikTok, Reddit, Pinterest, Snapchat — that is a request to hand the user with the exact string and the exact screen, never a reason to stop on the platforms it can write. ChatGPT Ads is one Baker can write: its campaign and ad group `--tracking-template` (`baker ads chatgpt campaigns|ad-groups update`), which should carry `campaign_id={campaign_id}&ad_group_id={ad_group_id}&ad_id={ad_id}` — an id that only rides in `utm_campaign` or `utm_content` is reported as that UTM and never as the campaign or the ad, so `--platform chatgpt --role adgroup_id` has nothing to split by.
 
 **The one recommendation about the ad account itself.** `baker analytics ads --platform <p>` warns when that platform's traffic carries no campaign id, ad group id or ad id — the three tiers every "which ad worked" question is grouped by — and returns the exact URL suffix, in the platform's own macro language, that would start sending the missing ones. It is the only mapping gap that cannot be fixed afterwards: naming a parameter Baker already captures corrects the history, because roles are resolved when a report is read, but a parameter the ads never sent has no stored values for a meaning to apply to. The hint stays quiet for a platform with little traffic, and defers to the untagged-account finding rather than repeating it.
 
@@ -4308,7 +4470,7 @@ baker chats diff <id> --live              # in-progress Session: read from its l
 ```
 
 **`list` flags:** `--status active|archived|all` (default `all`), `--limit` (1-100, default 20), `--full` (include each Session's full change list).
-**`view`:** returns the unified `effects` — git content (`content`, `creatives`) AND DB-only effects that never touch the repo (`actions`, `scheduledAgents`, `tags`, `ads.{google,meta,linkedin,x}`, `tagManager`, `ga4`, `funnel` (with the ways in it added or removed, `triggersAdded`/`triggersRemoved`), `conversions`, `conversionSends`, `eventSources`), plus `otherChanges` for every other change the Session made (A/B tests, recipes, library images), each resolved to real detail and flagged `staged` (in-progress draft) vs applied. Plus `kickoff`, `outputs` counts, `threads`, `commits`, `diffAvailable`.
+**`view`:** returns the unified `effects` — git content (`content`, `creatives`) AND DB-only effects that never touch the repo (`actions`, `scheduledAgents`, `tags`, `ads.{google,meta,linkedin,x}`, `tagManager`, `ga4`, `funnel` (with the ways in it added or removed, `triggersAdded`/`triggersRemoved`), `conversions`, `conversionSends`, `eventSources`), plus `otherChanges` for every other change the Session made (A/B tests, recipes, library images), each resolved to real detail and flagged `staged` (in-progress draft) vs applied. Plus `kickoff`, `outputs` counts, `threads`, `commits`, `diffAvailable`, and `publish` — what the Publish left behind (`failedTotal`) and the changes that went through but read back differently on the platform afterwards (`unconfirmedTotal`, `surfaces[].unconfirmedChanges`); a hint names either.
 **`transcript` flags:** `--limit` (1-1000, default 100, most recent), `--full` (untruncated text). Returns `entries` (`role` + `text`) and `truncated`.
 **`diff` flags:** `--surface knowledge|company|brand|landings|flows|creatives`, `--full` (patch text per file), `--live` (read an in-progress Session's changes from its live workspace). Returns `available`, `source` (`published`|`live`), `files` (`path`, `surface`, `status`, `additions`, `deletions`, `patch`), and `truncated` when a large live diff was capped.
 

package/dist/account-3H6BZO5H.js

@@ -0,0 +1,80 @@
+import {
+  CHATGPT_ADS_REFERENCE,
+  runChatgptRead
+} from "./chunk-IG627WWY.js";
+import "./chunk-SWL4AAPP.js";
+import {
+  apiGet
+} from "./chunk-XDZVBX6L.js";
+import "./chunk-N5O67GK5.js";
+import "./chunk-EE72SSB2.js";
+import {
+  registerSchema
+} from "./chunk-WNSE7N75.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-AE5IJGGW.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-3H6BZO5H.js.map

package/dist/account-IKFDY52P.js

@@ -0,0 +1,138 @@
+import {
+  handleMetaError,
+  resolveAccountIdArg
+} from "./chunk-QTOZ32SU.js";
+import {
+  writeJsonEnvelope
+} from "./chunk-SWL4AAPP.js";
+import {
+  NO_CACHE_ARG
+} from "./chunk-K3TNTBZJ.js";
+import {
+  apiGet
+} from "./chunk-XDZVBX6L.js";
+import "./chunk-N5O67GK5.js";
+import "./chunk-EE72SSB2.js";
+import "./chunk-WNSE7N75.js";
+import "./chunk-YQSBHWOI.js";
+
+// ../api/src/ads-meta/accountHealth.ts
+var ACCOUNT_STATUS = {
+  1: "ACTIVE",
+  2: "DISABLED",
+  3: "UNSETTLED",
+  7: "PENDING_RISK_REVIEW",
+  8: "PENDING_SETTLEMENT",
+  9: "IN_GRACE_PERIOD",
+  100: "PENDING_CLOSURE",
+  101: "CLOSED",
+  201: "ANY_ACTIVE",
+  202: "ANY_CLOSED"
+};
+var DISABLE_REASON = {
+  1: "ads integrity policy",
+  2: "ads IP review",
+  3: "payment risk",
+  4: "gray account shut down",
+  5: "ads AFC review",
+  6: "business integrity review",
+  7: "permanently closed",
+  8: "unused reseller account",
+  9: "unused account",
+  10: "umbrella ad account",
+  11: "Business Manager integrity policy",
+  12: "misrepresented ad account",
+  13: "legal entity de-share",
+  14: "thread review",
+  15: "compromised ad account"
+};
+var DELIVERS_ANYWAY = /* @__PURE__ */ new Set([1, 9]);
+function statusBlocker(account) {
+  const status = account.account_status;
+  if (status === void 0 || status === 1) return void 0;
+  const name = ACCOUNT_STATUS[status] ?? `status ${status}`;
+  const reason = account.disable_reason ? DISABLE_REASON[account.disable_reason] : void 0;
+  const why = reason ? ` (${reason})` : "";
+  if (DELIVERS_ANYWAY.has(status)) {
+    return `the ad account is ${name}${why}: a payment failed and Meta stops delivery when the grace period ends \u2014 the account owner settles it in Meta Billing`;
+  }
+  return `the ad account is ${name}${why}, so nothing on it delivers \u2014 only the account owner can resolve that with Meta (Account Quality / Billing)`;
+}
+function metaAccountDeliveryBlockers(account) {
+  const blockers = [];
+  const status = statusBlocker(account);
+  if (status) blockers.push(status);
+  const hasFunding = Boolean(account.funding_source || account.funding_source_details?.id);
+  if (!hasFunding && !account.is_prepay_account) {
+    blockers.push(
+      "the ad account has no payment method, so Meta accepts its ads but delivers none (they wait in PENDING_BILLING_INFO) \u2014 the account owner adds one in Meta Billing"
+    );
+  }
+  if (spendCapReached(account)) {
+    blockers.push(
+      "the ad account has reached its spending limit, so Meta stops delivering every ad on it \u2014 an admin raises or removes the limit in Meta Billing \u2192 Payment settings, or Baker can change it as part of a chat"
+    );
+  }
+  return blockers;
+}
+function spendCapReached(account) {
+  const cap = Number(account.spend_cap ?? "0");
+  const spent = Number(account.amount_spent ?? "0");
+  return Number.isFinite(cap) && Number.isFinite(spent) && cap > 0 && spent >= cap;
+}
+
+// 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) and whether it can deliver:
+a hint names a disabled account or a missing payment method, which Meta never refuses at publish \u2014 its ads just never run.
+\`bakerPermissions\` says which per-company Meta permissions (leadAds, catalog, pagePosts) are switched on for this
+company and held by the connection; a hint names any that still needs the user to reconnect Meta.
+
+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);
+      const permissionHints = data.bakerPermissions ? accountPermissionHints(data.bakerPermissions) : [];
+      writeJsonEnvelope({ ok: true, data, hints: [...accountDeliveryHints(data), ...permissionHints] });
+    } catch (err) {
+      handleMetaError(err);
+    }
+  }
+});
+function accountDeliveryHints(account) {
+  const blockers = metaAccountDeliveryBlockers(account);
+  if (blockers.length === 0) return ["The account can deliver: it is active and has a payment method."];
+  return [
+    ...blockers.map((blocker) => `Cannot deliver: ${blocker}.`),
+    "Staging still works and publishing still applies the changes, but nothing serves until this is fixed \u2014 tell the user before they publish anything they expect to run."
+  ];
+}
+var PERMISSION_LABEL = {
+  leadAds: "Lead ads (instant forms and their leads)",
+  catalog: "Catalog changes",
+  pagePosts: "Facebook Page posts"
+};
+function accountPermissionHints(permissions) {
+  return Object.keys(PERMISSION_LABEL).filter((key) => permissions[key].reconnectNeeded).map(
+    (key) => `${PERMISSION_LABEL[key]}: switched on for this company, but this Meta connection predates it \u2014 ask the user to reconnect Meta in the dashboard before relying on it.`
+  );
+}
+export {
+  accountCommand,
+  accountDeliveryHints,
+  accountPermissionHints
+};
+//# sourceMappingURL=account-IKFDY52P.js.map

package/dist/account-IKFDY52P.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../api/src/ads-meta/accountHealth.ts","../src/commands/ads/meta/account.ts"],"sourcesContent":["/**\n * Whether a Meta ad account can deliver at all — read off the account node.\n *\n * Meta stages and publishes ads on an account that cannot pay or is disabled\n * without a word: the docs say an account with no funding source can \"still\n * create ads but these ads will get no delivery\", and they sit in\n * PENDING_BILLING_INFO. Nothing in the publish answer says so, so the only\n * place to catch it is a read of the account before something goes live.\n */\n\n/** The account fields this reads (all in `ACCOUNT_FIELDS`). */\nexport interface MetaAccountHealthFields {\n  account_status?: number;\n  disable_reason?: number;\n  funding_source?: string;\n  funding_source_details?: { id?: string; display_string?: string; type?: number } | null;\n  is_prepay_account?: boolean;\n  /** Minor units as a string; \"0\" is no limit. */\n  spend_cap?: string;\n  amount_spent?: string;\n  /** What the person whose connection Baker uses may do on the account (MANAGE, ADVERTISE, ANALYZE, DRAFT). */\n  user_tasks?: string[];\n}\n\n/** `account_status` values, from the Ad Account reference (v25.0). 1 is the only one that delivers. */\nconst ACCOUNT_STATUS: Readonly<Record<number, string>> = {\n  1: \"ACTIVE\",\n  2: \"DISABLED\",\n  3: \"UNSETTLED\",\n  7: \"PENDING_RISK_REVIEW\",\n  8: \"PENDING_SETTLEMENT\",\n  9: \"IN_GRACE_PERIOD\",\n  100: \"PENDING_CLOSURE\",\n  101: \"CLOSED\",\n  201: \"ANY_ACTIVE\",\n  202: \"ANY_CLOSED\",\n};\n\n/** Why an account is disabled, when it is (`disable_reason`). */\nconst DISABLE_REASON: Readonly<Record<number, string>> = {\n  1: \"ads integrity policy\",\n  2: \"ads IP review\",\n  3: \"payment risk\",\n  4: \"gray account shut down\",\n  5: \"ads AFC review\",\n  6: \"business integrity review\",\n  7: \"permanently closed\",\n  8: \"unused reseller account\",\n  9: \"unused account\",\n  10: \"umbrella ad account\",\n  11: \"Business Manager integrity policy\",\n  12: \"misrepresented ad account\",\n  13: \"legal entity de-share\",\n  14: \"thread review\",\n  15: \"compromised ad account\",\n};\n\n/**\n * In grace period, Meta still delivers while a failed payment is retried, so\n * it is a warning that delivery is about to stop rather than a stop.\n */\nconst DELIVERS_ANYWAY = new Set([1, 9]);\n\nfunction statusBlocker(account: MetaAccountHealthFields): string | undefined {\n  const status = account.account_status;\n  if (status === undefined || status === 1) return undefined;\n  const name = ACCOUNT_STATUS[status] ?? `status ${status}`;\n  const reason = account.disable_reason ? DISABLE_REASON[account.disable_reason] : undefined;\n  const why = reason ? ` (${reason})` : \"\";\n  if (DELIVERS_ANYWAY.has(status)) {\n    return `the ad account is ${name}${why}: a payment failed and Meta stops delivery when the grace period ends — the account owner settles it in Meta Billing`;\n  }\n  return `the ad account is ${name}${why}, so nothing on it delivers — only the account owner can resolve that with Meta (Account Quality / Billing)`;\n}\n\n/**\n * Plain reasons this account will not deliver, empty when it can. Each names\n * who can fix it, since nothing Baker stages can.\n */\nexport function metaAccountDeliveryBlockers(account: MetaAccountHealthFields): string[] {\n  const blockers: string[] = [];\n  const status = statusBlocker(account);\n  if (status) blockers.push(status);\n  const hasFunding = Boolean(account.funding_source || account.funding_source_details?.id);\n  if (!hasFunding && !account.is_prepay_account) {\n    blockers.push(\n      \"the ad account has no payment method, so Meta accepts its ads but delivers none (they wait in PENDING_BILLING_INFO) — the account owner adds one in Meta Billing\",\n    );\n  }\n  if (spendCapReached(account)) {\n    blockers.push(\n      \"the ad account has reached its spending limit, so Meta stops delivering every ad on it — an admin raises or removes the limit in Meta Billing → Payment settings, or Baker can change it as part of a chat\",\n    );\n  }\n  return blockers;\n}\n\n/** `spend_cap` \"0\" (or absent) is no limit; a limit reached stops all delivery until it is raised. */\nfunction spendCapReached(account: MetaAccountHealthFields): boolean {\n  const cap = Number(account.spend_cap ?? \"0\");\n  const spent = Number(account.amount_spent ?? \"0\");\n  return Number.isFinite(cap) && Number.isFinite(spent) && cap > 0 && spent >= cap;\n}\n\n/** Statuses on which Meta takes no new ads or edits: only the account owner and Meta can change them. */\nconst REFUSES_WRITES = new Set([2, 101]);\n\n/** Where an account owner reads why Meta restricted an account and asks for a review. */\nexport const META_ACCOUNT_QUALITY_URL = \"https://www.facebook.com/accountquality\";\n\n/**\n * Why Meta will refuse this change on this account at publish, or `undefined`.\n *\n * Only explicit evidence refuses: an account whose status is missing from the\n * read says nothing. A `removal` (a delete, a pause) is let through, because it\n * takes nothing live and is what someone cleaning up a disabled account does.\n */\nexport function metaAccountWriteRefusal(\n  account: MetaAccountHealthFields,\n  change: \"change\" | \"removal\",\n): string | undefined {\n  return accessRefusal(account.user_tasks) ?? statusRefusal(account, change);\n}\n\n/** Tasks that let a person publish changes on an ad account; ANALYZE and DRAFT do not. */\nconst PUBLISHING_TASKS = new Set([\"MANAGE\", \"ADVERTISE\"]);\n\nfunction accessRefusal(tasks: readonly string[] | undefined): string | undefined {\n  if (!tasks || tasks.length === 0 || tasks.some((task) => PUBLISHING_TASKS.has(task))) return undefined;\n  return 'the person who connected Meta to Baker can only view this ad account, so Meta refuses every change Baker would publish on it — an admin of the ad account gives them the \"Manage campaigns\" permission in Meta Business settings → Ad accounts (https://business.facebook.com/settings/ad-accounts), then this can be staged again';\n}\n\nfunction statusRefusal(account: MetaAccountHealthFields, change: \"change\" | \"removal\"): string | undefined {\n  const status = account.account_status;\n  if (status === undefined || !REFUSES_WRITES.has(status) || change === \"removal\") return undefined;\n  const reason = account.disable_reason ? DISABLE_REASON[account.disable_reason] : undefined;\n  const why = reason ? ` (${reason})` : \"\";\n  return `the ad account is ${ACCOUNT_STATUS[status]}${why}, so Meta refuses new ads and edits on it — only the account owner can resolve that with Meta, in Account Quality (${META_ACCOUNT_QUALITY_URL}); nothing can be staged here until then`;\n}\n","import { type MetaAccountHealthFields, metaAccountDeliveryBlockers } from \"@baker/api/ads-meta/accountHealth\";\nimport type { MetaPermissionStates } from \"@baker/api/ads-meta/permissionGates\";\nimport { defineCommand } from \"citty\";\nimport { NO_CACHE_ARG } from \"../../../cache-flag.ts\";\nimport { apiGet } from \"../../../client.ts\";\nimport { writeJsonEnvelope } from \"../output.ts\";\nimport { handleMetaError, resolveAccountIdArg } from \"./shared.ts\";\n\nexport const accountCommand = defineCommand({\n  meta: {\n    name: \"account\",\n    description: `Show single Meta ad account detail (currency, timezone, balance, business) and whether it can deliver:\na hint names a disabled account or a missing payment method, which Meta never refuses at publish — its ads just never run.\n\\`bakerPermissions\\` says which per-company Meta permissions (leadAds, catalog, pagePosts) are switched on for this\ncompany and held by the connection; a hint names any that still needs the user to reconnect Meta.\n\nExamples:\n  baker ads meta account --account-id act_123\n  BAKER_META_AD_ACCOUNT_ID=act_123 baker ads meta account`,\n  },\n  args: {\n    \"account-id\": { type: \"string\", description: \"Meta ad account ID (act_...)\" },\n    \"no-cache\": NO_CACHE_ARG,\n  },\n  run: async ({ args }) => {\n    const accountId = resolveAccountIdArg(args);\n    try {\n      const params: Record<string, string> = { \"account-id\": accountId };\n      if (args[\"no-cache\"]) params[\"skip-cache\"] = \"true\";\n      const data = await apiGet<\n        Record<string, unknown> & MetaAccountHealthFields & { bakerPermissions?: MetaPermissionStates }\n      >(\"/api/ads/meta/account\", params);\n      const permissionHints = data.bakerPermissions ? accountPermissionHints(data.bakerPermissions) : [];\n      writeJsonEnvelope({ ok: true, data, hints: [...accountDeliveryHints(data), ...permissionHints] });\n    } catch (err) {\n      handleMetaError(err);\n    }\n  },\n});\n\n/** Whether ads on this account can run at all, said once, in the words staging warns with. */\nexport function accountDeliveryHints(account: MetaAccountHealthFields): string[] {\n  const blockers = metaAccountDeliveryBlockers(account);\n  if (blockers.length === 0) return [\"The account can deliver: it is active and has a payment method.\"];\n  return [\n    ...blockers.map((blocker) => `Cannot deliver: ${blocker}.`),\n    \"Staging still works and publishing still applies the changes, but nothing serves until this is fixed — tell the user before they publish anything they expect to run.\",\n  ];\n}\n\nconst PERMISSION_LABEL: Record<keyof MetaPermissionStates, string> = {\n  leadAds: \"Lead ads (instant forms and their leads)\",\n  catalog: \"Catalog changes\",\n  pagePosts: \"Facebook Page posts\",\n};\n\n/** One hint per permission switched on for this company that the current Meta connection does not hold yet. */\nexport function accountPermissionHints(permissions: MetaPermissionStates): string[] {\n  return (Object.keys(PERMISSION_LABEL) as (keyof MetaPermissionStates)[])\n    .filter((key) => permissions[key].reconnectNeeded)\n    .map(\n      (key) =>\n        `${PERMISSION_LABEL[key]}: switched on for this company, but this Meta connection predates it — ask the user to reconnect Meta in the dashboard before relying on it.`,\n    );\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;AAyBA,IAAM,iBAAmD;AAAA,EACvD,GAAG;AAAA,EACH,GAAG;AAAA,EACH,GAAG;AAAA,EACH,GAAG;AAAA,EACH,GAAG;AAAA,EACH,GAAG;AAAA,EACH,KAAK;AAAA,EACL,KAAK;AAAA,EACL,KAAK;AAAA,EACL,KAAK;AACP;AAGA,IAAM,iBAAmD;AAAA,EACvD,GAAG;AAAA,EACH,GAAG;AAAA,EACH,GAAG;AAAA,EACH,GAAG;AAAA,EACH,GAAG;AAAA,EACH,GAAG;AAAA,EACH,GAAG;AAAA,EACH,GAAG;AAAA,EACH,GAAG;AAAA,EACH,IAAI;AAAA,EACJ,IAAI;AAAA,EACJ,IAAI;AAAA,EACJ,IAAI;AAAA,EACJ,IAAI;AAAA,EACJ,IAAI;AACN;AAMA,IAAM,kBAAkB,oBAAI,IAAI,CAAC,GAAG,CAAC,CAAC;AAEtC,SAAS,cAAc,SAAsD;AAC3E,QAAM,SAAS,QAAQ;AACvB,MAAI,WAAW,UAAa,WAAW,EAAG,QAAO;AACjD,QAAM,OAAO,eAAe,MAAM,KAAK,UAAU,MAAM;AACvD,QAAM,SAAS,QAAQ,iBAAiB,eAAe,QAAQ,cAAc,IAAI;AACjF,QAAM,MAAM,SAAS,KAAK,MAAM,MAAM;AACtC,MAAI,gBAAgB,IAAI,MAAM,GAAG;AAC/B,WAAO,qBAAqB,IAAI,GAAG,GAAG;AAAA,EACxC;AACA,SAAO,qBAAqB,IAAI,GAAG,GAAG;AACxC;AAMO,SAAS,4BAA4B,SAA4C;AACtF,QAAM,WAAqB,CAAC;AAC5B,QAAM,SAAS,cAAc,OAAO;AACpC,MAAI,OAAQ,UAAS,KAAK,MAAM;AAChC,QAAM,aAAa,QAAQ,QAAQ,kBAAkB,QAAQ,wBAAwB,EAAE;AACvF,MAAI,CAAC,cAAc,CAAC,QAAQ,mBAAmB;AAC7C,aAAS;AAAA,MACP;AAAA,IACF;AAAA,EACF;AACA,MAAI,gBAAgB,OAAO,GAAG;AAC5B,aAAS;AAAA,MACP;AAAA,IACF;AAAA,EACF;AACA,SAAO;AACT;AAGA,SAAS,gBAAgB,SAA2C;AAClE,QAAM,MAAM,OAAO,QAAQ,aAAa,GAAG;AAC3C,QAAM,QAAQ,OAAO,QAAQ,gBAAgB,GAAG;AAChD,SAAO,OAAO,SAAS,GAAG,KAAK,OAAO,SAAS,KAAK,KAAK,MAAM,KAAK,SAAS;AAC/E;;;ACpGA,SAAS,qBAAqB;AAMvB,IAAM,iBAAiB,cAAc;AAAA,EAC1C,MAAM;AAAA,IACJ,MAAM;AAAA,IACN,aAAa;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAQf;AAAA,EACA,MAAM;AAAA,IACJ,cAAc,EAAE,MAAM,UAAU,aAAa,+BAA+B;AAAA,IAC5E,YAAY;AAAA,EACd;AAAA,EACA,KAAK,OAAO,EAAE,KAAK,MAAM;AACvB,UAAM,YAAY,oBAAoB,IAAI;AAC1C,QAAI;AACF,YAAM,SAAiC,EAAE,cAAc,UAAU;AACjE,UAAI,KAAK,UAAU,EAAG,QAAO,YAAY,IAAI;AAC7C,YAAM,OAAO,MAAM,OAEjB,yBAAyB,MAAM;AACjC,YAAM,kBAAkB,KAAK,mBAAmB,uBAAuB,KAAK,gBAAgB,IAAI,CAAC;AACjG,wBAAkB,EAAE,IAAI,MAAM,MAAM,OAAO,CAAC,GAAG,qBAAqB,IAAI,GAAG,GAAG,eAAe,EAAE,CAAC;AAAA,IAClG,SAAS,KAAK;AACZ,sBAAgB,GAAG;AAAA,IACrB;AAAA,EACF;AACF,CAAC;AAGM,SAAS,qBAAqB,SAA4C;AAC/E,QAAM,WAAW,4BAA4B,OAAO;AACpD,MAAI,SAAS,WAAW,EAAG,QAAO,CAAC,iEAAiE;AACpG,SAAO;AAAA,IACL,GAAG,SAAS,IAAI,CAAC,YAAY,mBAAmB,OAAO,GAAG;AAAA,IAC1D;AAAA,EACF;AACF;AAEA,IAAM,mBAA+D;AAAA,EACnE,SAAS;AAAA,EACT,SAAS;AAAA,EACT,WAAW;AACb;AAGO,SAAS,uBAAuB,aAA6C;AAClF,SAAQ,OAAO,KAAK,gBAAgB,EACjC,OAAO,CAAC,QAAQ,YAAY,GAAG,EAAE,eAAe,EAChD;AAAA,IACC,CAAC,QACC,GAAG,iBAAiB,GAAG,CAAC;AAAA,EAC5B;AACJ;","names":[]}

package/dist/account-VGSYM7LY.js

@@ -0,0 +1,79 @@
+import {
+  csvOrJson,
+  handleLinkedinError,
+  resolveAccountIdArg
+} from "./chunk-TTHM66TA.js";
+import {
+  writeAdsJson,
+  writeAdsOutput
+} from "./chunk-SWL4AAPP.js";
+import {
+  NO_CACHE_ARG
+} from "./chunk-K3TNTBZJ.js";
+import "./chunk-DAO63OOP.js";
+import "./chunk-GXDLWBOY.js";
+import "./chunk-GIWHHCD6.js";
+import "./chunk-XQIOCIDO.js";
+import "./chunk-WTJSMYY2.js";
+import {
+  apiGet
+} from "./chunk-XDZVBX6L.js";
+import "./chunk-N5O67GK5.js";
+import "./chunk-EE72SSB2.js";
+import "./chunk-WNSE7N75.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-FYB6QG7K.js").then((m) => m.accountUrlParamsCommand)
+  },
+  args: accountDetailCommand.args,
+  default: "detail"
+});
+export {
+  accountCommand
+};
+//# sourceMappingURL=account-VGSYM7LY.js.map