The ‘strong(est) chain index’, that is an index where for each indexed height, the whole block is always available&known&validated, right?
Meanwhile, in the candidate chain, may it be that for one indexed height the header is known but the block is not known yet because it has not been downloaded yet? And, you only trig a reorg that is ‘candidate index’ is a chain with more work than the ‘strong(est) chain index’, you do that ONLY when for each height in that whole candidate chain index, the full block has been known&validated ?