v0.2.3

fix: use last change timestamp as pagination cursor

Previously, serverTimestamp was set to new Date().toISOString() which returned the current server time. This caused pagination to fail because the next page would use a timestamp in the future as cursor, returning 0 changes.

Now serverTimestamp correctly returns the updatedAt of the last returned change, ensuring pagination continues from the correct position.