You’re not losing your mind! I was able to replicate it just now, but I’m not 100% able to explain it. The code that tries to do clever things with list and icons is in need of an overhaul. I think I was able to fix the issue with ordered lists. As for preventing icons, if you use an unordered list with HTML instead of Markdown, that should prevent the icons from appearing. For example:
Yeah, you can mix HTML and Markdown within the same document, but not within the same line of the document (or at least not consistently). I’ve also found that weird things can happen when blocks of HTML and Markdown “touch” — you kind of have to space them out with a solid empty linebreak between them or things get wacky. (To be clear, this isn’t just a fluke of my genuinely flukey code, but is actually something that happens with a ton of Markdown parsers in general.)
I do think I can make this better in the long-term, though, by rewriting the overall parser to accept more specific directives for lists. Part of the problem now is that the current parser assumes that all Markdown unordered lists should be Font Awesome lists, which clearly isn’t always going to be the case. So instead of making that assumption, I can add something that lets you explicitly define what you want (or don’t want).