@audienti/cli 0.1.63 → 0.1.64

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to the Audienti CLI are documented here.
 
 ## [Unreleased]
 
+## [0.1.64] - 2026-09-10
+
+### Changed
+
+- List routing-rule create and update resolve `locations` and `company_locations` labels to a known LinkedIn geography at save time. Unknown labels return 422. Read responses include `geo_key` on those entries.
+
 ## [0.1.63] - 2026-09-10
 
 ### Fixed

package/README.md

@@ -321,7 +321,9 @@ audienti lists routing-rules <list_id> apply
 Use `action_kind: "route_to_list"` with `target_list_id` to route to another
 working list. `apply` queues the existing list-routing background job, just like
 the UI; it reports that work was enqueued, not that every prospect has finished
-routing. Run `audienti lists routing-rules help` for the full condition contract.
+routing. Location and company_location labels must resolve to a known geography
+at save time; unknown labels return 422. Run `audienti lists routing-rules help`
+for the full condition contract.
 
 To inspect activity for prospects that entered the account during a specific
 cohort while keeping a separate activity window:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@audienti/cli",
-  "version": "0.1.63",
+  "version": "0.1.64",
   "description": "Agent-first command-line client for Audienti.",
   "type": "module",
   "bin": {

package/skills/audienti/SKILL.md

@@ -246,10 +246,11 @@ Never infer that `ready: true`, paused motions, or prepared queue work authorize
 provider execution.
 
 List routing-rule create and update commands accept the same normalized
-condition and action data as the list UI. Inspect the ordered rules first, use
-`audienti lists routing-rules help` for the payload contract, and treat `apply`
-as an asynchronous relaunch: it queues the existing routing job and does not
-mean every list member has finished routing.
+condition and action data as the list UI. Location and company_location labels
+must resolve to a known geography or the request returns 422. Inspect the
+ordered rules first, use `audienti lists routing-rules help` for the payload
+contract, and treat `apply` as an asynchronous relaunch: it queues the existing
+routing job and does not mean every list member has finished routing.
 
 Motion start and end dates are optional lifecycle controls. A due start can
 activate a configured preparing or paused motion; an end date is the final

package/src/cli.js

@@ -9513,6 +9513,15 @@ const HELP_TOPICS = new Map([
     "  locations, company_locations, seniorities, job_titles, bio_texts,",
     "  company_sizes, company_types, company_keywords, seniority_match_mode, industry_groups",
     "",
+    "Location and company_location entries:",
+    "  name: string | required; must resolve to a known geography",
+    "  negative: boolean | optional",
+    "  geo_key: LinkedIn geography id or app key such as app:north_america | optional on write, filled on save",
+    "  id: legacy LinkedIn id | treated as geo_key",
+    "  Known labels include countries, US states, Canadian provinces, and named regions",
+    "  (North America, Europe, EMEA, DACH, Nordics, ANZ, UK and Ireland, Middle East,",
+    "  APAC, LATAM, Africa, Oceania). Unknown labels fail with 422.",
+    "",
     "Example payload file:",
     "  {",
     "    \"name\": \"VP prospects to Alice\",",