按规划继续工作

结论：新增 namedparam_ini_semantics 夹具，将本地命名参数和 _ini[...] 查询纳入 upstream rs274 -i 基线，并接入 Node WASM 与浏览器 INI-aware 解释器 smoke；HAL 查询继续保留在 standalone adapter 边界。

wasm-port/docs/compatibility-validation.md

@@ -250,7 +250,7 @@ Positive G-code fixtures currently cover:
 - percent-delimited file `FINISH` boundary
 - file-open `ON_RESET` boundary
 - comment logging canonical calls
-- named and numbered parameters
+- local, INI-backed named parameters and numbered parameters
 - O-word subroutines
 - program-end modal reset
 - canonical runtime edge calls
@@ -276,14 +276,16 @@ for `minimal_linear`, `arc_semantics`, `length_units`, `modal_incremental`,
 `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`, and `namedparam_semantics`
-through both Node WASM and browser INI-aware program ABI smoke coverage,
+`canon_runtime_edges`, `program_end_modal_reset`, `namedparam_ini_semantics`,
+and `namedparam_semantics` through both Node WASM and browser INI-aware
+program ABI smoke coverage,
 plus the `g1_zero_feed`, `arc_radius_mismatch`, `arc_zero_radius`,
 `cutter_comp_plane_change`, `g53_incremental`, `namedparam_readonly`,
 `numbered_param_readonly`, `tool_not_found`, and
 `tool_length_offset_not_found` negative fixtures. The WASM interpreter file
 path additionally covers the same canonical-event fixture group, plus
-`namedparam_semantics` through the INI-aware file execution ABI,
+`namedparam_ini_semantics` and `namedparam_semantics` through the INI-aware
+file execution ABI,
 `file_open_reset`, `percent_file_finish`, and `oword_subroutine`.
 `position_params` uses a dedicated file-path expectation under
 `tests/fixtures/canon_file/` because LinuxCNC file execution advances the
@@ -369,6 +371,7 @@ Node WASM `Interp::execute()` coverage currently includes:
 - `state_tag_motion`
 - `canon_runtime_edges`
 - `program_end_modal_reset`
+- `namedparam_ini_semantics` through the INI-aware program ABI
 - `namedparam_semantics` through the INI-aware program ABI
 
 Node WASM file-path coverage currently includes:
@@ -400,6 +403,7 @@ Node WASM file-path coverage currently includes:
 - `percent_file_finish`
 - `oword_subroutine`
 - `position_params` through the dedicated `canon_file/` expectation
+- `namedparam_ini_semantics` through the INI-aware file ABI
 - `namedparam_semantics` through the INI-aware file ABI
 
 Node WASM file-path negative coverage currently includes every fixture under
@@ -454,6 +458,7 @@ Browser interpreter `Interp::execute()` coverage currently includes:
 - `canon_runtime_edges`
 - `tool_reload`
 - `program_end_modal_reset`
+- `namedparam_ini_semantics` through the INI-aware program ABI
 - `namedparam_semantics` through the INI-aware program ABI
 
 Browser interpreter negative coverage currently includes every fixture under
@@ -499,6 +504,7 @@ Browser interpreter file-path coverage currently includes the same
 - `percent_file_finish`
 - `oword_subroutine`
 - `position_params` through the dedicated `canon_file/` expectation
+- `namedparam_ini_semantics` through the INI-aware file ABI
 - `namedparam_semantics` through the INI-aware file ABI
 
 All current positive G-code fixtures have browser interpreter smoke coverage
@@ -509,24 +515,27 @@ 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 and feed-state
 readback, comment/logging,
-numbered-parameter, probing, spindle-orient, file-open reset, file-finish,
+numbered-parameter, local named-parameter plus `_ini[...]` lookup through
+`rs274 -i`, probing, spindle-orient, file-open reset, file-finish,
 tool-reload, tool select/change/length-offset, 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
+adapters, HAL/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. `state_tag_motion` now compares its motion events with upstream
-`rs274`, while `UPDATE_TAG` events remain a standalone state-tag capture
-boundary. `tool_semantics` now compares T/M6/G43/G49 canonical events with
-upstream `rs274`; M61 current-pocket host-state behavior remains covered by the
-standalone fixture expectation, and `Interp::synch()` current/selected tool
-slot reads are covered by the native init harness.
+baseline: `namedparam_semantics` still depends on the standalone HAL adapter,
+while `namedparam_ini_semantics` now covers the local named-parameter and
+LinuxCNC `_ini[...]` subset against upstream `rs274 -i`. `state_tag_motion`
+now compares its motion events with upstream `rs274`, while `UPDATE_TAG`
+events remain a standalone state-tag capture boundary. `tool_semantics` now
+compares T/M6/G43/G49 canonical events with upstream `rs274`; M61
+current-pocket host-state behavior remains covered by the standalone fixture
+expectation, and `Interp::synch()` current/selected tool slot reads are
+covered by the native init harness.
 
 The kinematics probes currently cover LinuxCNC identity/trivial kinematics, the
 switchable `5axiskins` XYZBCW bridge-mill model, TRT `xyzac`/`xyzbc`