Now that in 269 we have two paths for reading markdown content I think I can build this in.
The default “safe” path is to read Bike’s nested list subset of Markdown. This is “safe” because when Bike saves it will output the same document structure. So Bike is a safe “editor” for this format.
In the latest 269 release when you open a markdown that doesn’t conform to Bike’s nested list format you will see a warning and be given the option to “Open Anyway”. In this second path Bike will still open file OK, but if you save the file it will change the structure to Bike’s nested list format.
Now that we have this distinction I think I will implement some previous markdown ideas in the “Open Anyway” path. In particular mapping headings to outline structure. Phew. Hope that makes some sense.