Thanks - that’s helpful context, and the linked report looks very similar.
What’s odd in my case is that it did behave “non-responsive” when I wrote the OP: /search/query was being called with term=Eve Park etc. (200 responses), but the chooser list stayed static and did not refine at all.
Since then, I can now reproduce the intended “responsive search” behaviour (as shown in my Safe Mode recording) side-by-side with another browser window.
I haven’t changed anything on the server beyond what I described in the OP, so my current suspicion is that I initially hit either:
- a client-side state issue (cached assets / hard refresh difference / theme component interaction), or
- a query edge case where certain terms don’t return as expected (verbatim / punctuation / stop words / ordering), similar to the “verbatim move search can’t find topic” report you linked.
Next I’m going to compare the actual JSON response from /search/query between the “non-responsive” case and the “responsive” case (same term), and I’ll also run Safe Mode again with/without themes to see if it correlates.
If anyone knows the exact matching rules used by the move-topic chooser (vs full /search) or where it differs, that would be super helpful - I’m trying to pin down whether this is a known limitation/edge case or a regression.