Donkie 9a93892a91 Add allow_archived to /search and stop the candidate cap hiding new rows ...

Two gaps in the new /search endpoint, neither yet released:

Archived spools were always included, unlike GET /spool. /search now takes
allow_archived (default false) and applies the same false-or-null clause
spool.find uses, so the two endpoints agree on what "archived" hides. The
exact-id shortcut honours it too -- otherwise searching an archived spool's id
surfaced it regardless.

Candidate selection ordered by id ASC before LIMIT 200, so on a database with
more than 200 matches for a term only the 200 lowest ids were ever ranked and a
newly added spool could not be found at all. Ordering descending makes the newest
rows the ones that get ranked, which is the useful bias for an inventory that
only grows. Ranking still re-sorts the survivors by match quality, so this
changes which rows are considered, not how results are ordered.

Integration tests cover both defaults and both opt-ins.

2026-07-28 20:56:10 +02:00

..

__init__.py

Add cross-entity search to v2 client

2026-07-13 19:33:52 +02:00

test_search.py

Add allow_archived to /search and stop the candidate cap hiding new rows

2026-07-28 20:56:10 +02:00