I think you missed some of the context/point behind the reference. The bug was reported when it first came up in 23.10, a non-LTS release. The previous non-LT

I think you missed some of the context/point behind the reference. The bug was reported when it first came up in 23.10, a non-LTS release. The previous non-LTS release is a final proving ground for an LTS release. They had an opportunity to fix it from 23.10 until the release of their next LTS, and chose not to. There won't be an LTS for 2 more years, so this regression is likely stuck there (It worked fine prior to 23.10, even supported snaps). If Canonical hadn't been forcing snaps down everyone's throat for the past several years, and continually ignoring all of the negative feedback they get over it, it might have been a different story, but on the back of everything we've seen from them over the years, it reeks of "deliberate choice", and it's really hard not to see this as a deliberate break rather than accidental. Canonical have unfortunately reached trust thermocline stage with everything related to snaps.