0.12.0 — query_items can filter, sort and search

query_items could only page. Anyone who wanted "the workouts assigned to me that are not done, newest first" had to fetch every row and filter on their side — slow, expensive, and it reads like the product cannot query its own data. The REST endpoint behind it always accepted search, status, priority and a sort field; the tool simply never passed them.

Added

• query_items takes search, status, priority, sort and archived. search matches the row title and its text cells; status and priority take a comma-separated list; sort takes title, createdAt, updatedAt or status with a leading - for descending; archived chooses active (the default), archived or all. They apply to the paging loop too, so an unpaged call comes back narrowed instead of pulling every row first.

Changed

• query_items now says in its description that a published app's own REST endpoints take a fuller grammar — nine filter operators per column, relation filters, per-field search — and points at get_app_spec. The tool is the admin view of a board, not the app's query language.

Alongside this, on the API

Sorting by updatedAt is new on the server too. The App API also gained the three things a client needs to work offline: ?since= (what changed, plus the ids that were deleted, plus a cursor), Idempotency-Key on writes, and POST /<endpoint>/batch for up to 50 operations. All three are in each app's generated OpenAPI.