Especially if the cursors are opaque, either offset or ID-based pagination can be implemented using cursor-based pagination...Using cursors gives additional flexibility if the pagination model changes in the future.
The vast majority of GraphQL APIs are inherently stateless. The 'cursor' is being decoded as input to a new request, and offers no guarantees. From this observation, the advice falls apart.
Cursors don't solve the consistency problem; they give the client the false impression of solving the problem. The claim is that an opaque cursor is compatible across changes. Changed to do what exactly, would be the more relevant question.
[
Collection
]
[
|
...
]