Cool. Was wondering why this change, as previous version in console had 0. But looking at the analytics I can see that it's actually expected to be 1-based, with an `offset - 1` when slicing. Having it at 0 would also mean that there's one less result returned too, which I see now it was doing, always one less than the limit.

But I wonder if 'offset' is more naturally 0-based, while something like 'page' is 1-based. I see that it was renamed in atmos from 'fromPosition' to 'offset'. Maybe it should become 0-based in elucidator when we make the switch, as offset = 1 suggests something else to me.