> Agile just finally embraced that specs are incomplete and can even be wrong because the writer of the spec does not yet really know or understand what they want. So they need working software to show the spec in action and then we can iterate on the results.

I agree, but what you describe is agile, not Agile (capital A).

Agile (capital A) is Scrum (capital S) where you have Backlog Grooming (patent pending) where the team clears any ambiguity to define a spec (ticket).

Deviating from said spec is seen as Scope Creep (gasp) and might lead to complaints during Sprint Review (trademark).

So yes, agile prefers working software over detailed spec. But typical manifestations of Agile (capital A) are exactly the opposite.