I thought it'd be okay to use the community-maintained Obsidian git plugin, but as fate would have it, my original fears actually came to pass. I lost over a month of notes due to how badly behaved its git merge heuristics are. It force pushes and rewrites history and will step on other machines with different updates. It took me a little while to catch on to the fact my notes were disappearing, and there was nothing I could do to recover.
I ultimately threw up my hands and abandoned Obsidian outright.
If the use case is single user wiki and the user is technical enough, MediaWiki requires more resources and is also more work than Git + Markdown + a static site generator if you are already comfortable with static site generators. No specific web server config, no tricky configuration files, no database to maintain, not difficulties to upgrade the server…
Now, one could argue that "single user wiki" just means "regular website" because the essence of the wiki is gone. Wiki means "quick" (friction-less?) edits by multiple users, possibly anonymous [1]). What the author of the post did is convenient handling of internal links. Which is still a good idea, but I would do it differently: I would not create a <a href="..."> tag for missing pages, that not very nice to users. If you do this, you are intentionally creating broken links that can only be distinguished with styling, which is not very accessible. Red links are useful in an actual wiki where users can actually create the page, but on a regular website, I'd use something like <span class="missing" title="Dedicated page coming"> or so (+ whatever is needed for the title text to be accessible).
[1] https://en.wikipedia.org/wiki/Wiki
> A wiki is a form of online hypertext publication, collaboratively edited and managed by its own audience, using a web browser