Every write (via with_txn or a direct execute) goes through writer,
the single connection WAL reserves for the one process-wide writer. Reads
go through readers: a pool of separate connections in file-backed mode,
or the same connection as the writer for in_memory, where a second
connection would just see an empty, unrelated database.
Cap on what one traverse call returns. The walk also stops expanding
after TRAVERSE_MAX_WALK (id, depth) pairs, because a hub entity can
connect one memory to tens of thousands and the context pack that asks
only shows a handful.