A backend engineer fixed a bug in a Python Flask API's search endpoint: previously, search results were returned unsorted; now they are sorted by relevance score descending. The engineer wants to make sure the fix didn't break anything in the surrounding search flow. Produce a regression scout report as report.md.

=============== FILE: inputs/search-service-overview.md ===============

Search Service Overview

Changed File

• api/search/views.py — search endpoint handler (CHANGED: added .sort() call on results)

Related Files

• api/search/serializers.py — formats search results for API response
• api/search/filters.py — applies user query filters
• api/search/pagination.py — paginates result sets
• api/auth/decorators.py — rate limiting and auth decorators applied to search
• tests/search/test_views.py — view tests
• tests/search/test_pagination.py — pagination tests

Behaviors Before Change

• Results returned in database retrieval order
• Empty result set returned []
• Pagination offset calculated after filtering but before any sorting

Behaviors After Change

• Results sorted by relevance_score DESC before serialization
• Sort applied in-place on the queryset before pagination slice
• Empty result set still returns [] =============== END FILE ===============