According to the bug post, it's actually behavior which actually exist only if some other thing failed ("If Astute pre-deployment hook failes right now..."), so based on that I can conclude it should not count for HCF: it's rather affecting development workflow only. Then, I think it should be tracked as part of next milestone (6.0), and with possible backport to stable/5.1 only if needed for dev purposes.
According to the bug post, it's actually behavior which actually exist only if some other thing failed ("If Astute pre-deployment hook failes right now..."), so based on that I can conclude it should not count for HCF: it's rather affecting development workflow only. Then, I think it should be tracked as part of next milestone (6.0), and with possible backport to stable/5.1 only if needed for dev purposes.