按建议，继续完成后续工作

结论：已将 INI 面板的 OPFS 文本文件读写抽为 host-side file-service，并新增 Node mock 验证，确认 OPFS 边界不进入 WASM core 且可覆盖保存、读取、缺失路径和非法路径行为。

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

@@ -51,7 +51,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 future adapter |
+| 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/` |
 | 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/` |
@@ -70,6 +70,7 @@ Current validation is intentionally mechanical:
   fixture-covered through vendored `interp_convert.cc` and `interp_queue.cc`.
 - Browser/WASM C ABI and JS SDK layers are not yet built for the full
   interpreter/planner core. The INI parser has a Node WASM smoke harness.
-- OPFS persistence is not yet connected to INI, tool table, parameter file, or
-  G-code program loading.
+- OPFS persistence is connected to the INI panel through the host-side
+  `runtime/opfs/file-service.js` adapter; tool table, parameter file, G-code
+  program loading, and browser-level OPFS validation remain future work.
 - Native LinuxCNC GUI code remains out of scope for implementation.