按规划继续工作

结论：OPFS 参数文件已通过桥接进入 LinuxCNC-backed WASM restore/save 路径，native 与 host/WASM/browser 验证全部通过。

wasm-port/docs/compatibility-validation.md

@@ -99,7 +99,10 @@ paths, unavailable OPFS storage, and the host-side OPFS path model for INI,
 tool table, parameter, G-code, preview-cache, and session-snapshot storage
 targets. It also validates the host-side session snapshot JSON envelope and
 round-trip store plus pure-text machine file and G-code stores without
-defining CNC machine-state or file-format semantics.
+defining CNC machine-state or file-format semantics. It now also validates the
+OPFS-to-WASM parameter-file bridge with a mock interpreter SDK to ensure the
+host boundary copies text into and out of the WASM filesystem without defining
+parameter semantics.
 
 The browser INI/OPFS smoke script serves `wasm-port/` over localhost and runs
 Chromium headless against a test page that imports the JS SDK, loads the INI
@@ -114,7 +117,9 @@ behavior in JavaScript, and verifies existing canonical fixtures through the
 exported C ABI backed by vendored LinuxCNC `Interp::execute()` and
 `Interp::open()`/`read()`/`execute()` paths, including the INI-aware
 named-parameter file path and negative interpreter fixtures with expected
-error text plus absent canonical motion output.
+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()`.
 
 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
@@ -168,9 +173,9 @@ The validation fails if:
 | --- | --- |
 | `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()`, 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/opfs/node/verify_file_service.sh` | Validates the host-owned OPFS text-file adapter, path model, session snapshot store, machine file store, G-code text store, and OPFS-to-WASM parameter-file bridge without moving file persistence or parameter semantics 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. |
+| `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, including OPFS-backed parameter-file restore/save through vendored LinuxCNC source. |
 | `tests/host/verify_host_smokes.sh` | Runs the current host-side Node, WASM interpreter-core, OPFS, and browser smoke validation with shared WASM builds. |
 
 ## Fixture Coverage
@@ -238,8 +243,10 @@ 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
+OPFS validation covers the JavaScript host-boundary adapter, the INI browser
+smoke harness, and a browser interpreter smoke that copies OPFS-backed
+parameter text through the SDK into vendored LinuxCNC parameter-file
+restore/save. Full browser coverage, full SDK coverage, and full
 machine-session validation remain future work.
 
 ## WASM/Browser Fixture Matrix

wasm-port/docs/drift-report.md

@@ -43,7 +43,7 @@ semantic rewrites:
 | Kinematics component lifecycle | Kinematics modules are initialized through LinuxCNC module entry points where native runtime probes exist, while HAL component init/ready/exit, HAL pin allocation, and RTAPI module metadata are handled by standalone shims. |
 | Go math C/C++ linkage | `genserkins` runtime probing compiles vendored `gomath.c` through a narrow C++ wrapper so LinuxCNC `genserfuncs.c` can link to the upstream Go math symbols without editing vendored source. |
 | Switchkins iterative forward | `genhexkins` runtime probing follows LinuxCNC switchkins iterative-forward behavior, including the first-call warmup path before asserting roundtrip convergence. |
-| Browser storage | OPFS remains outside the native core; `runtime/opfs/file-service.js` owns browser text-file persistence, `runtime/opfs/path-model.js` owns host-side storage paths for INI, tool table, parameter, G-code, preview-cache, and session-snapshot content, `runtime/opfs/snapshot-store.js` owns generic JSON session snapshot persistence, and `runtime/opfs/machine-file-store.js` owns pure-text machine-file and G-code persistence. |
+| Browser storage | OPFS remains outside the native core; `runtime/opfs/file-service.js` owns browser text-file persistence, `runtime/opfs/path-model.js` owns host-side storage paths for INI, tool table, parameter, G-code, preview-cache, and session-snapshot content, `runtime/opfs/snapshot-store.js` owns generic JSON session snapshot persistence, `runtime/opfs/machine-file-store.js` owns pure-text machine-file and G-code persistence, and `runtime/opfs/linuxcnc-parameter-bridge.js` only copies parameter files between OPFS text storage and the LinuxCNC-backed WASM parameter-file ABI. |
 
 ## Enforced Non-Drift Rules
 

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; 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` |
+| Native file IO | `inifile.cc`, `rs274ngc_pre.cc`, parameter file paths | Allowed in native probes; the interpreter WASM C ABI 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`, pure-text machine-file persistence in `runtime/opfs/machine-file-store.js`, and OPFS-to-WASM parameter-file copying in `runtime/opfs/linuxcnc-parameter-bridge.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/` |
@@ -82,8 +82,9 @@ Current validation is intentionally mechanical:
   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; 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.
+  table, parameter file, and G-code program content.
+  `runtime/opfs/linuxcnc-parameter-bridge.js` copies OPFS-backed parameter
+  files into the interpreter SDK filesystem and writes back the LinuxCNC-saved
+  parameter file plus backup; UI-level session plumbing, semantic loading for
+  tool tables, and machine-state restoration remain future work.
 - Native LinuxCNC GUI code remains out of scope for implementation.