@koda-sl/baker-cli 0.215.0 → 0.216.0

package/README.md

@@ -100,6 +100,17 @@ question — and nothing in the output said so. Both spellings of an option work
 (`--run-id` and `--runId`), as they always did. Run `baker schema <command>` to see
 every option a command takes.
 
+### Fresh reads: `--no-cache`
+
+Every command that caches takes `--no-cache`, and it skips **both** cache layers — the
+CLI's own disk cache and the server's. The Google, GA4, GSC, research and X families
+used `--no-cache` while LinkedIn and Meta used `--skip-cache`, a split that named our
+two cache layers rather than anything a caller wanted to choose between. Once an
+unrecognised option started failing the call, it broke every consumer that could not
+know which family it was talking to — including report refresh, which appends
+`--no-cache` for any source. `--skip-cache` is still accepted as the old spelling and
+is rewritten to `--no-cache` before parsing; it will be removed.
+
 Use `--output` to change format:
 
 | Format  | Description                        | Best for           | Available on |
@@ -885,7 +896,7 @@ The HTTP backend exposes more endpoints (catalogs, ad-studies, ad-images, labels
 - Tokens auto-refresh server-side (60-day rolling long-lived user tokens). On `code 190` reconnect Meta from the dashboard.
 - Account scoping: backend rejects any call against an account not in the picker selection — pick accounts via Settings → Connections → Meta Ads first.
 - All cached actions are keyed per company; two companies that connect to the same Meta account never share cache entries.
-- `--skip-cache` on any command forces a re-fetch.
+- `--no-cache` on any command forces a re-fetch.
 
 #### Restricted pixel fields
 
@@ -1114,7 +1125,7 @@ Each finding: `{id, area, check, status, severity, evidence, fix: {explanation,
 - Account scoping: backend rejects calls against an account not in the picker selection.
 - Pinned API version: `Linkedin-Version: 202606` (declared in `oauth/constants.ts`). Bump as a coordinated change — LinkedIn deprecates monthly with a ~12-month support window. The floor is `TRACKING_PARAM_DYNAMIC_MIN_API_VERSION` (`CREATIVE_NAME` needs 202606), asserted in `ads/linkedin/utils.test.ts`.
 - Cache TTLs: accounts/account-detail 1h, listings 30m, analytics 15m–6h (depends on date range), facets 7d, urn-resolve 1h, bid-pricing/forecast 6h, audience-size 1h.
-- `--skip-cache` (server-side) and `--no-cache` (client-side, where supported) on any command.
+- `--no-cache` on any command skips both cache layers (the CLI's own and the server's).
 
 #### LinkedIn-specific gotchas