Lists workflow runs for the authenticated organization with optional full-text
search, filtering, sorting, and pagination.

Search matches workflow name, step input/output, errors, console logs, and run
ID (when the search value is a UUID). Filtering, search, sort, and pagination
are performed server-side.

Results are always scoped to the authenticated organization. OAuth callers
require the workflows:read scope (and matching workspace permission). API key
callers are authorized by organization membership.

Results default to newest-first by started_at. Use sort=started_at for
oldest-first.

Pagination

Two pagination modes are supported (same contract as other public list
endpoints):

• Offset-based — pass offset with limit. Served from the search
  index; offset + limit must not exceed 10,000.
• Cursor-based (required past the 10k window; preferred for large
  result sets) — pass cursor with the opaque metadata.next_cursor
  value from a previous response. Cursors encode started_at + id
  keyset position and are served from Postgres. cursor and offset
  cannot be combined.

Every successful response includes metadata.next_cursor and
metadata.cursor_reset. On offset pages, next_cursor bootstraps a
transition to cursor pagination. When next_cursor is null, there are no
more results. cursor_reset is true when a supplied cursor could not be
used as a position and the page was reset to the start.

Filters, search, and sort are not encoded in the cursor — re-send them on
every page request.