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

结论：minimal interpreter harness 已按 LinuxCNC Interp::init 对齐 G73/G83 毫米默认 peck-clearance，canned_cycles 已纳入 upstream rs274 side-by-side baseline，完整 native probes 验证通过。

wasm-port/docs/compatibility-validation.md

@@ -124,20 +124,19 @@ 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, 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, 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.
 
 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: `canned_cycles` currently exposes G83 retract-height canonical detail
-that should not be filtered away, `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.
+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.
 
 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,14 +69,14 @@ 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
-  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 not yet in the upstream `rs274` side-by-side baseline
-  because G83 currently exposes retract-height canonical detail that needs a
-  dedicated native LinuxCNC baseline instead of broad event filtering.
+  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_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.
 
 ## Current Drift Conclusion