We're still using misaka, which is not good, and bugs about markdown formatting are piling up from multiple bug trackers, so I think it would be a good idea to replace misaka with something else. See https://todo.sr.ht/~sircmpwn/sr.ht/223, https://todo.sr.ht/~sircmpwn/sr.ht/195, https://todo.sr.ht/~sircmpwn/sr.ht/188, https://todo.sr.ht/~sircmpwn/sr.ht/127, https://todo.sr.ht/~sircmpwn/git.sr.ht/201, https://todo.sr.ht/~sircmpwn/git.sr.ht/191, and that was only a cursory search.
As mentioned before, there is https://github.com/rtfd/CommonMark-py, and I found https://pypi.org/project/marko, which implements CommonMark, adds additional extensions and has GFM support. However, it clearly states that it's a bit slower than other processors; I don't know whether this is going to be an issue.
I don't program often in Python, but I am willing to try to rewrite https://git.sr.ht/~sircmpwn/core.sr.ht/tree/master/srht/markdown.py to use marko instead. There will probably be a lot of bugs, but I can put forth a first implementation.
Support the scenario where the input to an argument could have been interpreted as an option. This is generally not wanted, so it will be optional (i.e an argument-specific type flag), and maybe include a note about it in the help message?
The select flags and value parsers have been added. Currently not hooked up to anything, but they will be soon.
REPORTED RESOLVED IMPLEMENTED
Instead of allowing hardcoding, which brings a variety of parsing issues to deal with, only (associative) array references will be allowed. When not using an associative array, the element name is the first part of the element.