The README contents part builds each anchor slug from the heading's markdown source rather than its rendered text, so an emoji shortcode or an HTML entity in a heading gives an anchor the forge does not have: `## :rocket: Launch` is linked as `#rocket-launch` where the forge renders `#-launch`, and `## A & B` as `#a-amp-b` where the forge renders `#a--b`.

The README contents part builds each anchor slug from the heading's markdown source rather than its rendered text, so an emoji shortcode or an HTML entity in a heading gives an anchor the forge does not have: ## :rocket: Launch is linked as #rocket-launch where the forge renders #-launch, and ## A & B as #a-amp-b where the forge renders #a--b.

Grounds

• pursued: every contents link names an anchor the forge's page has; a contents link to an anchor missing from the rendered page shows it wrong