pub const MAX_TILE_BYTES: usize = crate::kv::NATS_PAYLOAD_BUDGET; // 262_144usizeExpand description
Largest encoded tile a single message may carry.
Derived from crate::kv::NATS_PAYLOAD_BUDGET rather than restating
its value, so raising the broker’s max_payload moves this without
anyone remembering that it should. It stays its own constant because
“how far may one screen tile grow” and “when does stdout spill to the
Object Store” (crate::kv::STDOUT_INLINE_THRESHOLD) are different
questions that merely share a broker limit — collapsing them would mean
a future tile-specific ceiling (headers do consume some of the budget)
silently retuning result overflow.
Comfortably above the ~94 KB mean tile #1142 measured; a full-screen change encodes to ~700 KB and the sender must split it.