EntityAdapter selectAll ordering stability when sortComparer omitted and sort-relevant properties updated

Goal

Achieve predictable display order for entity lists derived from selectAll when entities are frequently updated on properties that should affect sort position.

Constraints and uncertainty

The EntityAdapter only reorders the internal ids array when a sortComparer is provided and an operation mutates that array (add, upsert, remove). An update() that changes a sort-relevant field leaves the ids array reference unchanged, so the memoized selectAll selector returns the same array reference and Angular change detection sees no difference. Without a sortComparer, order reflects insertion sequence, which can diverge between eagerly and lazily loaded feature modules. In ngrx v16+ signal-based stores, the interaction between selector memoization and signal equality checks adds another layer of uncertainty about when a new array reference is produced.

Questions

1. What is the recommended pattern to trigger a re-sort of selectAll output after a sort-relevant property update without re-adding every affected entity?
2. Does the v16+ functional entityAdapter API expose a built-in mechanism to invalidate the ids ordering on property changes, or must developers dispatch a synthetic action that replaces the ids array?
3. How does signal-store selector memoization differ from the classic createSelector behavior when the underlying ids array reference is preserved but entity property values change?