Added value: +"EntityType"

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}

Previous value: -"Include past employees (alumni) alongside current\nones in the attached people block (default false). Company lists only."New value: +"Include past employees (alumni) alongside current\nones in the people search (default false). Company lists only."

Previous value: -"Soft preferences and exclusions for the attached\npeople. Each is checked against them, where only an exclusion rules\nsomeone out; the kept people are ordered most senior first. Company\nlists only."New value: +"Soft preferences and exclusions for the people\nfound. Each is checked against them, where only an exclusion rules\nsomeone out. Company lists only."

Previous value: -"For company lists, a positive-form query for the people to\nattach as a `data.people[]` block on each company row — controls which\npeople come back. Company lists only; skipped on person lists."New value: +"For company lists, a positive-form query for the people to\nfind at each new company that the check against `criteria` doesn't\nreject — controls which people come back. They're saved as person rows\non the '<list_name>-people' list when the search finishes. Company lists\nonly; skipped on person lists."

Previous value: -"The roles `people_query` is asking for, as title keywords,\ne.g. ['Marketing', 'Growth'] or ['Operations', 'Chief']. Each is matched\nas a case-insensitive substring of a person's job title and the list is\nOR-ed, so use the distinctive word a title is built from rather than a\nwhole title: companies word the same job many ways, and a full phrase\nfinds only the ones that word it exactly as written here. Broader words\nrecall more people and admit more adjacent roles, so pick the narrowest\nword that still covers the variants. Set it whenever `people_query`\nnames roles — the attachment runs unattended, so this is its only\nstructured read of the roles you asked for. Company lists only."New value: +"The roles `people_query` is asking for, as title keywords,\ne.g. ['Marketing', 'Growth'] or ['Operations', 'Chief']. Each is matched\nas a case-insensitive substring of a person's job title and the list is\nOR-ed, so use the distinctive word a title is built from rather than a\nwhole title: companies word the same job many ways, and a full phrase\nfinds only the ones that word it exactly as written here. Broader words\nrecall more people and admit more adjacent roles, so pick the narrowest\nword that still covers the variants. Set it whenever `people_query`\nnames roles — the people search runs unattended, so this is its only\nstructured read of the roles you asked for. Company lists only."

Previous value: -"company domains/URLs the webset must not ingest (compared by\ncanonical hostname). Use to avoid re-ingesting rows already recorded in\nthe list, e.g. seeds from find_companies_by_tech_stack."New value: +"company domains/URLs the webset must not ingest (matched by\ndomain). Use to avoid re-ingesting rows already recorded in\nthe list, e.g. seeds from find_companies_by_tech_stack."

Previous value: -"Title keywords to reject, e.g. ['Coordinator',\n'Intern']. Same substring matching as `people_titles`, subtracted from\nit. Whenever `people_preferences` rules a role out, put that role here\ntoo — the attachment cannot read the prose, so an exclusion written only\nthere is not applied. Company lists only."New value: +"Title keywords to reject, e.g. ['Coordinator',\n'Intern']. Same substring matching as `people_titles`, subtracted from\nit. Whenever `people_preferences` rules a role out, put that role here\ntoo — an exclusion written only there applies after the fetch, so the\nexcluded people can still fill the fetched slots. Company lists only."

Previous value: -"Soft ranking/filtering preferences (and exclusions)\nfor the attached people. Company lists only."New value: +"Soft preferences and exclusions for the attached\npeople. Each is checked against them, where only an exclusion rules\nsomeone out; the kept people are ordered most senior first. Company\nlists only."

Added value: +{
+  "description": "The agent to host the new list.",
+  "type": "integer"
+}

Previous value: -"'person' or 'company'. Mixed people+company tasks are\nsupported — each list has its own row type."New value: +"'person' or 'company'. Mixed people+company agents are\nsupported — each list has its own row type."

Previous value: -"short kebab slug identifying the bucket (e.g.\n'oil-gas-operators'). Pick a name distinct from any existing list\non the task. Re-using a finished list's name extends it; re-using\na running list's name is refused."New value: +"short kebab slug identifying the bucket (e.g.\n'oil-gas-operators'). Pick a name distinct from any existing list\non the agent. Re-using a finished list's name extends it; re-using\na running list's name is refused."

Removed value: -{
-  "description": "The task to host the new list.",
-  "type": "integer"
-}

Previous value: -[
-  "task_id",
-  "list_name",
-  "criteria",
-  "entity_type"
-]New value: +[
+  "agent_id",
+  "list_name",
+  "criteria",
+  "entity_type"
+]