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

结论：tool_table_setup 已通过专用 rs274 -t 工具表和毫米单位 INI 纳入 upstream side-by-side baseline，完整 native probes 验证通过。

wasm-port/docs/compatibility-validation.md

@@ -124,19 +124,20 @@ 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, 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.
+tool-reload, 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. Fixtures
+that depend on standalone-only runtime adapters, HAL/INI/tool-change 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.
 
 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, 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.
+resolution, and `tool_semantics` depends on tool-change 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,15 +69,17 @@ 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, 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-cycle, state-tag motion, tool-table setup, 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.
+- `tool_table_setup` is now in the upstream `rs274` side-by-side baseline using
+  a dedicated `rs274 -t` tool table and `-i` millimeter-unit INI boundary.
 
 ## Current Drift Conclusion