Once ORES drafttopic data is in ElasticSearch (via some combination of {T240556} and {T240558}), expose it to the search field via some keyword such as `topic:<topics>` (e.g. `topic:Culture.Arts|Geography.Maps|STEM.Science`; or maybe we'd want some user-friendlier topic names, maybe even localizable ones). This should probably happen via the [[https://www.mediawiki.org/wiki/Extension:CirrusSearch/Hooks/CirrusSearchAddQueryFeatures|CirrusSearchAddQueryFeatures]] hook in the ORES extension.
Open questions:
* what should be the exact search logic? Should it act like a filter (limit the result set to pages for which all the specified topics are above some (what?) threshold), or more like a scoring function (hits where the specified topics have higher ORES scores get scored higher by ES)? Since ORES scores will be stored as a text field, the latter seems easier and more natural.