MAX_ID_SET_BYTES

const MAX_ID_SET_BYTES: number;

Cap on the SERIALIZED size of an idSet cursor.

This is the real bound, and the one the platform enforces: a cursor must fit in 65,536 bytes. DEFAULT_ID_SET_MAX counts ENTRIES, and a blog URL runs 60–120 bytes, so ten thousand of them is roughly 800 KB — twelve times over a limit a count can never see. A scrape source in production reached it after a few hundred posts, and every run afterwards was refused, so the source could not advance past the point where it broke. A count cap alone cannot prevent that; only measuring the bytes can.

Held under the limit rather than at it, because the cursor is serialized inside a larger envelope.