v3.20.4

Highlights

• @byline/core — new CollectionDefinition.listSearch schema key that decouples the admin list-view quick-search box from the site-search search.body configuration. The two settings answer different questions — "find the row I mean" (a substring ILIKE over store_text) versus "rank relevant published content" (weighted provider indexing) — and previously the list box was tied to the store_text subset of search.body, forcing a collection with a broad six-field weighted search.body to also match all six fields in its list view. listSearch lets a collection name just its identity field (plus, say, a serial/code field) for quick-search while keeping a rich search.body for the search provider. Either key is valid independently: declaring listSearch on an unindexed collection keeps the list box working with no search config at all. When omitted, list search falls back to the identity field (useAsTitle, else the first declared text field) — so existing collections need no change. Lives on the schema alongside useAsTitle (not admin config) because the query layer resolves it server-side. Boot-time validateCollections now enforces that each listSearch entry names an existing, non-virtual, text-store-backed field.

All other @byline/* packages bumped to 3.20.4 in lockstep with no behavioural changes this cycle.