mirror of
https://github.com/4gray/iptvnator.git
synced 2026-10-12 03:56:15 -08:00
Review follow-up (Greptile P1 x2, Codex P2 x3 on #1172): for multi-token compound terms like "A&E HD", the compound substring arms let any title containing "a&e" into the bounded SQL candidate window (200 per-playlist / 5000 global) before scoring enforced the remaining tokens, so enough plain "A&E" rows could push real "US: A&E HD" matches out of the window. - title and M3U payload conditions now compose per word: each word's token conditions AND together, and only a compound word's own arm gains the intact-substring OR — every other word stays an independent constraint - the trigram FTS supplement AND-s the non-compound tokens as contains LIKE conditions next to MATCH '"a&e"' - new SearchWordPlan/getSearchWordPlans/getCompoundResidualTokenGroups helpers in content-search.util.ts Verified on real SQLite: searching "A&E HD" selects "US | A&E HD" but no longer selects plain "A&E"/"US: A&E" rows at the SQL level. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>