Broken pagination in conversations, contacts and tickets search #294

When search returns more than one page, iterating the returned pager (for / async for) requests page 1 again and again forever. The _get_next closure calls search again with the original pagination and drops the starting_after cursor that it has just read from the response (_parsed_next).

This happens in the sync and async search methods of:

• POST /conversations/search (conversations/raw_client.py)
• POST /contacts/search (contacts/raw_client.py)
• POST /tickets/search (tickets/raw_client.py)

The list methods page correctly. Their cursor is a top-level argument, and the generated code passes starting_after=_parsed_next. In search, the cursor sits inside the pagination request body object. I suspect that Fern does not handle a cursor in that position.

To reproduce: run a search that matches more than one page, then iterate through:

pager = await client.conversations.search(
    query={"field": "updated_at", "operator": ">", "value": 0},
    pagination={"per_page": 5},
)
async for conversation in pager:  # never ends: page 1 repeats
...

Suggested fix: _get_next must send the original pagination, with starting_after set to _parsed_next:

async def _get_next():
    if isinstance(pagination, StartingAfterPaging):
        next_pagination = {"per_page": pagination.per_page, "starting_a
    elif isinstance(pagination, dict):
        next_pagination = {**pagination, "starting_after": _parsed_next}
    else:
        next_pagination = {"starting_after": _parsed_next}
    return await self.search(query=query, pagination=next_pagination, request_options=request_options)