Of the 12 “Principles behind the Agile Manifesto”, at least 3 are directly focussed on crafting quality software:

“Continuous attention to technical excellence and good design enhances agility.

“Simplicity–the art of maximizing the amount of work not done–is essential.

“The best architectures, requirements, and designs emerge from self-organizing teams.”

We need to focus our energy on crafting better software better rather than crafting new manifestos.

to me ‘working software’ means not only that it functions, but that it ‘works’ for the customer. That means that if what the customer needed was just a rapid prototype to get feedback, that it’s not overengineered. or if it’s production quality code that works for the long haul that it’s maintainable and enhanceable. If that’s the case, then I’d say it’s likly been built with a level of craftsmanship

If you succesfully respond to change are you not adding value (or preventing the loss of value) and if not, how exactly are you measuring success?

If you value individuals and interactions, are you not naturally part of a larger community and interacting with your peers?

If you are succesful at collaborating with your customer have you not created a productive partnership?

I appreciate the intent also, but I think they’ve mixed up cause and effect.