Release v4.6.0 · Byline-CMS/bylinecms.dev

Highlights

@byline/host-tanstack-start, @byline/admin, @byline/db-postgres — the collection list view now remembers each admin user's choices. Page size and column sort are persisted per user and reapplied on return, backed by a new scoped per-user key-value store (an admin-preferences module in @byline/admin, the byline_admin_user_preferences table and repository in @byline/db-postgres, and a setListViewPreference server fn in the host adapter). Preferences are keyed by user and scope, so future admin-surface settings can reuse the same store.
@byline/host-tanstack-start — editing a document and closing the editor now returns you to the originating list page with its filters and pagination intact, rather than resetting to the first page. New list return-state helpers and a shared list search schema back the round trip.

@byline/host-tanstack-start — the list page size now defaults to 15 (aligned to the server default) and the original page-size options (including 20) were restored, correcting a regression in the page-size selector.
@byline/host-tanstack-start — preference writes now validate the target collection and narrow sortable fields to scalar store types, preventing invalid sort selections from being persisted.

@byline/db-postgres — this release adds the byline_admin_user_preferences table. Installations that run Drizzle migrations pick it up automatically. Existing production databases that do not run drizzle:migrate must apply the standalone migration before the list-view preferences feature will work:
```
psql "$DATABASE_URL" -f packages/db-postgres/sql/0005_add-admin-user-preferences.sql
```
The script is idempotent (guarded on the table's absence, single transaction) and adds a user_id-scoped table with a cascade FK to byline_admin_users.

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