56a251eb13
BlockSection::set resolved the old cell through get and then probed the section palette three times per non-trivial write: keying the old state by id, testing the incoming state and finding it. The slot at the written index already is the old state's id, so read it straight from storage and resolve only the incoming state, with a single map probe. Palette reuse, free slots and growth are unchanged, so palette, counts, free list and NBT are identical. PalettedContainer::unpack and unpack_u16 matched the palette variant inside the per-cell loop; dispatch Single/List/Global once before it. Measured against copies of the pre-optimization code (ignored tests): BlockSection::set 12.73 -> 11.37 ns/write (1.12x), unpack list 1.956 -> 1.860 us/call (1.05x), global 2.255 -> 2.172 (1.04x). See docs/performance/paletted-container-access-results.md. set_matches_baseline_under_random_edits drives both implementations over the same 50k-edit streams for 1/2/16/17/24/64 distinct states, with periodic whole-section collapses, and asserts equal results, bits, palette, counts, free list and NBT.