Wait no- comments like this are what I enjoy. I personally struggle with the whole dichotomy of "marketing led" writing and then balancing that with just spending 2,000 words talking through test frameworks and cases. Maybe for a future blogpost, but the idea of stateful state tracking is a rabbit hole I can get buried under.
To address your main point, I think Git is in the same camp of Python's origins. Powerful despite the creator's initial intentions. Where like it or not, it becomes a powerful mental API to interact with domains. (Git -> Changesets, Python -> Notebooks/Repls)
When I was working on the material for the feature, I kept on trying to find a parallel that fit within people's mental model without it being a leaky abstraction. (Of course my colleague helps make me sound sane.) Other ideas to get people's attention was talking a bit about YAML, but to your point- I hate the bashing that most DevOps companies do that say: K8s is EVIL!!11!!!. Or end DevOps11!!!!!! - it's a series of practices that help you for an outcome, in the same way how Git, SVN, Mercurial, help you and a team track changes.
Changesets is just one way to maintain a production/infra practice a suite of recommendations that a team can adopt.
Thanks for commenting and I hope it was an interesting read :3