The problem is that those are a really vague and metaphorical 4-5 lines so it's hard to argue against somebody projecting whatever the hell meaning they want on to it.
I'd argue that "agile" where I have done it and it worked well is at its core about tightening up OODA loops - with code (refactoring+tests+iterative improvements), with customer interaction (frequent interaction/experiment driven tests), with team organization (retros, adapting team processes).
Feedback loops are, however, not mentioned once in the philosophy and neither are any concrete examples of "agile" or "not agile".
Agile as a concept will stop being broken when people stop saying "to me, agile means X". Which will probably never happen - I suspect people will just stop talking about it one day and start using different terms for all the concrete steps that are sometimes filed under "agile" but which actually work.
That's a bit misleading. agilemanifesto.org also hosts a (still short, but way more concrete) Twelve Principles of Agile Software: https://agilemanifesto.org/principles.html
(Also worth noting that scrum and most of the best known agile methodologies predate the manifesto; the manifesto was formed from guiding principles of those methodologies, not the other way around: https://agilemanifesto.org/history.html)
It is the pseudoscience of Taylorism and 'Scientific management', not the manifesto, which is really just a repackaged form of modern organization theory.
How unsurprising, than, that every little town and village has their own folk religion built around those 4-5 sentences. No wonder this topic is a holy war.
> Individuals and interactions over processes and tools
> Working software over comprehensive documentation
> Customer collaboration over contract negotiation
> Responding to change over following a plan
> That is, while there is value in the items on the right, we value the items on the left more.
The thing I think everyone has grown to universally despise is the cargo cult of “Scrum” that got bolted onto that.