按规划持续工作

结论：五轴 TRT boat demo 已通过 LinuxCNC vendored remap/tool-table/file 执行路径纳入 native、Node WASM、browser 和 UI 验证，未在 JS 或自有代码中实现 M428/M429/M430 或运动学语义。

wasm-port/docs/compatibility-validation.md

@@ -109,15 +109,16 @@ Emscripten filesystem through the SDK and runs them through LinuxCNC
 `Interp::open()`, `Interp::read()`, and `Interp::execute()` to validate the
 file execution path. It also writes the vendored LinuxCNC `xyzac-trt` and
 `xyzbc-trt` table-rotary-tilting sample machine INI, `remap_subs/*.ngc`, and
-`xyzac_switchkins.ngc`/`xyzbc_switchkins.ngc` demo files into the Emscripten
-filesystem, then validates the WASM C ABI/SDK path for vendored LinuxCNC
-`REMAP` parsing, O-word remap execution, `M68`/`M66` HAL synchronization, and
-file `open()`/`read()`/`execute()` completion without JavaScript M-code or
-kinematics semantics. The same Node smoke writes LinuxCNC-format parameter
-files into the Emscripten filesystem and validates vendored
-`Interp::restore_parameters()` and `Interp::save_parameters()`, including the
-saved parameter values, missing required numeric parameter defaulting, and the
-`.bak` backup file boundary. It also writes the
+`xyzac_switchkins.ngc`/`xyzbc_switchkins.ngc` plus `boat-xyzac.ngc` and
+`boat-xyzbc.ngc` demo files into the Emscripten filesystem, then validates the
+WASM C ABI/SDK path for vendored LinuxCNC `REMAP` parsing, vendored LinuxCNC
+tool-table loading from the machine INI, O-word remap execution, `M68`/`M66`
+HAL synchronization, and file `open()`/`read()`/`execute()` completion
+without JavaScript M-code or kinematics semantics. The same Node smoke writes
+LinuxCNC-format parameter files into the Emscripten filesystem and validates
+vendored `Interp::restore_parameters()` and `Interp::save_parameters()`,
+including the saved parameter values, missing required numeric parameter
+defaulting, and the `.bak` backup file boundary. It also writes the
 negative G-code fixtures into the Emscripten filesystem and verifies their
 LinuxCNC-produced error text through the `Interp::open()`/`read()`/`execute()`
 file path.
@@ -162,8 +163,8 @@ when a machine session is copied into the interpreter WASM filesystem. It also
 clicks the INI panel's 5-axis remap demo action and verifies that the UI
 copies vendored LinuxCNC `xyzac-trt` machine/remap/demo files into the
 interpreter WASM filesystem, calls the LinuxCNC-backed SDK remap execution
-path, and displays the resulting `fiveaxis_*` status lines without JavaScript
-M-code or kinematics semantics.
+path for the vendored `boat-xyzac.ngc` demo, and displays the resulting
+`fiveaxis_*` status lines without JavaScript M-code or kinematics semantics.
 
 The browser interpreter smoke script serves `wasm-port/` over localhost and
 runs Chromium headless against a test page that loads the interpreter-core
@@ -196,8 +197,9 @@ override INI-derived names before OPFS text is copied into the LinuxCNC-backed
 WASM filesystem, and that absent INI file-name values use the default OPFS
 parameter/tool-table paths in a real browser session. It also writes vendored
 LinuxCNC `xyzac-trt`/`xyzbc-trt` INI, remap subroutines, and switchkins demo
-files into the browser WASM filesystem and verifies `runFiveAxisRemapFile()`
-for both sample machines through the exported LinuxCNC remap/file execution
+files, including the larger `boat-xyzac.ngc` and `boat-xyzbc.ngc` demos, into
+the browser WASM filesystem and verifies `runFiveAxisRemapFile()` for both
+sample machines through the exported LinuxCNC remap/tool-table/file execution
 path.
 
 The aggregate host smoke script builds the INI, interpreter-core, and
@@ -228,7 +230,7 @@ The validation fails if:
 | `linuxcnc_interp_init_harness` | Validates vendored LinuxCNC `Interp::init()` emits canonical initialization boundaries, reads metric/inch machine units, and synchronizes current/selected tool slots through standalone status adapters. |
 | `linuxcnc_indexer_harness` | Validates vendored LinuxCNC single-axis rotary indexer dispatch emits lock/unlock and motion boundaries through the standalone event sink. |
 | `linuxcnc_remap_hal_sync_harness` | Validates vendored LinuxCNC `M68`/`M66` execution can drive the standalone HAL adapter boundary used by 5-axis switchkins remap files, including `_hal[motion.switchkins-type]` readback. |
-| `linuxcnc_5axis_remap_execute_harness` | Validates vendored LinuxCNC `REMAP` parsing plus NGC remap execution for the 5-axis `M429 -> M428 -> M430 -> M429` switchkins path in the `xyzac-trt` and `xyzbc-trt` sample machines, then runs vendored `xyzac_switchkins.ngc`, `xyzbc_switchkins.ngc`, `xyzac_switchkins_test_1.ngc`, and `xyzac_switchkins_test_3.ngc` through the LinuxCNC file `open/read/execute` path. |
+| `linuxcnc_5axis_remap_execute_harness` | Validates vendored LinuxCNC `REMAP` parsing plus NGC remap execution for the 5-axis `M429 -> M428 -> M430 -> M429` switchkins path in the `xyzac-trt` and `xyzbc-trt` sample machines, loads vendored machine tool tables through LinuxCNC `tooldata_load()`, then runs vendored `xyzac_switchkins.ngc`, `xyzbc_switchkins.ngc`, `xyzac_switchkins_test_1.ngc`, `xyzac_switchkins_test_3.ngc`, `boat-xyzac.ngc`, and `boat-xyzbc.ngc` through the LinuxCNC file `open/read/execute` path. |
 | `linuxcnc_tp_api_probe` | Validates vendored LinuxCNC trajectory planner calls for linear, arc, and queued motion paths. |
 | `linuxcnc_kinematics_probe` | Validates vendored LinuxCNC `trivkins.c` plus `kins_util.c` initialize and perform identity forward/inverse mapping through the standalone HAL/RTAPI boundary. |
 | `linuxcnc_5axis_kinematics_probe` | Validates vendored LinuxCNC `5axiskins.c` through `switchkins.c`, including 5-axis forward/inverse round-trip behavior and switching to identity kinematics. |

wasm-port/docs/porting-steps-standalone.md

@@ -802,24 +802,28 @@ Current five-axis switchkins status:
 5. `linuxcnc_remap_hal_sync_harness` validates vendored LinuxCNC `M68` and
    `M66` synchronization through the standalone HAL adapter boundary.
 6. `linuxcnc_5axis_remap_execute_harness` executes the `xyzac-trt` and
-   `xyzbc-trt` switchkins `M429 -> M428 -> M430 -> M429` paths plus vendored
-   `xyzac_switchkins.ngc`, `xyzbc_switchkins.ngc`,
-   `xyzac_switchkins_test_1.ngc`, and `xyzac_switchkins_test_3.ngc` through
-   LinuxCNC remap/file execution paths.
+   `xyzbc-trt` switchkins `M429 -> M428 -> M430 -> M429` paths, loads
+   vendored machine tool tables through LinuxCNC `tooldata_load()`, and runs
+   vendored `xyzac_switchkins.ngc`, `xyzbc_switchkins.ngc`,
+   `xyzac_switchkins_test_1.ngc`, `xyzac_switchkins_test_3.ngc`,
+   `boat-xyzac.ngc`, and `boat-xyzbc.ngc` through LinuxCNC remap/file
+   execution paths.
 7. The WASM interpreter core now links vendored `interp_remap.cc` plus the
    Python-only runtime edge stub, and the Node WASM smoke runs vendored
-   `xyzac_switchkins.ngc` and `xyzbc_switchkins.ngc` through the SDK C ABI
-   without JavaScript M-code or kinematics semantics.
+   `xyzac_switchkins.ngc`, `xyzbc_switchkins.ngc`, `boat-xyzac.ngc`, and
+   `boat-xyzbc.ngc` through the SDK C ABI without JavaScript M-code or
+   kinematics semantics.
 8. Browser smoke and the INI panel UI now expose the same validated 5-axis
    remap execution path by copying vendored LinuxCNC sample-machine files into
    the interpreter WASM filesystem and calling the SDK C ABI.
 
 Next work:
 
-1. Continue broadening five-axis fixture coverage after the native, Node WASM,
-   browser, and UI remap paths are stable.
-2. Evaluate larger vendored LinuxCNC TRT demos such as boat/impeller through
-   the same source-backed execution boundary.
+1. Continue broadening five-axis fixture coverage through the same
+   source-backed execution boundary.
+2. Evaluate remaining larger vendored LinuxCNC TRT demos such as impeller
+   after the boat demos are stable in native, Node WASM, browser, and UI
+   remap paths.
 
 Involved LinuxCNC source: