Prioritize active records before filtering a bounded history window

When a read surface removes synthetic records after fetching a bounded history window, recent excluded records can fill the window and hide an older active record. If active work is the product priority, place active records first before applying the database limit, then apply explicit exclusions and the display limit. Add a regression with more excluded records than the fetch bound. This preserves active visibility without an unbounded query, but it still cannot guarantee complete historical coverage; use a separately scoped detail read for a selected record.

Applies when: Live work and completed synthetic history share one bounded read query. Keywords: active calls bounded history postfilter synthetic exclusion starvation ordering window