Extend catalog cascade to GET /library/query so modern Card Catalog sees matched_via

[jakebromberg]

Closes #977. Follow-up to #973 (which wired the cascade onto GET /library/).

The modern Card Catalog calls GET /library/query, which runs its own
field-aware ILIKE primary path in librarySearchService.searchLibrary
and never reaches the Track 1 (CTA) + Track 2 (LML /lookup) cascade
owned by libraryService.searchLibraryBothMode. So even though prod is
running with both CATALOG_TRACK_SEARCH_*_ENABLED=true, modern dj-site
showed no chips for vi scose poise while classic-experience search did.

Approach

After the primary db.execute(dataQuery) returns 0 rows AND the parsed
query is a single bareword (no artist: / album: / label: qualifier,
no quoted exact, no NOT), fall through to:

1. searchLibraryByCTARaw(q, limit, on_streaming) — Track 1, gated by flags.ctaEnabled
2. on Track 1 0-hit, searchLibraryByTrackRaw(q, limit) — Track 2, gated by flags.discogsEnabled

Both primitives already return TaggedLibraryViewEntry[] (LibraryArtistViewEntry + matched_via) and were introduced as reusable building blocks in #973. Genre/format/on_streaming filters and the requested sort + order apply to the bounded cascade list in-memory before serialization. Cascade fallback is single-page (page > 0 returns []) so the client doesn't paginate into a bounded list.

With both flags off (the default), the function path is byte-identical to today.

Trigger detection

Cascade fires when the parsed SearchCondition[] is exactly:

[{ field: 'all', exact: false, negated: false, ... }]

Field-qualified queries like artist:NonexistentFoo skip the cascade even on 0-hit — they signal a structured match intent, not a cross-table track lookup.

Test plan

• npm run typecheck — clean
• npm run lint — 0 errors on touched files
• npm run format:check — clean
• npm run test:unit — 1991 / 1991 pass
• Integration (CI docker stack):
  • tests/integration/library-query.spec.js — all 22 pass (17 pre-existing + 5 new BS#977 cascade cases)
  • tests/integration/library.spec.js — all 60 pass (no regressions on Wire searchLibrary cascade into GET /library/ so catalog clients see matched_via #972/Wire catalog cascade into GET /library/ via fuzzySearchLibrary (BS#972) #973 cascade describes)
  • tests/integration/library.search-ranking.spec.js — all 5 pass
• Once merged + deployed, smoke against prod: GET /library/query?q=vi+scose+poise should return { results: [{ id: …, matched_via: [{ source: "discogs_release" | "discogs_master", … }] }], total: 1, page: 0, totalPages: 1 }. Modern Card Catalog chip rendering should turn on automatically (component already wired at dj-site/src/components/experiences/modern/catalog/Results/Result.tsx:111).

Related

• Extend catalog cascade to GET /library/query so modern Card Catalog sees matched_via #977 (this fixes)
• Wire catalog cascade into GET /library/ via fuzzySearchLibrary (BS#972) #973 (built the reusable TaggedLibraryViewEntry + *Raw primitives)
• Wire searchLibrary cascade into GET /library/ so catalog clients see matched_via #972 (parent — wired the cascade onto /library/)
• Project Catalog Track Search #30