按规划继续工作

结论：补齐 INI 派生参数文件和刀具表 OPFS 会话加载，扩大浏览器解释器 file-path fixture 覆盖，并通过 host/WASM/browser 聚合验证。

wasm-port/docs/compatibility-validation.md

@@ -120,7 +120,8 @@ exported C ABI backed by vendored LinuxCNC `Interp::execute()` and
 named-parameter file path and negative interpreter fixtures with expected
 error text plus absent canonical motion output. It also uses real browser OPFS
 storage plus the interpreter SDK to restore and save a LinuxCNC parameter file
-through vendored `Interp::restore_parameters()` and `Interp::save_parameters()`.
+through vendored `Interp::restore_parameters()` and `Interp::save_parameters()`,
+and to load/save LinuxCNC tool tables through vendored `tooldata_common.cc`.
 
 The aggregate host smoke script builds the INI and interpreter-core WASM
 artifacts once, then runs the Node WASM smokes, the Node OPFS mock smoke, and
@@ -254,10 +255,11 @@ the raw canonical-event display fed directly by LinuxCNC interpreter WASM
 output, the Node parameter/tool-table bridges that copy OPFS text through the
 SDK into vendored LinuxCNC file APIs, the Node machine-session bridge that
 groups INI, parameter, and tool-table loading, the random-toolchanger flag
-derived from vendored LinuxCNC INI boolean parsing and passed through to the
-LinuxCNC-backed tool-table ABI, and a browser interpreter smoke that uses the
-same session bridge before saving OPFS-backed parameter and tool-table text
-through vendored LinuxCNC file APIs.
+derived from vendored LinuxCNC INI boolean parsing, INI-derived
+`[RS274NGC]PARAMETER_FILE` and `[EMCIO]TOOL_TABLE` file names mapped to OPFS
+machine files, and a browser interpreter smoke that uses the same session
+bridge before saving OPFS-backed parameter and tool-table text through
+vendored LinuxCNC file APIs.
 Full browser coverage, full SDK coverage, and richer machine-state validation
 remain future work.
 
@@ -367,12 +369,36 @@ Browser interpreter negative coverage currently includes every fixture under
 - `tool_length_offset_not_found`
 - `tool_not_found`
 
-Browser interpreter file-path coverage currently includes:
+Browser interpreter file-path coverage currently includes the same
+`INTERP_FILE_FIXTURES` list as the Node WASM smoke:
 
-- `position_params` through the dedicated `canon_file/` expectation
+- `minimal_linear`
+- `arc_semantics`
+- `length_units`
+- `modal_incremental`
+- `plane_selection`
+- `coordinate_offsets`
+- `g53_machine_coordinates`
+- `feed_control_modes`
+- `probe_semantics`
+- `spindle_orient`
+- `comment_logging`
+- `numbered_params`
+- `tool_semantics`
+- `tool_table_setup`
+- `tool_reload`
+- `canned_cycles`
+- `cutter_comp_motion`
+- `threading_sync`
+- `nurbs_g5_semantics`
+- `nurbs_g6_semantics`
+- `state_tag_motion`
+- `canon_runtime_edges`
+- `program_end_modal_reset`
 - `file_open_reset`
 - `percent_file_finish`
 - `oword_subroutine`
+- `position_params` through the dedicated `canon_file/` expectation
 - `namedparam_semantics` through the INI-aware file ABI
 
 All current positive G-code fixtures have browser interpreter smoke coverage