Updated patch: the specialization of ConjunctionTermsScorer broke this navigation API as well, because it doesnt have subscorers, instead accessing the docsenums and shit directly.
But there is a way worse bug in this: if even one term is omitTF in your term conjunction it treats the whole conjunction as match-only, which is wrong scoring!!!!!!
I fixed both of these in the patch. I think we can improve/refactor/generalize this conjunction stuff even better, but this issue is already out of control. I'm just trying to fix bugs.