Which writes have finished being processed.

A write returns as soon as the memory is stored, then fact extraction runs behind it. Without this endpoint a developer polls blind: they cannot tell "extraction has not finished" from "there was nothing to extract", which is the first confusing thing anyone hits when building on us.

events are the newest writes, newest first; status filters them before limit is applied, so ?status=error returns the most recent errors however many ready writes came after them.

processing in the response is how many writes of this key's project (of user_id, when given) are still in flight, counted over all of them, so a batch import can wait on one number instead of walking every id. It ignores status and limit.

No webhook announces that a write's extraction finished: memory.created is sent when the memory is stored, before its facts, and GET /admin/webhooks/events lists the events there are. Waiting for the facts is polling this, or reading the memory again.