按规划继续工作

结论：参数文件 restore/save 已通过解释器 WASM C ABI 直连 vendored LinuxCNC，native 与 host/WASM/browser 验证全部通过。

wasm-port/docs/compatibility-validation.md

@@ -87,7 +87,10 @@ required LinuxCNC `_setup` state readback with the matching files in
 `tests/fixtures/canon/`. It also writes selected G-code fixtures into the
 Emscripten filesystem through the SDK and runs them through LinuxCNC
 `Interp::open()`, `Interp::read()`, and `Interp::execute()` to validate the
-file execution path.
+file execution path. 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 and `.bak` backup file boundary.
 
 The OPFS host-boundary script validates the JavaScript file-service adapter
 with a Node mock of the browser File System Access handles. It covers nested
@@ -164,7 +167,7 @@ The validation fails if:
 | Harness | Purpose |
 | --- | --- |
 | `tests/wasm/node/verify_ini_wasm.sh` | Validates the browser-facing INI WASM module can be built from vendored LinuxCNC `inifile.cc`, loaded through the JS SDK in Node, and queried through the exported C ABI. |
-| `tests/wasm/node/verify_interp_wasm.sh` | Validates the initial interpreter-core WASM module can be built from vendored LinuxCNC interpreter source, loaded through the interpreter JS SDK, run the first fixture group through `Interp::execute()` and selected file fixtures through `Interp::open()`/`read()`/`execute()`, and match the native canonical event plus required state readback fixtures. |
+| `tests/wasm/node/verify_interp_wasm.sh` | Validates the initial interpreter-core WASM module can be built from vendored LinuxCNC interpreter source, loaded through the interpreter JS SDK, run the first fixture group through `Interp::execute()` and selected file fixtures through `Interp::open()`/`read()`/`execute()`, match the native canonical event plus required state readback fixtures, and run parameter-file restore/save through vendored LinuxCNC `Interp::restore_parameters()` and `Interp::save_parameters()`. |
 | `tests/opfs/node/verify_file_service.sh` | Validates the host-owned OPFS text-file adapter, path model, session snapshot store, machine file store, and G-code text store used by the browser INI panel without moving file persistence into the WASM core. |
 | `tests/browser/verify_ini_panel_browser.sh` | Validates the INI SDK, WASM module loading, OPFS text-file round trip, generic session snapshot round trip, machine file text round trip, and G-code text round trip in a real browser runtime. |
 | `tests/browser/verify_interp_browser.sh` | Validates the interpreter-core WASM module loads through the interpreter JS SDK in a real browser runtime and runs selected positive and negative canonical fixtures through vendored LinuxCNC `Interp::execute()` plus `Interp::open()`/`read()`/`execute()` via the exported C ABI. |
@@ -230,6 +233,11 @@ path additionally covers the same canonical-event fixture group, plus
 `position_params` uses a dedicated file-path expectation under
 `tests/fixtures/canon_file/` because LinuxCNC file execution advances the
 post-execute position parameters differently than the line-by-line MDI smoke.
+The Node WASM interpreter smoke also covers LinuxCNC parameter-file
+restore/save behavior through the exported C ABI, including out-of-order file
+rejection, missing-file success, required numeric parameter writeback, removal
+of named-parameter-only lines from saved output, and the `.bak` backup produced
+by vendored `save_parameters()`.
 OPFS validation is limited to the JavaScript host-boundary adapter plus the INI
 browser smoke harness. Full browser coverage, full SDK coverage, and full
 machine-session validation remain future work.

wasm-port/docs/drift-report.md

@@ -32,6 +32,7 @@ semantic rewrites:
 | Interpreter state tags | LinuxCNC `UPDATE_TAG` callbacks are captured from the state tags packed by vendored interpreter code; standalone code does not derive modal state. |
 | Rotary indexer lock state | LinuxCNC `UNLOCK_ROTARY` and `LOCK_ROTARY` callbacks are captured from the vendored single-axis indexer path; standalone code does not implement rotary-indexing semantics. |
 | File flush | LinuxCNC `FINISH` is captured as a canonical test event on the vendored `%`-delimited file-reading path. |
+| WASM parameter-file backup | LinuxCNC `save_parameters()` calls `link()` to create the `.bak` parameter-file backup; `runtime/core/linuxcnc_wrap/linuxcnc_wasm_posix_stubs.cpp` maps that WASM/MEMFS edge to a file copy so the vendored save path can run unchanged. |
 | Interpreter reset | LinuxCNC `ON_RESET` is captured as a canonical test event on the vendored interpreter reset/file-open path. |
 | Interpreter init | LinuxCNC `INIT_CANON` and the canonical initialization sequence from vendored `Interp::init()` are captured as test events. |
 | Comment logging | LinuxCNC `LOGOPEN`, `LOG`, `LOGAPPEND`, and `LOGCLOSE` callbacks are captured as canonical test events instead of writing host log files. |

wasm-port/docs/source-reuse-map.md

@@ -53,7 +53,7 @@ Current validation is intentionally mechanical:
 
 | Dependency | LinuxCNC files that expose it | Standalone treatment |
 | --- | --- | --- |
-| Native file IO | `inifile.cc`, `rs274ngc_pre.cc`, parameter file paths | Allowed in native probes; browser OPFS remains a host-side adapter under `runtime/opfs/`, with path ownership in `runtime/opfs/path-model.js`, generic snapshot persistence in `runtime/opfs/snapshot-store.js`, and pure-text machine-file persistence in `runtime/opfs/machine-file-store.js` |
+| Native file IO | `inifile.cc`, `rs274ngc_pre.cc`, parameter file paths | Allowed in native probes; the interpreter WASM C ABI now validates parameter-file restore/save by calling vendored `Interp::restore_parameters()` and `Interp::save_parameters()` against Emscripten filesystem paths; browser OPFS remains a host-side adapter under `runtime/opfs/`, with path ownership in `runtime/opfs/path-model.js`, generic snapshot persistence in `runtime/opfs/snapshot-store.js`, and pure-text machine-file persistence in `runtime/opfs/machine-file-store.js` |
 | RTAPI | `rtapi_*.h`, TP, posemath, motion headers | Minimal standalone shim in `runtime/core/shims/rtapi.h` |
 | NML transport | `emc.hh`, motion/NML type headers | Transport is not ported; only the status/type edges needed by vendored compute code are exposed through standalone shims and probes |
 | HAL runtime | named parameter lookup, kinematics component lifecycle, and runtime status edges | Standalone HAL adapter under `runtime/core/linuxcnc_wrap/` |
@@ -73,15 +73,17 @@ Current validation is intentionally mechanical:
 - Browser/WASM C ABI and JS SDK layers are now present for the INI parser and
   the current interpreter-core smoke scope. The interpreter SDK is a thin
   allocation, filesystem, and C ABI wrapper over vendored LinuxCNC execution
-  paths; it does not define G-code semantics. Full planner/session SDK
-  coverage remains future work.
+  paths, including parameter-file restore/save through vendored
+  `rs274ngc_pre.cc`; it does not define G-code or parameter semantics. Full
+  planner/session SDK coverage remains future work.
 - OPFS persistence is connected to the INI panel through the host-side
   `runtime/opfs/file-service.js` adapter. `runtime/opfs/path-model.js` now
   defines paths for INI, tool table, parameter file, G-code program,
   preview-cache, and session-snapshot targets. `runtime/opfs/snapshot-store.js`
   adds a generic JSON session snapshot envelope.
   `runtime/opfs/machine-file-store.js` adds pure-text storage for INI, tool
-  table, parameter file, and G-code program content; semantic loading for tool
-  tables, parameter files, G-code programs, and machine-state restoration
-  remains future work.
+  table, parameter file, and G-code program content; browser session plumbing
+  that feeds OPFS-backed parameter files into the existing WASM
+  `restore_parameters()`/`save_parameters()` ABI, plus semantic loading for
+  tool tables and machine-state restoration, remains future work.
 - Native LinuxCNC GUI code remains out of scope for implementation.