[Repo Assist] fix: Markdown.ToMd uses correct backtick fence for inline code containing backticks

[github-actions]

🤖 This is an automated PR from Repo Assist.

Problem

Markdown.ToMd always wrapped InlineCode spans with a single backtick:

| InlineCode(body, _) -> "`" + body + "`"

When body itself contains backtick characters this produces invalid Markdown. For example, InlineCode("ab", _)serialised to ``ab , which a parser would read as the empty span a followed by literal `b` ` `` — not the intended inline code.

The fsdocs inline parser already supports N-backtick fences (List.DelimitedNTimes) and the backtick-with-spaces form, so a serialiser that produces multi-backtick fences round-trips correctly.

Fix

MarkdownUtils.formatSpan for the InlineCode case now:

1. Counts the longest run of consecutive backtick characters in the body.
2. Uses a fence of (run + 1) backticks — guaranteeing the delimiter never appears inside the body.
3. Adds a leading/trailing space when the body itself starts or ends with a backtick, to prevent fence ambiguity (per CommonMark spec).

Changes

File	Change
src/FSharp.Formatting.Markdown/MarkdownUtils.fs	Replace single-backtick InlineCode serialisation with adaptive fence
tests/FSharp.Markdown.Tests/Markdown.fs	Add two round-trip tests: single-backtick and double-backtick body content
RELEASE_NOTES.md	Changelog entry under [Unreleased] / Fixed

Test Status

• ✅ dotnet build FSharp.Formatting.sln --configuration Release — 0 warnings, 0 errors
• ✅ dotnet test tests/FSharp.Markdown.Tests --configuration Release --no-build — 283/283 passed (includes 2 new tests)
• ✅ dotnet test FSharp.Formatting.sln --configuration Release --no-build — full suite passes (fsdocs-tool: 12, CodeFormat: 30, Literate: 143, ApiDocs: 88, Markdown: 283)
• ✅ dotnet fantomas … --check — formatting unchanged

Generated by 🌈 Repo Assist, see workflow run. Learn more.

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@e1ecf341a90b7bc2021e77c58685d7e269e20b99