October 24, 2026 (UTC) — Local UPC evaluation brief
Scope: the optional Python customer UPC matching recipe. The recipe now produces a human-readable evaluation brief alongside its local machine-readable report. Read the brief guide for browser and print output. Use it to explain the tested inputs, candidates, ambiguous results, failures and limitations to a colleague. Candidates are not verified product matches, and a bounded evaluation does not measure coverage of the whole dataset. Review a report before sharing it outside your organization. Integration impact: this adds local evaluation output. It does not change API response fields, matching rules, quotas or existing data. Dry run remains the starting mode; API lookup still requires an explicit choice and an API key. Your action: update your copy of the examples repository if you want the brief. Existing API integrations need no changes.Earlier guidance — Taxonomy 2.0
The Taxonomy 2.0 release note explains canonical category values, historical mappings and classification scope. The original note does not give a single effective date for every delivery surface; this index does not assign one retroactively. Affected fields:llm_category and llm_category_path. Field names and types
remain nullable strings, while returned category paths may change or stop at a
supported non-leaf node.
Your action: review exact-path mappings and fixed-depth assumptions against
the release note. No API version migration is required solely for that refresh.