The Agile Manifesto is not gospel.
For starters, I would argue that, "The most efficient and effective method of conveying information to and within a development team is face-to-face conversation," has proven, in the fullness of time, to be an oversimplification.
More importantly, the Agile Manifesto not saying something two decades ago does not mean that it has no place in contemporary agile software development. We've had 20 years' worth of time to learn since then. It would be a shame if we hadn't.
To that end, I do think that active orchestration - and, for that matter, written communication - is critical to being really agile at any sort of scale. It doesn't necessarily need to be done using swim lanes, but they do happen to be a nice mental model (and visual mnemonic) for keeping track of real-world phenomena such as varying quality of service obligations.
But I also think that it makes sense to leave them out of any concrete definition of what it means to be agile. Not only is there more than one way to satisfy that need, there's also no guarantee that every team will have that need.