按规划继续工作

结论：扩展 position_params 的 MDI 与 file-path 期望，固定 vendored LinuxCNC 执行后的 modal、override、spindle、mist、flood 状态读回，并同步验证文档。

wasm-port/docs/compatibility-validation.md

@@ -294,7 +294,9 @@ file execution ABI,
 `file_open_reset`, `percent_file_finish`, and `oword_subroutine`.
 `position_params` uses a dedicated file-path expectation under
 `tests/fixtures/canon_file/` because LinuxCNC file execution advances the
-post-execute position parameters differently than the line-by-line MDI smoke.
+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.
 The same Node WASM and browser file-path smokes also cover the negative fixture
 group and check the LinuxCNC file-execution error text plus absent canonical
 motion constraints where applicable.
@@ -530,10 +532,10 @@ 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 the `canon_runtime_edges` post-program modal, override, spindle, mist, and
+pin the `position_params` MDI/file-path and `canon_runtime_edges` post-program
-flood `_setup` state. The same upstream baseline also validates the current
+modal, override, spindle, mist, and flood `_setup` state. The same upstream
-negative fixture error text and absent canonical-event constraints. Fixtures
+baseline also validates the current negative fixture error text and absent
-that depend on standalone-only runtime
+canonical-event constraints. Fixtures that depend on standalone-only runtime
 adapters, HAL state, upstream `rs274` output gaps such as
 `WAIT` or hidden NURBS control-point detail, or richer machine session state
 still need dedicated native LinuxCNC baselines.

wasm-port/docs/drift-report.md

@@ -98,8 +98,8 @@ semantic rewrites:
   fixtures; it also covers threading/rigid tap, NURBS dispatch boundaries, and
   comparable canonical runtime edge and program-end cleanup calls. The
   vendored-source native harness plus Node WASM and browser smokes also pin
-  the `canon_runtime_edges` post-program modal, override, spindle, mist, and
+  the `position_params` MDI/file-path and `canon_runtime_edges` post-program
-  flood `_setup` state. It now also checks the negative fixture set
+  modal, override, spindle, mist, and flood `_setup` state. It now also checks the negative fixture set
   against upstream `rs274 -g` for expected error text and absent canonical
   event constraints.
   HAL-backed adapter-heavy fixtures, standalone modal-state assertions, and upstream

wasm-port/tests/fixtures/canon/position_params.events

@@ -8,3 +8,13 @@ setup.current_z=5
 setup.parameter_5420=1
 setup.parameter_5421=2
 setup.parameter_5422=3
+post_execute.plane=1
+post_execute.distance_mode=1
+post_execute.feed_mode=0
+post_execute.motion_mode=10
+post_execute.origin_index=0
+post_execute.feed_override=0
+post_execute.speed_override_0=0
+post_execute.spindle_turning_0=1
+post_execute.mist=0
+post_execute.flood=0

wasm-port/tests/fixtures/canon_file/position_params.events

@@ -11,5 +11,13 @@ setup.current_z=5
 setup.parameter_5420=1.5
 setup.parameter_5421=1
 setup.parameter_5422=5
+post_execute.plane=1
 post_execute.distance_mode=1
+post_execute.feed_mode=0
 post_execute.motion_mode=10
+post_execute.origin_index=0
+post_execute.feed_override=0
+post_execute.speed_override_0=0
+post_execute.spindle_turning_0=1
+post_execute.mist=0
+post_execute.flood=0