The future of RSS is "git clone". RSS was invented in 1999, 6 years before git! Now we have git and should just be "git cloning" blogs you like, rather than subscribing to RSS feeds. I still have RSS feeds on all my blogs for back-compat, but git clone is way better.
What problems does that solve? Reading blogs over git clone sounds like re-inventing the wheel. Are there even any tools that do that? If anything were to replace RSS (and Atom) I'd personally hope for h-feed [1] since it's DRYer. But realistically it's going to be hard to eclipse RSS, there's far too much adoption and it is mostly sufficient. [1] https://indieweb.org/h-feed
..and tooling could take care of all the things you like in an RSS reader. I could see this working really well for static site generators like vitepress or Jekyll or what have you, but going beyond what's in the source is kind of project-specific, but maybe I'm interested in just a summary of commits/PRsAnyway, there isn't an official IANA-defined type for a git repo (the application/x-git is my closest guess until one became official) but my point is it isn't too far beyond what auto-discovery of RSS is.
I think the GP's comment is from the point of view of making it easy to retrieve the contents of the blog archive, easier than the hoops mentioned (bulk archive retrieval and generating WordPress page sequences, etc.) as well as solving the problem in TFA (partial feeds, partial blog contents in the feed).