feature: Filter from messages in descending order

When using the message filtering feature, there's a way to filter messages from the start offset and find the oldest matches within the count specified. However, the reverse starting from the latest offset doesn't seem possible?

This seems to be the current supported behavior...

for (offset=START_OFFSET, offset<=LATEST_OFFSET, offset++):
    if filter(messages[offset]):
        results.push_to_top(messages[offset])
        returned_count++
        if returned_count >= MAX_RESULTS:
            break;

Whereas we’re looking for

for (offset=LATEST_OFFSET, offset>=START_OFFSET, offset--):
    if filter(messages[offset]):
        results.push_to_bottom(messages[offset])
        returned_count++
        if returned_count >= MAX_RESULTS:
            break;

Yes, it’s technically possible to zero in on the desired set in the example by changing the custom start offset but it’s a really noisy feedback loop

No files or tests are identified in the issue. Start by locating the message filtering and offset traversal entry points, then trace how the current start-offset search collects matches; done means filtering can begin at the latest offset, return matches in descending order, and stop at the requested count.