Add pagination to list_sessions

[jackwildman]

Summary

• SDK: New SessionListResult dataclass with total/offset/limit fields
• Generated API client: offset/limit query params on list_sessions endpoint
• MCP server: ListSessionsInput model for pagination params, output shows page info
• All function signatures updated with offset: int = 0, limit: int = 25 defaults

Test plan

• SDK tests pass (uv run pytest tests/test_session.py)
• MCP tests pass (uv run pytest everyrow-mcp/tests/test_server.py)
• Pyright type check clean
• Integration test against deployed API

🤖 Generated with Claude Code

[sentry]

Bug: The from_dict method uses d.pop() for new pagination fields, which will raise a KeyError if the API response is from an older backend version, causing a crash.
_{Severity: CRITICAL}

Suggested Fix

Replace d.pop("key") with d.get("key", default_value) for the total, offset, and limit fields to provide graceful degradation and maintain backwards-compatibility with older API responses that do not include these fields. This prevents KeyError crashes.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: src/everyrow/generated/models/session_list_response.py#L63-L65

Potential issue: The `SessionListResponse.from_dict()` method uses `d.pop()` to extract
the `total`, `offset`, and `limit` fields from the API response. If the SDK is deployed
before the backend API is updated to include these new pagination fields, or if it
receives a response from an older, cached, or partially-deployed backend, the call will
fail with a `KeyError`. This breaks backwards-compatibility and will cause a runtime
crash when calling the `list_sessions()` endpoint.

_{Did we get this right? 👍 / 👎 to inform future reviews.}