Markdown Footnotes vs. "more" tag

The footnotes code produced by the Jetpack Markdown module uses relative links as anchors, such as "#fn-10167-2." However, when using the "more" tag to limit the amount of a post showing up on the front pate, these kinds of links are broken (since the current URL is the URL of the front page, not the individual post). This could be fixed if the HTML code produced by Markdown footnotes used the full URL instead. Other aspects of WordPress work this way, such as comments. Clicking on a comments link above a post directs one to the anchor for comments on that post, even if you are on the front page of the site.

It is the difference between:

http://mywebsite.tld/#fn-10167-2

and

http://mywebsite.tld/date/slug-for-post/#fn-10167-2

Start by locating the Jetpack Markdown module's footnotes implementation and the handling of WordPress's “more” tag. Reproduce a post with footnotes on the front page, then verify that each footnote link includes the individual post URL and still reaches the correct anchor.

Written by the indexing model from the issue text.