# Assigned Lead search

`GET /agent-api/agent-leads/assigned/search?q=Jerry&cursor=...`
also exists under `/api/agent-leads/assigned/search`.

This searches all eligible Leads assigned to the authenticated staff user, not
only the first 25 downloaded records. It uses the same web Account Manager field,
`leads.assigned_admin_id`, and the existing prefix query validation, throttle,
audit, eligibility rules, and pagination. No all-Leads permission is required;
other assignees are excluded server-side. Cursors are bound to user, query and
the assigned-search scope, so they cannot be replayed in unrestricted search.

Deploy before the Flutter Assigned to Me search client; no migration is needed.
Ordinary list ordering remains unchanged. An old Lead newly assigned to a user
may still be beyond page one, but can now be found directly by search.

Regression coverage: old Lead below the first page, assignment through the web
repository, reassignment visibility, both route prefixes, pagination, validation,
authentication, and foreign user/query/scope cursor rejection.

This reproduces a discoverability gap from the meeting; the actual production
Jerry Lim row has not been inspected and no production assignments were changed.