"You might want to look at some of the other proposed "pull requests" from the 10 yr, 15 yr, and 20 yr anniversaries "

Seems like there is a definite desire to update the original, I'd say.

"your article seems to assume Scrum as the start/basis for the result - which certainly was not the case at the time"

I know it wasn't at the time. I've talked to Kent and I know the history of how Scrum won the marketing war over XP. It's far easier to sell certs than it is to sell improved outcomes. Today, Scrum is where more organizations start and also where they end. Then they try scaling it with a framework like SAFe and it all ends in tears.

"Some of the basic updates ... were things like changing "Working Software:" to "Working Solutions", getting rid of the "project" word", putting more of a customer-focus back into the first principle."

And if those changes were made, there would be fewer misunderstandings.

"It should also be noted the first principle is what coined "Continuous Delivery", and was exactly the focus of Humble & Farley's work to take it literally, and transform it from a principle to a practice."

CD SHOULD be the goal, but it rarely is.

"The "every 2-4 weeks) part from today is not so much about release/deploy as it is about establishing a development "cadence""

The Manifesto says, "Deliver working software frequently, from a couple of weeks to a couple of months..." It doesn't says "cadence" it says "deliver." The Agile Industrial Complex communicates this as delivering at the end of a 2-4 week sprint. This leads to large, terrifying releases and large batch thinking. It takes time to repair this.

"perhaps 1-2 weeks would be better"

Yes, 1 week is much better. Continuous flow is better still. My team delivered 3 important changes this week so far.

"delivery+deployment is not the same as continuous release (especially in light of "latent" code that may be delivered to production env, buut isnt necessarily fully turned on nor fully customer validated anywhere near as frequently as the CD frequency."

Deploy vs. release is highly contextual. I've other posts that go more deeply into CD, though I recommend Dave's videos on the CD YouTube channel more.

"But it was always about continuous delivery of value"

The Intent and implementation are not aligned in most cases.

"Last but not least, the most recent update attempt is from the 2021 "Agile 2" effort."

I'm aware. I talk to Cliff. Here's the problem with all of those efforts, they are not updating the original document. When people treat the Manifesto as holy writ instead of just fixing it and people keep starting with the Manifesto, then those people keep starting 20 years behind. They invest in buying training from the Agile Industrial Complex that keeps reinforcing ancient dogma because they paid to get certified in the dogma. Then it requires more expense to level up the affected teams AFTER convincing the C-suite that things like CD aren't a fad and trying to explain why their "Agile Transformation" never materialized the outcomes they were promised.

Someone asked me why I didn't publish something that extended the Manifesto instead of suggesting an upgrade to fix root the defects. Simply because I'm a software engineer and I don't believe in workarounds.