The package is behaving as designed. In an idiomatic foreach over an EntityQuery, the change versions of of the query's RW components are updated once in the loop preamble, not per loop iteration (or per RefRW.value write). This is to avoid unnecessary overhead in the overwhelmingly common case where the change version isn't changing over the course of the loop. If you want to force the change version to be updated for each loop iteration, you can use the approaches in the W and E loops as a workaround.

In general, due to the way EntityQuery instances are cached and shared between systems, the behavior of change versions and query filtering is significantly more difficult to reason about when a system is both reading/writing component data and also updating other systems, especially when the same EntityQuery is used by both the parent and child systems. For this reason, as a best practice to avoid confusion, we recommend that most ECS systems should either only manipulate component data or only update other systems.