@koda-sl/baker-cli 0.481.0-dev.2d33e194f → 0.498.0-dev.e2ca08ce6

package/README.md

@@ -163,79 +163,6 @@ Multi-platform ad commands. Google, Meta, and LinkedIn support both reads and **
 
 ---
 
-### `baker ads performance`
-
-Every connected ad platform's numbers from Baker's stored copy (refreshed every few hours, full history), without calling the platforms. Read-only. Results are the company's chosen conversion goals, else each platform's headline conversions; money is shown in the company's reporting currency at the period's average ECB rate (`--currency <ISO>` for another, `--currency native` for each ad account's own), and comparisons use only days whose conversions have settled.
-
-It is the first read for any ads report, analysis or alert: no rate limit and the whole history, a few hours behind (`status` says how fresh). The live `baker ads <platform>` reads are for today's numbers and what this lacks, and their answers name the synced command that covers the same question.
-
-```bash
-baker ads performance overview --days 30          # spend, results, cost per result per platform, vs the period before
-baker ads performance setup                       # is everything set up: one headline and what to fix, in order
-baker ads performance accounts --days 30          # each ad account against its own target, with its weeks
-baker ads performance attention                   # the few things that matter most now: fix now, worth a look, opportunities
-baker ads performance attention claim <id>        # this chat works on it (at once; lapses when the chat ends)
-baker ads performance attention fixed <id> --note "Cut the budget 20%"   # staged: at Publish it shows "Fixed, checking it worked"
-baker ads performance attention dismiss <id> --wrong --reason "Paused on purpose"   # staged; without --wrong it is "not now"
-baker ads performance entities --level ad --sort cost_per_result
-baker ads performance entities --platforms google --compare   # each row against the settled days before; what stopped, and who stopped it
-baker ads performance entity <id> --platform meta --level ad_group   # one entity + verdict before changing it
-baker ads performance changes --days 14
-baker ads performance impact --actor-kinds baker
-baker ads performance creatives   # each row also names the Baker creative (and version) it is: madeInBaker
-baker ads performance creative-health --sections trending,poor   # trending creatives, poor performers, launch hit rate, freshness
-baker ads performance families --by hook   # launched creatives by winning-ads library family, hook, angle, framework… with real spend and results
-baker ads performance creative-assets --ad-ids <id>   # every version of an ad's pictures and videos, stored at full size
-baker ads performance health --platforms meta   # spend vs last month, cost per result, budget in learning, audiences, copy, frequency
-baker ads performance breakdown --dimension placement   # also country, device; Meta: age, gender, audience_segment
-baker ads performance search-terms --zero-results
-baker ads performance search-terms --term-segments brand --campaign-segments non_brand   # brand searches bought by non-brand campaigns
-baker ads performance brand-split --days 30      # Google Search: brand, competitor and non-brand apart, each against its own target
-baker ads performance impression-share           # per Search campaign: share, lost to budget / ad rank, top of page, change in points
-baker ads performance keyword-quality --max-quality-score 5   # quality score and its parts, and the pages keywords lead to
-baker ads performance google-report --days 7     # every section of a Google Ads review in one read
-baker ads performance budgets                    # monthly budgets and how this month paces against each
-baker ads performance pacing --month 2026-10
-baker ads performance funnel --level campaign
-baker ads performance tracking
-baker ads performance landings
-baker ads performance live-in --landing <slug>   # live campaigns sending people to a landing; --creative <slug> for the ads showing a creative
-baker ads performance goals
-baker ads performance status                     # freshness per account; adsInManyAdGroups names ads counted under two ad groups
-baker ads performance people --level campaign  # who each campaign brought, how far up the ladder, cost per step
-baker ads performance people --level ad --ad-group-ids <id>  # the same, for the ads inside one ad set
-baker ads performance personas --dimension role  # the same people by role, company size, industry...
-baker ads performance ladder                     # the lead-to-customer steps and what they can be made of
-baker ads performance persona-fields             # which Form fields say who people are
-baker ads performance progress --status worsening  # worst first: really getting worse, how sure, and why
-baker ads performance diagnose <id> --platform meta --level campaign   # one entity: what moved, findings, weekly line
-baker ads performance pulse                      # last settled day against the 7 before, per ad account
-baker ads performance anomalies --cpa-spike 0.3  # unusual days in the last 2 settled weeks, what carried them, event health
-baker ads performance recap --days 7             # the week's changes as plain sentences: what, where, who, when
-baker ads performance targets --days 30          # per ad account and event: numbers against the target, what counts as a result
-baker ads performance targets set --platform meta --account 123 --event offsite_conversion.fb_pixel_lead --cost 25 --currency EUR
-baker ads performance targets set --company --roas 3   # the company default; --clear removes a target
-baker ads performance targets unstage --all      # take back what this chat staged
-baker ads performance goals set --platform google --account 456 --count "Lead form" --uncount Calls
-baker ads performance goals name --singular "demo request" --plural "demo requests"   # what the company calls a result; --reset
-baker ads performance budget-recommendations --moves scale,cut   # scale, hold, cut or pause each campaign against the target that judges it (its brand/non-brand target, else its account's, else the default)
-baker ads performance segments                   # the brand and competitor names, a person's choices, segment targets
-baker ads performance segments set --brand "Acme, acme.com" --competitors "Globex"
-baker ads performance segments set --campaign <id> --account <id> --segment brand   # or --term "<term>"; --clear
-baker ads performance segments set --target non_brand --cost 40 --currency EUR
-baker ads performance budgets set --amount 45000 --currency USD   # --platform --account [--segment brand] for one account
-```
-
-Brand, competitor and non-brand are read per search term and keyword by Baker's decision model against the brand and competitor names, and per campaign from what its keywords spent on; a person's choice always wins.
-
-`targets set`, `goals set`, `goals name`, `segments set` and `budgets set` stage on the chat (they need `BAKER_CHAT_ID`) and apply when it is published; a target someone changes in the dashboard meanwhile is kept and the staged one reported as not applied. Event targets are Meta and LinkedIn only — the other platforms cannot split spend by event.
-
-`progress` and `diagnose` judge the last 2 settled weeks against the 4 before, on the metric each entity is for (falling back to cost per click when results are too few), and separate a real decline from a measurement change (`not_comparable`), the market, scaling, fatigue, one child, the landing page and noise, with a confidence.
-
-Compact by default; `--full` returns every field. Errors with `ADS_NOT_CONNECTED` (and a `fix`) when no ad platform is connected.
-
----
-
 ### `baker ads google accounts`
 
 List the Google Ads accounts selected for this company. Run this first to find account IDs.
@@ -462,19 +389,19 @@ The same lines also go to stderr. A read with nothing to report prints none of i
 
 | Preset                 | Description                              | Default date range |
 |------------------------|------------------------------------------|--------------------|
-| `campaign-performance` | Campaign metrics, all conversions included, and bidding type | LAST_30_DAYS |
+| `campaign-performance` | Campaign metrics overview                | LAST_30_DAYS       |
 | `conversions-by-action` | Which conversion action each campaign's conversions actually are | LAST_30_DAYS |
-| `keyword-analysis`     | Keyword performance per ad group, with first-page, top-of-page and first-position CPC estimates | LAST_30_DAYS |
+| `keyword-analysis`     | Keyword performance per ad group         | LAST_30_DAYS       |
 | `keyword-serving`      | Why a keyword is limited — status reasons, first-page bid estimate vs max CPC, quality score | ALL_TIME |
 | `positive-keywords`    | Positive (targeting) keywords only       | ALL_TIME           |
 | `negative-keywords`    | Negative (blocking) keywords only        | ALL_TIME           |
 | `negative-keyword-lists`   | Shared negative lists + their terms  | ALL_TIME           |
 | `negative-list-attachments`| Which campaigns each shared list covers | ALL_TIME        |
-| `search-terms`         | Actual user queries triggering ads, with the match type that matched | LAST_7_DAYS |
-| `ad-copy-performance`  | Every ad's metrics, cost included, with RSA headlines/descriptions | LAST_30_DAYS |
+| `search-terms`         | Actual user queries triggering ads       | LAST_7_DAYS        |
+| `ad-copy-performance`  | Ad headline/description effectiveness    | 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, all conversions included | 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 |
@@ -483,8 +410,6 @@ The same lines also go to stderr. A read with nothing to report prints none of i
 | `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 |
-| `bidding-strategy-performance` | Portfolio bidding strategies: type, status, targets and metrics | LAST_30_DAYS |
-| `conversion-tags`      | Website and call conversions' tracking code (Google tag + event snippet) | — |
 | `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) | — |
@@ -1602,8 +1527,11 @@ baker analytics sources --map --source <id> --field email={{contact.email}} --fi
 baker analytics sources --create-hubspot --property lifecyclestage --value customer   # an event HubSpot keeps for Baker each time the property changes
 baker analytics sources --create-hubspot --property deal_value --operator greaterThan --value 1000   # any condition a Form's filter can say
 baker analytics sources --map --source <id> --field email={{work_email}} --field value={{deal_value}} --field currency=EUR   # repoint a HubSpot read
+baker analytics sources --create-activecampaign --events subscribe,deal_update   # ActiveCampaign's webhook sends these; each is an activecampaign.<event>
 ```
 
+**ActiveCampaign events.** `--create-activecampaign [--events …] [--name …] [--account <id>]` makes a source that ActiveCampaign's own webhook sends to — set up on the account when the chat is published (at once outside a chat), deleted when the source is removed. Each arrival is an event named `activecampaign.<event>` (`activecampaign.subscribe`, `activecampaign.deal_update`, …), about its contact, with the rest of the payload as `properties.*` — the name a scheduled agent on `event.received` is narrowed to.
+
 **Sources: where events reach Baker from a server.** Measure → Sources is three built-in doors — the Baker landings, the website tag, and **the client's own server** — plus the connections Baker reads (HubSpot today). `--server` prints the server's one address: made once, the same for ever, `counting` at once, Baker's own format (`sending-events` is the contract; `X-Baker-Mode: test` rehearses). A HubSpot event is a trigger in HubSpot's own words, kept by HubSpot's journal each time the property changes and counted within a minute. `--create --name <tool>` still makes an address for a tool that cannot be told what to send — its first send is a masked sample counted as nothing until `--map` confirms the rows — but the dashboard no longer offers those; a tool worth reading is a connection, requested from the Sources page. Each `--field` is a **template**: text with `{{path}}` mentions, one thing per mention (`--field currency=EUR` types a value, `--field first_name="{{who.first}} {{who.last}}"` joins two; there is no `{{a|b}}` fallback); a bare path is read as its mention when the sample has it. From then on every arrival is an ordinary event carrying `baker_source: <name>`, listed by `feed --source <name>`, and `--pause`, `--resume` and `--remove` are by `--source <id>`.
 
 **`--preview` then `--create-hubspot --property <name> [--operator <op>] --value <value>… [--name <name>] [--field <field>=<template>…] [--amount-property <n> --currency <c>]`: a HubSpot event.** HubSpot keeps each change to the property for Baker, filtered to the condition — on any plan, nothing to set up in HubSpot, an account of any size — and every contact whose new value satisfies the condition is one event, within a minute, named after the source (default: the trigger's words). The condition is any a Form's filter can say, by the property's kind: `is` / `isNot` (a dropdown, `--value` repeated for several), `contains` / `startsWith` / `endsWith` (text), `greaterThan` / `lessThanOrEqual` … (numbers), `isAfter` / `isBetween` (dates, `YYYY-MM-DD`), `isEmpty` / `isNotEmpty` (any); `--operator` is `is` when unsaid. Names, kinds and operators come from `baker hubspot contacts properties` and row properties from `baker hubspot contacts fields`; `--preview --property … [--operator …] --value … [--field …] [--contact <id or email>]` says how many contacts satisfy it today (NOT counted — only contacts that come to satisfy it from now on are) and returns `preview.record`, the one most recently there or the one asked for, to check every row against before making anything. `--set-trigger --source <id> --property … [--operator …] --value …` changes what an event watches later: the rows stay and `countingSince` moves to now. The connection must be allowed to read contacts, and a refusal names the reconnect. `counting` at once, no URL; the source carries `hubspot { property, propertyLabel, kind, operator, values, valueLabels }`, `countingSince`, `listening` (whether HubSpot has been told to keep its changes: `listening`, `not_configured` or `failed`, with a `detail`), `lastError` and `mapping` — the same field → template table as an address, over the contact's properties plus `{{id}}`, defaulting to HubSpot's standard ones (email, phone, the contact id, name, address, `hs_google_click_id`, `hs_facebook_click_id`); a `--field` row at creation replaces the default it names, `--map --field` replaces the whole set later, and `--amount-property … --currency …` is the short spelling for the `value` and `currency` rows. `--field properties.<name>=<template>` adds an extra property of the event (`--field properties.plan={{plan_tier}}`): it breaks the event down on Measure → Events and a send reads it back as `{{properties.<name>}}`. A deal is watched the same way with `--object deal`, and a lead with `--object lead` (`baker hubspot leads properties|fields`) — where HubSpot records qualification and disqualification as the lead's stage. A deal's or a lead's event is about its contacts (`--contacts every|first`), read as `{{contact.<name>}}`; a lead has no amount. Leads need Sales Hub Professional or Enterprise. Where the event is sent on (Meta, Google Ads…) is `sends`, edited on the event's own card on the Sources page.
@@ -1933,6 +1861,38 @@ baker ga4 draft clear
 
 ---
 
+### ActiveCampaign reads (`baker activecampaign`)
+
+Read the connected ActiveCampaign account live; nothing is stored and nothing in ActiveCampaign changes.
+
+```bash
+baker activecampaign account                                   # contacts, site tracking on/off + tracking account id, allowed domains, event tracking
+baker activecampaign campaigns [--status completed] [--since 2026-09-01] [--limit 20]   # email reports, most recently sent first
+baker activecampaign automations [--active-only]               # on/off, entered/exited, what starts each one
+baker activecampaign contacts [--id <contact id> | --email a@b.com | --tag <id|name> | --list <id|name> | --search <text>] [--limit 20]
+baker activecampaign deals [--pipeline <id|title>] [--stage <id|title>] [--status open|won|lost] [--owner <id|username|email>]
+baker activecampaign pipelines | lists | tags [--search <text>] | fields | users
+```
+
+A contact looked up by `--id` or `--email` also carries its `tags` and its `activity`: custom events, page visits, campaign emails sent, opened and clicked, automation runs and list subscriptions. Campaign rows carry `sends`, `opens`, `uniqueOpens`, `clicks`, `uniqueClicks`, `unsubscribes`, `hardBounces`, `softBounces` and `rates` (`open`, `click`, `unsubscribe` and `bounce` as shares of sends; `clickToOpen` as unique clicks over unique opens; `null` before anything is sent). Deal values are in the currency's major units, and `totals` sums every matching deal per currency. Every command takes `--account <id>` when the company has more than one ActiveCampaign connection, and `--full` adds each row's untouched ActiveCampaign payload as `raw`. Nothing connected answers `NO_ACTIVECAMPAIGN_CONNECTION`, a key ActiveCampaign stopped accepting `ACTIVECAMPAIGN_RECONNECT_REQUIRED` — both with a `request_connection` fix.
+
+### ActiveCampaign changes (`baker activecampaign stage` / `unstage` / `drafts`)
+
+Stage a custom contact field, list, tag or deal pipeline on the connected ActiveCampaign account. Nothing changes in ActiveCampaign until the chat is published; then each change is created — or, when the account already has it (a field by its personalization tag, the rest by name), reused rather than duplicated.
+
+```bash
+baker activecampaign stage field --utm                                   # UTM_SOURCE, UTM_MEDIUM, UTM_CAMPAIGN, UTM_CONTENT, UTM_TERM
+baker activecampaign stage field --title "Plan" --type dropdown --options "Basic,Pro"
+baker activecampaign stage list --name "Webinar sign-ups"
+baker activecampaign stage tag --name "hot-lead"
+baker activecampaign stage pipeline --title "Inbound" --stages "New lead,Qualified,Won" --currency usd
+baker activecampaign drafts [--chat <id>]                                # what is staged; after Publish, what happened to each
+baker activecampaign unstage <ref|name|perstag>                          # drop one staged change
+baker activecampaign unstage --all                                       # drop every staged change
+```
+
+A field is put on every list. Field types: `text`, `textarea`, `date`, `datetime`, `dropdown`, `listbox`, `radio`, `checkbox`, `hidden`; `dropdown`, `listbox`, `radio` and `checkbox` need `--options`. A new pipeline gets exactly `--stages`; an existing one only gains the stages it lacks. Every `stage` takes `--account <id>` when the company has more than one ActiveCampaign connection.
+
 ### Google Search Console (`baker gsc`)
 
 GSC commands for PPC-SEO arbitrage, brand halo analysis, and negative keyword discovery.
@@ -2012,15 +1972,21 @@ Ads start from what customers said. Three commands carry the process; the agent
 ```bash
 baker creatives brief [--adset <id>] [--account-id act_<id>] [--no-research]   # one read: viewer, account bottleneck, what works, taste, customer quotes, ideas on file
 baker creatives ideas [--full]                                 # check and rank src/creatives/_ideas/*.md; build_next
-baker creatives make <idea> [--slug <s>] [--adset <id>] [--reference <adId> [--platform meta|linkedin|tiktok|google]] [--spec <beats.json>] [--from-idea] [--series <lead>]
+baker creatives make <idea> [--slug <s>] [--adset <id>] [--reference <adId> [--platform meta|linkedin|tiktok|google]] [--avatar <handle>] [--spec <beats.json>] [--from-idea] [--series <lead>]
 baker creatives translate --slug <ad> --to es-MX,es-CO,pt-BR [--copy-file <json>] [--note "<brief>"] [--again]   # the same ad in other languages, one design
 baker creatives learn [--days <n>] [--dry-run]                 # what each idea's ads did, written back onto the idea
+baker creatives rules list [--kind static|video] [--product <slug>] [--all]   # the company's standing rules for every ad
+baker creatives rules add --candidate <rc-…> | --text "<rule>" --strength never|must|prefer --applies <what> …   # a rule the person agreed to
+baker creatives rules retire <id> [--by <id>|BRAND.md]
+baker creatives check [--slug <s>]                             # which ads already made break a rule now in force
 ```
 
+- **Creative rules.** Every step of an ad reads one company (`engine/creative-context`): its reading of COMPANY.md (cached per edit), its BRAND.md (name, fonts, colours, voice, imagery, logo usage) and the rules that hold for the ad: BRAND.md's own (read by `google/gemini-3.5-flash`, cached per BRAND.md edit) and the ones a person taught, one file each in `src/content/creative-rules/`. Rules are read when a call runs, never copied into an ad's files; the compiled prompts carry them in a `<company_rules>` block the source fingerprint leaves out, so a rule edit re-renders on the next run and marks nothing stale. A never or a must is held before anything renders on the ad's words (`rule_broken`: whole phrases, accents, case and spacing folded, in the rule's language) and on its cast (`cast_not_decided` for an Avatar made for a role under a rule that only real people appear), and after on the finished ad: the rules a person taught are checked on a static's sizes and a video's frames by a vision model (each blocking break given a second look), and a video's voice, sound and subtitle rules by the watch pass. BRAND.md's rules are told to every render and its banned words are checked, but they never block a finished ad by eye. An ad departs from a rule only through `waive` in its prompt.json, which the source fingerprint covers; a rule three ads waive is flagged to retire. `feedback record` drafts the rules a rejection's words state for every ad (`ruleCandidates`, only where the words say it holds beyond this ad) and names reasons repeated across ads; `rules add` saves one only once the person agreed, after checking it duplicates and contradicts none of theirs, catches the version it came from and blocks none they approved. Each run record names the rules it was made against (`rules: { digest, ids }`). A correction (`--fix`, the spec repair) also reads the creative's case file: every rejection on it, in the person's words.
+
 - `brief` returns a verdict, not raw numbers: `account.bottleneck` is `hook`, `after_click`, `none` or `too_little_data`. A part that cannot be read says `unavailable`; the market searches (the followed brands, and the library for what COMPANY.md's first line says the company sells, in a few words) run at once and get 12 seconds, so a slow ad library leaves them out rather than holding the brief. With few customer quotes on file it runs `research customers` itself alongside the reads (about 30 s) and returns what it wrote; `--no-research` skips that. With no ideas on file, its hint lists the values `awareness`, `angle` and `format` take. `market` says what competitors' ads already say (the followed brands, else the library), how sophisticated the market is, and which awareness stages nobody speaks to.
 - `ideas` is local and nearly free: two readings of the words go to the decision model (a fraction of a cent, billed with the workspace's next run, answers kept in `canvas/.cache/`). An insight filed as `observed` reads as `interpreted` when its source cannot be opened or its quote is a statistic about people rather than someone's words ("39% de los propietarios…"), and a new idea is warned when its message says what a failed idea said, however reworded or translated. Without an answer, an insight keeps its status and only the same words count as the same message. An idea's `evidence` resolves to `src/content/insights/` entries, or it is an `explore` bet. Numbers must be in the Knowledge or our own customers' quotes (a Reddit, forum or web quote never sources a claim), no two ideas may share an angle and format, and a review or testimonial format needs a quote from our own customer.
 - `learn` pools each built idea's creatives, judges them against the rest of the account's cost per result and writes `status` (`winner`, `failed`, `inconclusive`, `testing`) and a frozen `result` onto the idea. `ideas` then warns when a new idea repeats a failed one.
-- `make` builds one idea, on a proven winning ad whenever one fits. A static searches the idea's container on the idea's message for our viewer, then for the container's strongest winners from any category (no query, by winner score), pools the candidates (each ad once, the better search first), checks up to six with `winning-ads fit`, three at a time (the next only once one does not fit), and keeps the best-ranked one that fits as soon as it and every better one have answered. The fit says what made that ad a winner, so what the creative carries of it (`reference.carry`: `whole_ad`, `layout`, `hook` or `angle`); make seeds it into `prompt.json` as `concept`, the canvas keeps the ad as its `original` node, and the renders see it for its structure only at `whole_ad` or `layout`. The first hint names the ad and what it carries (for a `--reference` chosen by hand, only the ad: nothing checked what made it win); if the concept could not be written into `prompt.json`, a hint says so and how to write it from the fit already made. For a new creative it starts scaffolding the best-ranked one while the fits are asked (kept when it fits, stopped and removed whole when another or none is kept). Finding, checking and describing a reference gets 150 seconds; past that the build is stopped and the static starts from the idea (`REFERENCE_SLOW`). A creative whose ad is already written is never built over (`ALREADY_MADE`): edit its `prompt.json`, or pass `--slug` for another ad of the same idea. A video idea takes its beats spec. Either way it records the idea on `_definition.md`, sets `prompt.json`'s `message` and syncs the definition. Drafted copy lines claiming a figure the company never wrote come back first in `hints`. Only when no proven ad fits (or with `--from-idea`) does a static start from the idea itself, and the first hint says why (none in the container, what the ones checked won on that the company lacks, the time ran out, or the proven ad it picked could not be read; a `--reference` chosen by hand that cannot be read fails instead): `prompt.json` holds the message and placeholders, and `canvas run` refuses to render until the scene and copy are written.
+- `make` builds one idea, on a proven winning ad whenever one fits. A static first reads a reference brief: one small model (`google/gemini-3.5-flash-lite`, about a second, cached per company notes and idea under `canvas/.cache/reference-brief/`) reads COMPANY.md and the idea and says what this ad sells, its industry and its people in the plain English the library files ads under, the market it runs in, who buys (consumer, small business, enterprise), whether the brand jokes (these and its own brand names from the company's reading, read once per COMPANY.md), what its rules forbid (its never-rules), and up to four wider searches, closest first (an adjacent product the same buyer weighs, the same buyer buying something else, the same kind of decision: for a padel-court builder, tennis courts, sports club owners, turnkey business investment). Without an answer it falls back to COMPANY.md's first line, its market line (English, Spanish, French, German or Italian) and the persona. It then searches for ads of what this ad sells, in its market and then anywhere, first in the idea's container for our viewer and then in any static container; then ads made for the same people whatever they sell; then the wider searches; then ads of the broader industry; then the idea's message; then the container's strongest winners from any category (no query, by winner score), in the market and then anywhere (a search that fails is asked once more; when every search for this ad's topic fails, the library's browse of any category's winners is never built on: the static starts from the idea, `REFERENCE_SEARCH_UNAVAILABLE`, and make can be run again later). It pools the candidates (one ad per brand, the better search first, ads whose run barely proves them after the proven ones, the company's own ads left out), reads up to 24 of them against the ad being made with the decision model (made for our kind of buyer? would our viewer see themselves in it? could our brand run something like it?) and checks the best six in that order, checks up to six with `winning-ads fit`, three at a time, each judged for the ad being made (the idea's persona from the Knowledge, its message, awareness, angle and the customers' words it cites; a reference the fit says our viewer would scroll past does not fit, and a fit made for one idea is never reused for another) (the next only once one does not fit), and, when more than one fits, looks at all of them side by side for the viewer (`~google/gemini-pro-latest`, one call) and keeps the one it prefers, saying why (`reference.chosen_because`, also in the first hint and the thinking's first read). The same look says, as a media buyer would, which element our ad takes from which of them (the hook, the visual, who appears, the proof, the layout, the call to action) and what it must not copy (a fake news page, dated urgency, another brand's marks); every picture is saved under `canvas/references/` and the thinking lays them out as a question to settle; measured on 14 production companies, judged blind by another model, the reference kept went from 5.0 to 6.9 out of 10. The fit says what made that ad a winner, so what the creative carries of it (`reference.carry`: `whole_ad`, `layout`, `hook` or `angle`); make seeds it into `prompt.json` as `concept`, the canvas keeps the ad as its `original` node, and the renders see it for its structure only at `whole_ad` or `layout`. The first hint names the ad and what it carries (for a `--reference` chosen by hand, only the ad: nothing checked what made it win); if the concept could not be written into `prompt.json`, a hint says so and how to write it from the fit already made. For a new creative it starts scaffolding the best-ranked one while the fits are asked (kept when it fits, stopped and removed whole when another or none is kept). Finding, checking and describing a reference gets 150 seconds; past that the build is stopped and the static starts from the idea (`REFERENCE_SLOW`). A creative whose ad is already written is never built over (`ALREADY_MADE`): edit its `prompt.json`, or pass `--slug` for another ad of the same idea. A video idea takes its beats spec. Either way it records the idea on `_definition.md`, saves a proven ad's picture under `canvas/references/`, writes a `## Thinking` outline into its body (open `[TODO: …]` questions, the first sending the agent to that picture, seeded with the fit's read: what the reference is and why it won, or why the bet should work; whether it fits the viewer; our hook; the angle and the call to action; who appears and what we show, listing what the company has: its ready Avatars (real people and ones made for a role), up to three customers' own words for this message from the testimonials, how to make the founder's Avatar, where to get product pictures, and its logos, and closing with three decision lines, `- Cast:`, `- Product shown:`, `- Logo:`; what must survive; the plan, which settles the format when the proven ad's container differs from the idea's), sets `prompt.json`'s `message` and `viewer.who` (the idea's persona, title and segment, never a placeholder: the image prompt, the casting check and the viewer check read it) and syncs the definition. `canvas run` and `canvas validate` refuse to render while a thinking question is open (`definition_not_thought`), so the definition is thought before the ad is written; a creative made before the outline existed is never asked. They also refuse a cast that is not ours (`cast_not_decided`): the cast must be an Avatar (`@handle`), a real customer, real footage or nobody, the product a library picture, a capture, a Hyperframe, footage or none, the logo a brand file or none; and on a static, an Avatar cast must be one `prompt.json` grounds a person on. `--avatar <handle>` (`@eduard` or `eduard,lucia`) casts the ad's people as those Avatars: run again with it once the thinking decides, before `prompt.json` is written; it rebuilds the canvas and keeps the thinking. Drafted copy lines claiming a figure the company never wrote come back first in `hints`. Only when no proven ad fits (or with `--from-idea`) does a static start from the idea itself, and the first hint says why (none in the container, what the ones checked won on that the company lacks, the time ran out, or the proven ad it picked could not be read; a `--reference` chosen by hand that cannot be read fails instead): `prompt.json` holds the message and placeholders, and `canvas run` refuses to render until the scene and copy are written.
 - `make --series <lead>` makes a static idea as another ad of a series: several messages in one style. Nothing is searched or rendered; the ad's `_definition.md` names its lead (`series: <lead>`), its `prompt.json` starts as the lead's ready version with the idea's message, and only its `copy` is written. Its canvas is written from the lead's on every run: the lead's finished picture with this ad's words, every other size the lead's own size with the same words. `baker canvas run --series <lead>` renders every ad of the series at once, one reviewed and corrected run each, skipping an ad already ready from the lead's current version.
 - `translate --slug <ad> --to <langs>` makes the ad in other languages as ads of the series it leads: one creative per language or country variant, `<ad>-<lang>` (the BCP-47 tag in lowercase: `-es-mx`), whose `_definition.md` says `series: <ad>` and `language: <lang>` (canonical case, `es-MX`, as the spec's market and the dashboard store it; tags are compared without case) and whose `prompt.json` is the ad's as last drawn with its words translated. Every language is translated in one text call (transcreated, each regional tag in that country's own variety and form of address, `es-MX` and `es-CO` two ads, each line keeping its role and about its length, brand names, prices and numbers kept, a customer's quote and the name on it never translated, and the ad's `message` translated with the lines; the spend is billed with the workspace's next run), or read from `--copy-file`: `{"<lang>": ["line 1", …]}` is every line with no model call, `{"<lang>": {"headline": "…", "3": "…"}}` only the lines given (by role or number), the model writing the rest. `--note` is the agent's brief for the translator (tone, form of address, terms to keep). Each made language lists the lines it `kept` as a customer said them, and the answer warns when the ad's `prompt.json` changed after its last render, since translations are made from the version rendered. The ad may itself be an ad of a series (an angle ad), so angles × languages stay one design. A language already made is left as it is, so adding one later re-renders nothing; `--again` translates it again. Then `baker canvas run --series <ad>` renders them; a new version of the ad reaches every language on the next `--series` run.
 
@@ -2634,7 +2600,7 @@ baker images screenshot https://competitor.com/pricing --context "Competitor pri
 
 ### `baker images library <query>`
 
-Search the company library (hybrid BM25 + vector + Cohere rerank). Use this FIRST before any external provider.
+Search the company library (hybrid BM25 + vector + rerank). Use this FIRST before any external provider.
 
 ```bash
 baker images library "hero banner"
@@ -2665,7 +2631,7 @@ Fanout image search: library first, then opted-in providers in parallel.
 
 ```bash
 baker images find "office" --sources library,pexels,pixabay --limit 20
-baker images find "office" --sources library,pexels --fallback --threshold 0.4
+baker images find "office" --sources library,pexels --fallback
 baker images find "celebration" --sources library,giphy --auto-ingest 3
 ```
 
@@ -2678,7 +2644,7 @@ Providers: `library`, `pexels`, `pixabay`, `google`, `iconify`, `giphy`, `pinter
 | `--sources`      | Comma-separated providers (default `library`)                                              |
 | `--limit`        | Max results per group (default 20, max 50)                                                 |
 | `--fallback`     | Skip external providers when the top library score ≥ `--threshold`                         |
-| `--threshold`    | Library score floor for `--fallback` (default `0.4`)                                       |
+| `--threshold`    | Library score floor for `--fallback` (default `0.6`)                                       |
 | `--auto-ingest`  | Ingest top N external hits into the library (0–20, default 0) and return Baker-owned URLs on ingested hits |
 | `--context`      | Free-text hint passed to Gemini describe to bias the generated description and tags (overrides provider-derived context on auto-ingest paths) |
 
@@ -3575,7 +3541,7 @@ Search the **ad-dna** corpus of scored "winning" competitor ads for reference cr
 
 > Replaces the old `baker ads google library` tree, which has been removed. Competitor-by-keyword discovery still lives at `baker research advertisers`.
 
-`baker winning-ads profile <advertiserId>` returns what one brand is doing: an estimated spend in USD (a range over every ad since `since`, the last 30 days, and a minimum, split by channel in `by_platform` — a channel that publishes no delivery is marked `unpriced`; `ads_counted` says how many ads were measured, estimated from similar ads, or not counted for lack of reach), what it launched lately and which of those still run, the concepts it tested and the version it kept, its format and platform mix, top landing pages, audiences and similar brands. `--platform` narrows it, `--full` returns everything. `baker winning-ads launches [--since 7] [--advertiser a,b]` lists what the followed brands (or the named ones) launched in the last N days and which still run.
+`baker winning-ads profile <advertiserId>` returns what one brand is doing: an estimated spend in USD (a range over every ad since `since`, the last 30 days, and a minimum, split by channel in `by_platform` — a channel that publishes no delivery is marked `unpriced`; `ads_counted` says how many ads were measured, estimated from similar ads, or not counted for lack of reach), what it launched lately and which of those still run, the concepts it tested and the version it kept, its format and platform mix, top landing pages, audiences and similar brands. `--platform` narrows it, `--full` returns everything. `baker winning-ads launches [--since 7] [--advertiser a,b]` lists what the followed brands (or the named ones) launched in the last N days and which still run. Both say, for every launch, whether it was a `new` idea, another version of one still in `testing`, or a version built on a `winner` the brand had already kept; the profile also counts new ideas per week and `unique_ideas` overall.
 
 `baker winning-ads landings <advertiserId>` lists every landing page the brand's ads point to, most ads first, with how many ads point there, how many still run, the platforms and when each was last used. `address_only` marks an address only Google search ads print: Google publishes no search ad's destination, so it may not be a real page and is never analysed. `--analyse` studies the top 5 pages not analysed yet (`--pages a,b` to name them): each page's headline, value propositions, offer, pricing, calls to action, proof, audience and sections in order. Analysis takes a few minutes per page and is shared by every company, so a page analysed once is ready for all. `--platform` narrows it, `--full` returns every field.
 
@@ -3630,6 +3596,7 @@ baker winning-ads search "delivery driver recruitment" --audience-temperature 0_
 | `--first-seen-after` / `--first-seen-before` | ISO date (`2026-01-01`, read as the start of that day in UTC) or datetime bounds (recency) |
 | `--hook-archetype <list>` | Narrow to ads on a proven hook **seed** (from `winning-ads hooks`) |
 | `--format-pattern <list>` | Narrow to statics in these containers (from `winning-ads formats`, e.g. `comparison_table`) |
+| `--partnership only\|exclude` | `only` = just Meta partnership ads (the brand ran it with a creator or another brand); `exclude` = the brand's own ads. Every partnership row carries `partnership: true` and the `partner` it was run with |
 | `--diverse` | One varied page (different brands, containers, hooks) instead of rank order; ignores paging |
 | `--all-kinds` | Also return Google search text, Shopping and app ads. By default only designed pictures and videos come back; `--format text` (or a query asking for search ads) returns search ads alone |
 | `--output json\|md\|files` | Output format (default json) |
@@ -3839,10 +3806,6 @@ baker scheduled-agents unstage <id-or-temp_agent_id>            # everything thi
 baker scheduled-agents unstage <id-or-temp_agent_id> --index 2  # one staged change only
 
 baker scheduled-agents run <id>
-
-baker scheduled-agents templates --list                  # every recipe this company can run
-baker scheduled-agents templates --category measurement  # one group only
-baker scheduled-agents create --template baker-ads --name "Weekly ad review" --description "..." --cron "0 8 * * MON"
 ```
 
 Triggers:
@@ -3859,8 +3822,6 @@ Triggers:
 | `experiment.concluded` | The winner has been moved into the page | `--experiment <id>` |
 | `task.completed` | A Task is closed | `--tag <slug>` |
 | `task.claimed` | An agent picks up a Task | `--tag <slug>` |
-| `ad_alert.opened` | Baker raises an ad alert (new, back, or a fix that did not hold) | `--ad-account <platform>:<id>`, `--alert <rule>` |
-| `ad_alert.claimed` / `ad_alert.fixed` / `ad_alert.closed` | An ad alert is picked up, marked fixed, or leaves the list (`how` says why) | `--ad-account`, `--alert` |
 
 Rules:
 
@@ -3872,39 +3833,12 @@ Rules:
 - `--occurrences 1` runs only the first time the trigger ever fires; `--occurrences 1,3` the first and the third. Omit it to run every time. It counts firings of this item's trigger, so a firing that `--occurrences` declines is still counted.
 - A signal-triggered item will not start a second run while its last one is still going, and never wakes itself.
 - `--prompt` is the whole job: there is no mode and no `--spawn-agent`. If a run should only advise, the brief says so.
+- Keep `--prompt` to five to eight schematic lines: `Goal:`, `Tools:` with each tool tagged (`@[Google Ads](integration:google-ads)`, `@[Gmail](mcp:gmail)`, `/skill`), numbered steps with the exact `baker` commands and flags, and `Report:`. A brief over 1,500 characters comes back with a hint to shorten it.
 - Publishing every run's work unreviewed is a standing authorization only the user can grant, on the item in Baker. The API refuses `autoPublish` outright.
 - Draft-created ids use `temp_agent_*`; use them with `get`, `update`, or `delete` before publish.
 - Staged commands require `BAKER_CHAT_ID` to point to an `in_progress` chat.
 - `run` rejects `temp_agent_*` and only accepts published ids. It returns the `chatId` of the Session it opened.
 - Company Timezone is the default; `--timezone` is an explicit IANA override.
-- `--template <id>` copies a marketplace recipe's brief onto the item — a copy, not a link, so the owner can read and edit every word, and a later change to the recipe does not reach it. `--prompt` is appended after it. The same recipe can be used more than once.
-
-#### Marketplace recipes (`templates`)
-
-`templates` lists every recipe a company can build an item from — the ones Baker maintains plus any the company wrote — and is also how one of theirs is written. Recipes we maintain take priority: a company recipe can never use one of our ids, and resolution reads ours first.
-
-```bash
-baker scheduled-agents templates --list --drafts        # include theirs not offered yet
-
-# Writing one of theirs, in this order:
-baker scheduled-agents templates --save weekly-posthog-check \
-  --name "Weekly PostHog check" \
-  --tagline "What moved in the funnel, from PostHog rather than GA4." \
-  --recipe-category measurement --frequency weekly \
-  --brief-file ./brief.md
-
-# ...build an item from it with --template, run that item, read what it produced, then:
-baker scheduled-agents templates --publish weekly-posthog-check
-baker scheduled-agents templates --delete weekly-posthog-check
-```
-
-- **Saving does not offer it.** A saved recipe is invisible and cannot be scheduled until `--publish`. The step between the two is running it: nothing enforces that, and it is the only way to know it produces anything worth reading.
-- **`--publish` refuses what it can check**: a brief too short to run unattended, a cadence or category that does not exist, an id that shadows one of Baker's, and a brief naming no source this company has connected. The problems come back as text addressed to the agent.
-- **Only company-wide and organization-wide connections count.** A run fires unattended, so a tool one person connected for themselves works in the chat where the recipe was written and returns nothing every run after that.
-- **Prefer `--brief-file`** over `--brief`: shell quoting eats apostrophes and newlines, and the brief is the whole recipe.
-- **Publishing stages**, like every other Session effect. The recipe reaches the marketplace when the chat is published and is listed there as a change; discarding the chat leaves the marketplace as it was. `BAKER_CHAT_ID` is required for `--save`, `--publish` and `--delete`.
-- **A company's own starts on Recommends** and offers every cadence. The company changes that from its Marketplace tab.
-- **`--delete` stops any schedule still pointing at it** — the response says how many.
 
 ---
 
@@ -3958,13 +3892,14 @@ baker flows options calendly                        # what a step/destination ca
 baker flows connect contact --node book --resource <id>          # fill a Calendly/SavvyCal/GoHighLevel step yourself
 baker flows connect contact --side-effect se-gsheet-1 --resource <spreadsheetId>   # a sheet Baker can reach (--tab to pick the tab)
 baker flows connect contact --side-effect se-gsheet-1 --new-sheet "Contact leads" --columns "Name,Email"   # create one and wire it
-baker flows connect contact --side-effect se-pipedrive-1         # Pipedrive / GoHighLevel contact: the account is the destination
+baker flows connect contact --side-effect se-pipedrive-1         # Pipedrive / GoHighLevel / ActiveCampaign contact: the account is the destination
 baker flows connect contact --side-effect se-email-1 --email "ana@x.com, luis@x.com" --subject "New lead — Contact"   # an email destination: the agent states it, never a card
 baker flows connect contact --side-effect se-httpWebhook-1 --url https://hooks.example.com/lead   # a webhook that needs no token
 baker flows connect contact --all --type googleSpreadsheet --same-as madrid:se-gsheet-1   # copy another Form's destination
 baker flows map contact --from map.json --write     # a whole mapping at once — past ~3 fields, use this
 baker flows map contact --map A=nombre --write      # one or two fields
 baker flows map contact --hubspot-form <guid> --from map.json --write   # HubSpot: field types read off the form
+baker flows map contact --map email=email --map 'tags="withbaker-"+tracking:page_path' --write   # ActiveCampaign: fields read off the account; tag each lead with its page
 baker flows map contact --side-effect <id> --hubspot-form <guid> --prune-missing --write   # drop dead mappings
 baker flows map contact --from map.json --replace --write   # the slot becomes exactly this; drops everything not named
 baker flows normalize contact --write              # repairs a nulled optional; runs pre-commit anyway
@@ -3974,13 +3909,13 @@ Notes:
 
 - **`schema` takes the kind as an argument because `hubspot` is both** — a node type (embeds a form on the page) and a side-effect type (fires a behavioural event). They are different things with one name.
 - **`connect` wires a HubSpot form without asking the user.** When HubSpot is connected and the agent knows which form is meant, `baker flows connect <slug> --hubspot-form <formId> [--side-effect <id>]` attaches the account and the form to a `hubspotForm` side effect (`--all`: every one in the Form still missing it, never repointing one already wired) — the same thing the chat card writes, sealed by Baker so the config never passes through the agent. It refuses a form with spam prevention (captcha) on, and returns `destination.formGuid` for `map --hubspot-form`. The card (`request_flow_input`) stays for an unconnected account or an ambiguous choice.
-- **`options` + `connect` do the same for every other connected platform.** `baker flows options <kind>` lists what the connected account holds (Calendly events, SavvyCal links, GoHighLevel calendars and forms, the Google spreadsheets Baker can reach); `connect --node|--side-effect <id> --resource <id>` writes exactly what the card would. Pipedrive and a GoHighLevel contact take no resource. `--new-sheet` creates a spreadsheet in the connected Google account (Google only lets Baker reach sheets it created or the user chose), `--same-as <slug>:<id>` copies another Form's wired destination, `--all --type <kind>` fills every unwired one of a kind. Nothing connected answers `NOT_CONNECTED` with the `request_connection` fix; several accounts connected need `--account <id>`.
+- **`options` + `connect` do the same for every other connected platform.** `baker flows options <kind>` lists what the connected account holds (Calendly events, SavvyCal links, GoHighLevel calendars and forms, the Google spreadsheets Baker can reach); `connect --node|--side-effect <id> --resource <id>` writes exactly what the card would. Pipedrive, a GoHighLevel contact and an ActiveCampaign contact take no resource. `--new-sheet` creates a spreadsheet in the connected Google account (Google only lets Baker reach sheets it created or the user chose), `--same-as <slug>:<id>` copies another Form's wired destination, `--all --type <kind>` fills every unwired one of a kind. Nothing connected answers `NOT_CONNECTED` with the `request_connection` fix; several accounts connected need `--account <id>`.
 - **`--email` / `--url` replace a destination whole, so they leave alone what only the user can set.** `--all --email` passes over an email that replies to the visitor's own answer (and says so in its hints); naming one is refused. A webhook that sends a credential keeps its address until the user re-enters both through `request_flow_input`. Unreadable settings are also left alone by default. For one unreadable email, `--replace-unreadable --email <complete list> --subject <text>` replaces the old setup when the user intends replacement, without revealing it. Never use this to add to an unknown recipient list; it cannot override `--all`, a known visitor reply, or a webhook. `flows show` reads back only destinations sealed for this company.
 - **Configure the destination before you map.** `columnMapping`/`fieldMapping` describe a *specific* destination — sheet columns, a portal's field names — that only `connect` or `request_flow_input` can set, and both return it. A mapping written first is valid JSON that ships and drops every submission; `verify` blocks the half-wired result.
-- **`map` reads the record shape off the side effect's type.** One property name, four record shapes: a Sheet is addressed by column letter, HubSpot by property name, Pipedrive and GoHighLevel by field key, Crmble by field id. That is why there is no `--key`, and why `--entity` and `--custom`/`--standard` are required rather than defaulted.
+- **`map` reads the record shape off the side effect's type.** One property name, four record shapes: a Sheet is addressed by column letter, HubSpot by property name, Pipedrive and GoHighLevel by field key, ActiveCampaign by field key (`email`, `firstName`, a custom field's id, `tags`, `lists`, `automations`, `note`, or a qualified `deal.title` / `account.name` / `event.name`), Crmble by field id. That is why there is no `--key`, and why `--entity` and `--custom`/`--standard` are required rather than defaulted for Pipedrive and GoHighLevel.
 - **A mapping is usually eight to fifteen fields, so `--from` is the main door.** It takes `{ "map": { "<destField>": "<value>" } }` from a file or stdin; `--map` flags are for one or two. Both produce identical output.
 - **Most CRM fields are not fed by a form field.** The value grammar is a bare form field (`nombre`), `field:Step.name` when two steps share a name, `tracking:utm_source`, `global:Name`, `code:exposed_value`, a `"literal"`, or any of those joined with `+`. Tracking names are validated against the engine's own `TRACKING_FIELD_IDS`, read out of the workspace rather than copied — attribution columns are the most common CRM mapping there is, and they were unexpressible before.
-- **A CRM mapping's field type is derived from the destination, never defaulted.** Every CRM record types `fieldType` as required, and it is the account's answer, not the agent's — HubSpot builds its submission key as `<objectTypeId>.<fieldType>.<fieldName>`, so a wrong type on a date property skips the `YYYY-MM-DD` coercion and the value is dropped. `--hubspot-form <formGuid>` (or `"hubspotForm"` in the mapping file) reads every property's type and object type off the form, so nothing has to state one. Where a destination cannot be read, put the type on the LEFT — `c0ffee:varchar=email` — which leaves `:` on the right for the value kinds. A mapping with no type from either route is refused, never written without one.
+- **A CRM mapping's field type is derived from the destination, never defaulted.** Every CRM record types `fieldType` as required, and it is the account's answer, not the agent's — HubSpot builds its submission key as `<objectTypeId>.<fieldType>.<fieldName>`, so a wrong type on a date property skips the `YYYY-MM-DD` coercion and the value is dropped. `--hubspot-form <formGuid>` (or `"hubspotForm"` in the mapping file) reads every property's type and object type off the form, so nothing has to state one. An `activeCampaignContact` mapping reads the connected ActiveCampaign account's field list on every call — no flag — so its types (`standard`, `custom`, `tags`, `lists`, `automations`, `deal`, `account`, `note`, `event`) are derived too, a custom field may be named by its id, personalization tag or label (stored as the id) — or as `custom.<TAG>` for one that is only staged so far, resolved when each lead is sent — and a name the account does not have is refused with the list of the ones it does. Its `tags`, `lists` and `automations` mappings are comma-separated names or ids that may mix text and variables, e.g. `tags="withbaker-"+tracking:page_path`; `deal.title` or `deal.pipeline` creates a deal (`deal.value` in major units, `deal.stage` / `deal.owner` by name or id), `account.name` finds or creates the lead's company, `note` leaves a note and `event.name` records an event (it needs the account's event key on the connection). The answer's `hints` name a list, automation, pipeline, stage or user the account does not have, a deal nothing creates, and an event with no event key. Where a destination cannot be read, put the type on the LEFT — `c0ffee:varchar=email` — which leaves `:` on the right for the value kinds. A mapping with no type from either route is refused, never written without one.
 - **`email` maps like anything else**, into `body.fields`, while `body.format` is `"json"`. A `"body"`-format email is one written message with no keys to address, and `map` refuses it rather than reshaping the body.
 - **A Form can look finished and be losing every lead.** HubSpot refuses a submission that names a property it does not have — the whole submission, not the field — and the visitor still reaches the thank-you screen. Baker re-checks each Form's destination and `baker flows show <slug>` reports what it found: `data.drift[]` carries **one entry per drifted destination** — a Form with two HubSpot side effects has two mappings, two form ids and two repairs — each with the severity, a sentence naming the fields, the side-effect id and that destination's HubSpot form id; the hints carry one repair command per entry. `drift: null` means the check could not be made and is not the same answer as `[]`.
 - **`--prune-missing` is the repair; `--replace` is not.** With `--side-effect <id>` and `--hubspot-form <guid>`, `--prune-missing` drops exactly the mappings whose destination field is absent from that form's live field list, names each one in `dropped`, and leaves every other mapping alone. It needs no `--map` and runs on its own. `--replace` drops everything the call does not name, so using it to remove three dead mappings means first restating the ten good ones correctly.
@@ -3990,7 +3925,7 @@ Notes:
 - **`normalize` exists so authoring a Form does not require remembering an exception.** `oauthProviderId` is an optional `string`, so a `null` there fails typecheck one build later — it is repaired and staged instead of rejected.
 
 - **Secrets never travel through this CLI or the chat.** `show` reports only whether each field is configured (`[set]`/`[missing]`, `[connected]`/`[needs connection]`, selected/not selected) — never a value. Configured secrets appear only as `[configured]` ciphertext markers.
-- Confidential side-effect types: `httpWebhook`, `zapier`, `crmble` (typed credentials); `pipedrive`, `googleSpreadsheet`, `hubspotForm`, `goHighlevelContact` (OAuth connection + resource); `email`. Widget node types needing a resource pick: `calendly`, `savvycal`, `hubspot`, `hubspotMeeting`, `highlevel`, `highlevelForm`.
+- Confidential side-effect types: `httpWebhook`, `zapier`, `crmble` (typed credentials); `pipedrive`, `googleSpreadsheet`, `hubspotForm`, `goHighlevelContact`, `activeCampaignContact` (connected account + resource); `email`. Widget node types needing a resource pick: `calendly`, `savvycal`, `hubspot`, `hubspotMeeting`, `highlevel`, `highlevelForm`.
 - `request_flow_input` changes stage on the chat's branch and apply when the chat is published; discarding the chat drops them.
 
 ### Action Items (`baker actions`)
@@ -4394,7 +4329,6 @@ baker studio generate "flat geometric mascot, brand palette" \
 | `google/gemini-3.1-flash-lite-image` | Cheapest tier (Nano Banana 2 Lite) — half the flash price per output token. High-volume variants and any 1K-sufficient frame, portrait ad formats included | standard **+** `1:4` `4:1` `1:8` `8:1` | `1K` **only** |
 | `google/gemini-3-pro-image` | Highest fidelity (Nano Banana Pro) — strong prompt adherence and reference grounding | standard set | `1K` `2K` `4K` |
 | `openai/gpt-image-2` | Photoreal + cleanest in-image text — ad/landing reproduction | standard set **minus** `4:5` `5:4` | *(none — derived from the ratio)* |
-| `openai/gpt-5.4-image-2` | **Legacy** — accepted so canvases authored before the gpt-image-2 switch still re-run. Don't pick it for new work. | standard set | `1K` `2K` `4K` (ignored upstream) |
 | `recraft/recraft-v4.1-pro-vector` | Vector/flat/SVG-style with palette control. Writes **SVG**, so its output cannot be fed back as a reference | `1:1` `4:3` `3:4` `16:9` `9:16` **only** | *(none — refuses `image_size`)* |
 
 Standard aspect ratios: `1:1` `2:3` `3:2` `3:4` `4:3` `4:5` `5:4` `9:16` `16:9` `21:9`.
@@ -4517,7 +4451,7 @@ Compact output per take is `{ slot, status, imageId | videoId, url, inLibrary, e
 | `product-pack-shot` | `openai/gpt-image-2` | `1:1` | 3 | **yes** |
 | `ugc-selfie-hook` | `openai/gpt-image-2` | `9:16` | 3 | **yes** |
 | `lifestyle-scene` | `openai/gpt-image-2` | `4:5` | 3 | **yes** |
-| `cinematic-still` | `google/gemini-3-pro-image-preview` | `16:9` | 3 | no |
+| `cinematic-still` | `google/gemini-3-pro-image` | `16:9` | 3 | no |
 | `brand-icon` | `recraft/recraft-v4.1-pro-vector` | `1:1` | 4 | no |
 | `background-plate` | `google/gemini-3.1-flash-image` | `4:5` | 3 | no |
 
@@ -4600,7 +4534,8 @@ baker canvas run my-canvas.json --regenerate gen,adapt
 #     edit (a file watcher), but you can invoke it directly. Accepts the
 #     .canvas.json, its prompt.json, or the creative folder. The rendered image
 #     still only changes on a real `run`, so the dashboard shows an "edited since
-#     last render" badge in the meantime.
+#     last render" badge in the meantime. It also carries the creative's
+#     _definition.md, which the dashboard shows as the ad's brief.
 baker canvas sync-definition src/creatives/<slug>/
 
 # 3. Inspect a finished run (per-node timing, file list, optional video thumbs)
@@ -5117,9 +5052,9 @@ No `image_size`: OpenAI derives the pixel dimensions from the ratio, so a size i
   "params": { "model": "openai/gpt-image-2", "prompt": "Photorealistic photo of …", "aspect_ratio": "16:9", "quality": "high" } }
 ```
 
-###### Model: `openai/gpt-5.4-image-2` (legacy)
+###### Superseded model ids
 
-Kept only so canvases authored before the gpt-image-2 switch still validate and re-run unchanged — `baker canvas run --slug` replays a recorded canvas verbatim. It keeps the full standard ratio set (including `4:5` / `5:4`) and still accepts `image_size`, which the provider ignores. Prefer `openai/gpt-image-2` for anything new.
+`openai/gpt-5.4-image-2`, `google/gemini-3.1-flash-image-preview` and `google/gemini-3-pro-image-preview` are no longer offered, but a canvas, Studio request or skill that still names one keeps working — `baker canvas run --slug` replays a recorded canvas verbatim. Each runs on its successor: `openai/gpt-image-2.5-sunburst` (a `4:5` / `5:4` snaps to `3:4` and `image_size` is dropped, since GPT Image 2.5 takes neither), `google/gemini-3.1-flash-image` and `google/gemini-3-pro-image` (same params). Never pick them for new work.
 
 ###### Model: `google/gemini-3.1-flash-image` (legacy id `google/gemini-3.1-flash-image-preview` still accepted)
 
@@ -6358,7 +6293,7 @@ baker canvas run ./static-ad.canvas.json
 
 Scaffolding runs (and bills) the two vision passes; **running** the result generates billed images. `baker canvas validate` does not check that the `[TODO]` paths exist — supply the real files before `run`.
 
-Size adaptations move and proportionally scale the existing composition first, keeping its background treatment, including intentional flat colour. Generation, adaptation, correction and series briefs preserve plausible anatomy, device proportions, scale, perspective and support, and reflow text while preserving letter shapes. Recognizable app controls remain native; marketing overlays stay visibly separate. Shared guidance records applicable intent and constraints briefly in `_definition.md`, then carries them into `prompt.json` (Markdown is not a render input). Direct briefs need no invented winner or fixed template; reference adaptations reason through the mechanism, transfer hypothesis and what must survive. `creatives make` returns this preparation hint before rendering. Choose the represented role and inspect existing Avatars before creating a new actor; a real founder or customer keeps their verified identity.
+Size adaptations move and proportionally scale the existing composition first, keeping its background treatment, including intentional flat colour. Generation, adaptation, correction and series briefs preserve plausible anatomy, device proportions, scale, perspective and support, and reflow text while preserving letter shapes. Recognizable app controls remain native; marketing overlays stay visibly separate. Shared guidance thinks the ad through in `_definition.md` first (the `## Thinking` outline `creatives make` writes), then writes `prompt.json` from its plan (Markdown is not a render input). `creatives make` returns this think-first hint before the one that writes the ad. Choose the represented role and inspect existing Avatars before creating a new actor; a real founder or customer keeps their verified identity.
 
 During continuations, the accepted image's screen content takes priority over geometry references unless explicitly changed. Laptop scenes receive guidance for a real laptop and consistent display, keyboard and hinge perspective.
 

package/canvas/avocado-tutorial.json

@@ -9,7 +9,7 @@
       "id": "persona",
       "type": "image_generate",
       "params": {
-        "model": "google/gemini-3-pro-image-preview",
+        "model": "google/gemini-3-pro-image",
         "prompt": "Portrait photo of a friendly young woman with natural makeup, wearing a casual white t-shirt, standing in a bright modern kitchen with white countertops and natural daylight from a large window. Warm smile, looking at camera, iPhone selfie style, 9:16 vertical framing.",
         "aspect_ratio": "9:16",
         "image_size": "1K"
@@ -22,7 +22,7 @@
         "image": "$ref:persona.images#0"
       },
       "params": {
-        "model": "google/gemini-3-pro-image-preview",
+        "model": "google/gemini-3-pro-image",
         "prompt": "Same woman from the reference image, now holding up a whole ripe avocado in her right hand, smiling at the camera in a bright modern kitchen. A wooden cutting board and chef knife are visible on the countertop. iPhone vertical selfie-style, natural daylight, 9:16.",
         "aspect_ratio": "9:16",
         "image_size": "1K"
@@ -35,7 +35,7 @@
         "image": "$ref:persona.images#0"
       },
       "params": {
-        "model": "google/gemini-3-pro-image-preview",
+        "model": "google/gemini-3-pro-image",
         "prompt": "Same woman from the reference image, proudly showing the camera two perfectly cut avocado halves on a wooden cutting board, the pit removed, bright modern kitchen, satisfied smile, iPhone vertical selfie-style, natural daylight, 9:16.",
         "aspect_ratio": "9:16",
         "image_size": "1K"

package/canvas/hello-world-overlay.json

@@ -9,7 +9,7 @@
       "id": "person_image",
       "type": "image_generate",
       "params": {
-        "model": "google/gemini-3.1-flash-image-preview",
+        "model": "google/gemini-3.1-flash-image",
         "prompt": "Portrait photo of a friendly person smiling, standing outdoors in a city park with soft golden-hour sunlight, 9:16 framing, natural colors.",
         "aspect_ratio": "9:16",
         "image_size": "1K"

package/dist/account-5VPZ3XQ3.js

@@ -0,0 +1,79 @@
+import {
+  csvOrJson,
+  handleLinkedinError,
+  resolveAccountIdArg
+} from "./chunk-NG2DMLU6.js";
+import {
+  writeAdsJson,
+  writeAdsOutput
+} from "./chunk-OTNGMKI6.js";
+import {
+  NO_CACHE_ARG
+} from "./chunk-ELNN4SNW.js";
+import "./chunk-MV2J73HP.js";
+import "./chunk-GXDLWBOY.js";
+import "./chunk-GIWHHCD6.js";
+import "./chunk-XQIOCIDO.js";
+import "./chunk-I2DNBEV6.js";
+import {
+  apiGet
+} from "./chunk-OSWCEDFE.js";
+import "./chunk-D53AAUG4.js";
+import "./chunk-FZKUUI3F.js";
+import "./chunk-4WYEGE4N.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-4KWMNH6A.js").then((m) => m.accountUrlParamsCommand)
+  },
+  args: accountDetailCommand.args,
+  default: "detail"
+});
+export {
+  accountCommand
+};
+//# sourceMappingURL=account-5VPZ3XQ3.js.map

package/dist/account-SYUEXERA.js

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