按规划继续工作

结论：扩展 tool_semantics 期望，固定 T/M6/G43/G49/M61 后 vendored LinuxCNC 的位置参数与 post-execute modal、override、spindle、mist、flood 状态读回，并同步验证文档。

wasm-port/docs/compatibility-validation.md

@@ -297,6 +297,9 @@ 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.
+`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.
 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.
@@ -532,10 +535,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 `position_params` MDI/file-path 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
+pin 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
 `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,9 @@ 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 `position_params` MDI/file-path and `canon_runtime_edges` post-program
-  modal, override, spindle, mist, and flood `_setup` state. It now also checks the negative fixture set
+  the `position_params` MDI/file-path, `tool_semantics`, and
+  `canon_runtime_edges` post-program 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/tool_semantics.events

@@ -9,3 +9,19 @@ canon_event=USE_TOOL_LENGTH_OFFSET x=0 y=0 z=0 a=0 b=0 c=0 u=0 v=0 w=0
 canon_event=MESSAGE:  tool g49 offset=0 x=0.0000 y=0.0000 z=0.0000
 canon_event=CHANGE_TOOL_NUMBER pocket=2
 canon_event=MESSAGE:  tool after_m61 current_pocket=2 current_tool=2
+setup.current_x=0
+setup.current_y=0
+setup.current_z=0
+setup.parameter_5420=0
+setup.parameter_5421=0
+setup.parameter_5422=0
+post_execute.plane=1
+post_execute.distance_mode=0
+post_execute.feed_mode=0
+post_execute.motion_mode=0
+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