Re: "Quality" is a structural attribute, not a bolt-on
You're not wrong, but the problem is definition vs usage.
It's like 'loose' and 'lose' or 'less' and 'fewer' in English. There are differences, they are defined, but if people continually use the words incorrectly they become accepted usage.
Continual abuse of the Agile philosophy is making it toxic. As the unit tests are generally written by developers, there's far too much scope for taking shortcuts. At least a more classical development model formalises a specification and testing. Yes, it still frequently goes awry, but if the specification is incomplete it's obvious, and if the QA are reduced, there's no 'agile' excuse to hide behind.