Problem

Two parallel pagination implementations exist — pagination/* (Paginator + Page + strategies) and http/paging/* (PagedIterable + PagedResponse + PagingOptions) — with different close semantics. PagedIterable.byPage() leaks a connection unless the caller closes (PagedIterable.kt:100-105).

Proposed change

Collapse to one stack: a single Page<T> + driver, enriched with the links/status/headers that PagedResponse carries. Preserve the max-pages cap, per-page close, and interrupt-aware blocking. Eliminate the byPage leak.

Acceptance

• One pagination surface
• No connection leak on partial consumption
• Tests + apiDump

Coordinate with async pagination + exception collapse.

Dependencies

• Blocks Typed page classes that rebuild typed params, not URL strings #56 — typed page classes build on the unified surface
• Related Async pagination support #34 — async pagination (shares the page model)
• Related Remove TokenPaginationStrategy (duplicate of CursorPaginationStrategy) #39, Single-read pagination extractor (items + cursor in one pass) #40 — pagination cleanups to keep consistent
• Pre-codegen: settle before the first generator run

Priority: high · Effort: large