数控系统仿真软件，从linuxcnc移植过来的

结论：新增 coordinate_offsets 文件执行路径专用 WASM/浏览器验证，保留 MDI 路径状态读回，并通过 native、Node WASM、browser 与 host 聚合 smoke 验证。

wasm-port/docs/compatibility-validation.md

@@ -297,6 +297,11 @@ file execution ABI,
 post-execute position parameters differently than the line-by-line MDI smoke;
 both expectations now also pin post-execute modal, override, spindle, mist,
 and flood `_setup` state readback.
+`coordinate_offsets` also uses a dedicated file-path expectation because
+LinuxCNC file execution leaves the post-execute position parameters at the
+file-path reset state while the line-by-line MDI path exposes the active G55
+offset values; both paths pin the post-execute modal, override, spindle, mist,
+and flood `_setup` state.
 `tool_semantics` also pins the post-execute position-parameter and modal,
 override, spindle, mist, and flood `_setup` state after T/M6/G43/G49/M61
 tool behavior.
@@ -397,7 +402,6 @@ Node WASM file-path coverage currently includes:
 - `length_units`
 - `modal_incremental`
 - `plane_selection`
-- `coordinate_offsets`
 - `g53_machine_coordinates`
 - `feed_control_modes`
 - `probe_semantics`
@@ -418,6 +422,7 @@ Node WASM file-path coverage currently includes:
 - `file_open_reset`
 - `percent_file_finish`
 - `oword_subroutine`
+- `coordinate_offsets` through the dedicated `canon_file/` expectation
 - `position_params` through the dedicated `canon_file/` expectation
 - `namedparam_ini_semantics` through the INI-aware file ABI
 - `namedparam_semantics` through the INI-aware file ABI
@@ -498,7 +503,6 @@ Browser interpreter file-path coverage currently includes the same
 - `length_units`
 - `modal_incremental`
 - `plane_selection`
-- `coordinate_offsets`
 - `g53_machine_coordinates`
 - `feed_control_modes`
 - `probe_semantics`
@@ -519,6 +523,7 @@ Browser interpreter file-path coverage currently includes the same
 - `file_open_reset`
 - `percent_file_finish`
 - `oword_subroutine`
+- `coordinate_offsets` through the dedicated `canon_file/` expectation
 - `position_params` through the dedicated `canon_file/` expectation
 - `namedparam_ini_semantics` through the INI-aware file ABI
 - `namedparam_semantics` through the INI-aware file ABI
@@ -538,9 +543,9 @@ canned-cycle, state-tag motion, tool-table setup, and O-word subroutine
 fixtures, plus threading/rigid tap, NURBS dispatch boundaries, and the
 comparable canonical runtime edge and program-end cleanup calls. The
 standalone vendored-source harness, Node WASM smoke, and browser smoke also
-pin `feed_control_modes`, the `position_params` MDI/file-path,
-`tool_semantics`, and `canon_runtime_edges` post-program modal, override,
-spindle, mist, and flood `_setup` state. The same upstream baseline also
+pin `coordinate_offsets` MDI/file-path, `feed_control_modes`, the
+`position_params` MDI/file-path, `tool_semantics`, and `canon_runtime_edges`
+post-program modal, override, spindle, mist, and flood `_setup` state. The same upstream baseline also
 validates the current negative fixture error text and absent canonical-event
 constraints. Fixtures that depend on standalone-only runtime
 adapters, HAL state, upstream `rs274` output gaps such as