I did see a problem with stairs — not sure if algorithm does not take into consideration or if data is not properly marked up in OpenStreetMap, but locally, it recommended a route goong over two long sets of stairs: one of them being practically a goat trail I would recommend against running on, but careful trodding is ok. The other stairs are long and wide, so probably not perfect for running (hard to figure out your stride), but ok. I wonder if elevation rate could be taken into account, which would probably exclude the goat trail one.
Steps are supported in OSM, but I don't know if your ones in particular are tagged. Either way, Trail Router doesn't consider them by default. If there is a lot of elevation gain/loss when using the stairs, you can adjust the Hill Preference slider (in the settings screen) to indicate whether you prefer hills or would rather avoid them. You can read more about that here: https://trailrouter.com/blog/greenery-and-hills-sliders/
I did see a problem with stairs — not sure if algorithm does not take into consideration or if data is not properly marked up in OpenStreetMap, but locally, it recommended a route goong over two long sets of stairs: one of them being practically a goat trail I would recommend against running on, but careful trodding is ok. The other stairs are long and wide, so probably not perfect for running (hard to figure out your stride), but ok. I wonder if elevation rate could be taken into account, which would probably exclude the goat trail one.