按建议，继续完成后续工作

结论：state_tag_motion 已补充 LinuxCNC motion 事件并纳入 upstream rs274 side-by-side baseline，UPDATE_TAG 仍由 standalone native harness 验证，完整 native probes 验证通过。

wasm-port/docs/compatibility-validation.md

@@ -124,9 +124,9 @@ The current fixture expectations validate standalone behavior against both the
 vendored LinuxCNC source path and an upstream `rs274` side-by-side baseline for
 parser/conversion, arc geometry, offsets, feed-control, comment/logging,
 numbered-parameter, probing, spindle-orient, file-open reset, file-finish,
-tool-reload, canned-cycle, and O-word subroutine fixtures, plus
-threading/rigid tap, NURBS dispatch boundaries, and the comparable canonical
-runtime edge and program-end cleanup calls. Fixtures that depend on
+tool-reload, canned-cycle, state-tag motion, and O-word subroutine fixtures,
+plus threading/rigid tap, NURBS dispatch boundaries, and the comparable
+canonical runtime edge and program-end cleanup calls. Fixtures that depend on
 standalone-only runtime adapters, HAL/INI/tool table setup, upstream `rs274`
 output gaps such as `WAIT` or hidden NURBS control-point detail, or richer
 machine session state still need dedicated native LinuxCNC baselines.
@@ -134,9 +134,9 @@ machine session state still need dedicated native LinuxCNC baselines.
 Remaining positive fixtures that are not in the upstream `rs274` side-by-side
 baseline are intentionally held out until they get a dedicated native LinuxCNC
 baseline: `namedparam_semantics` depends on standalone INI/HAL adapter
-resolution, `state_tag_motion` validates the standalone state-tag capture
-boundary, and `tool_semantics`/`tool_table_setup` depend on tool table host
-state.
+resolution, and `tool_semantics`/`tool_table_setup` depend on tool table host
+state. `state_tag_motion` now compares its motion events with upstream `rs274`,
+while `UPDATE_TAG` events remain a standalone state-tag capture boundary.
 
 The kinematics probes currently cover LinuxCNC identity/trivial kinematics, the
 switchable `5axiskins` XYZBCW bridge-mill model, TRT `xyzac`/`xyzbc`

wasm-port/docs/drift-report.md

@@ -69,11 +69,12 @@ semantic rewrites:
   path. The upstream `rs274` side-by-side baseline now covers simple motion,
   arc geometry, offsets, feed-control, comment/logging, numbered-parameter,
   probing, spindle-orient, file-open reset, file-finish, tool-reload, and
-  canned-cycle and O-word subroutine fixtures; it also covers threading/rigid
-  tap, NURBS dispatch boundaries, and comparable canonical runtime edge and
-  program-end cleanup calls. Adapter-heavy fixtures, standalone modal-state
-  assertions, and upstream `rs274` output gaps such as `WAIT` or hidden NURBS
-  control-point detail still need dedicated native LinuxCNC baselines.
+  canned-cycle, state-tag motion, and O-word subroutine fixtures; it also
+  covers threading/rigid tap, NURBS dispatch boundaries, and comparable
+  canonical runtime edge and program-end cleanup calls. Adapter-heavy fixtures,
+  standalone modal-state assertions, and upstream `rs274` output gaps such as
+  `WAIT` or hidden NURBS control-point detail still need dedicated native
+  LinuxCNC baselines.
 - `canned_cycles` is now in the upstream `rs274` side-by-side baseline after
   the minimal interpreter harness was aligned with LinuxCNC `Interp::init()`
   default `G73/G83` peck-clearance values for millimeter units.

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

@@ -1,2 +1,5 @@
 canon_event=UPDATE_TAG line=1
+canon_event=STRAIGHT_TRAVERSE line=1 x=1 y=2 z=0 a=0 b=0 c=0 u=0 v=0 w=0
+canon_event=SET_FEED_RATE rate=120
 canon_event=UPDATE_TAG line=2
+canon_event=STRAIGHT_FEED line=2 x=3 y=4 z=0 a=0 b=0 c=0 u=0 v=0 w=0

wasm-port/tools/verify_native_linuxcnc_fixture_baseline.sh

@@ -29,6 +29,7 @@ FIXTURES=(
   probe_semantics
   program_end_modal_reset
   spindle_orient
+  state_tag_motion
   threading_sync
   tool_reload
 )