OTA-694 only considers unconditionally-recommended updates when weighing connectivity between 4.(<y).z releases and 4.y channels. But some conditional risks only impact small subsets of clusters, and are easy for cluster-admins to recover from. In those situations, we would like the 4.(<y).z to appear in the 4.y channels, like graph-data#2485. We should review our current policy, and decide if we want to make bot-logic changes like "only consider Always and worse blocking when calculating connectivity". We may also decide to leave the bot-logic unchanged, and make occasional manual adjustments when we feel that the bot-logic is too strict for a particular case.