Sentry correctly identified that passing slice_start was wrong because
reduced_recent doesn't start at slice_start in messages_dict - it starts
at slice_start + (len(recent_messages) - keep_count).
The backwards search needs to start from the TRUE beginning of reduced_recent
in messages_dict, otherwise it will miss assistant messages between slice_start
and the actual start of reduced_recent.