yay
i just realised, because i wasn't expecting anyone to actually use it so soon, to make sure it doesn't send back too many events in one go. a cap of 1000 should be ok i think. i may have already covered that. wouldn't want to open it up to such an easy DoS
oshit i didn't actually implement the writing of events in the response haha
tag v0.4.8 actually implements the events endpoint now. haha it was running the search and returning null.
it should now return up to 512 events as an array of event objects.
this is all handled by the huma library automatically, so it's not so hyper-optimized on the encode step.
i did that to make it more openapi idiomatic.
