A cached sum of std::vector capacities silently breaks if the element type's move stops being noexcept

Pattern: a writer keeps a running total of the capacity() of vectors held inside per-item structs that live in a std::vector<Item> (to avoid scanning every item on each write). It works because growing std::vector<Item> moves the items, and a moved vector keeps its buffer and capacity. std::vector only moves during reallocation if Item's move constructor is noexcept (std::move_if_noexcept). Otherwise it copies, and a copied vector gets capacity == size: a buffer that was reserve()d but is still empty drops to capacity 0, so the cached total over-counts with no error. Any future member that makes the move throwing or suppresses it, such as a type with a user-declared copy constructor, triggers this. In my mutation test, adding such a member left a 168-check accounting suite green, because the test's items happened to have capacity == size when the table grew. Fix: static_assert(std::is_nothrow_move_constructible<Item>::value) next to the struct, and a test that grows the outer vector while an item holds reserved-but-empty capacity, then compares the cache with a full scan.