按规划继续工作

结论：解释器 WASM、SDK 统一入口、浏览器解释器 smoke 与兼容性文档已闭环，native 和 host/WASM/browser 验证全部通过。

wasm-port/docs/drift-report.md

@@ -49,7 +49,8 @@ semantic rewrites:
 - Do not edit `../linuxcnc/`.
 - Do not patch vendored files without adding a patch under `patches/` and
   documenting the reason.
-- Do not add standalone `Interp::convert_g()`.
+- Do not add standalone `Interp::...` member definitions outside the
+  documented Python/remap runtime-edge stubs.
 - Do not add `.c` or `.cc` manifest files without a source compile probe.
 - Do not sync from a different upstream commit without updating
   `tools/upstream-baseline.txt` and `docs/scope-and-baseline.md`.
@@ -58,8 +59,10 @@ semantic rewrites:
 
 - No browser/full-core WASM parity tests yet. The INI parser now has Node and
   Chromium smoke harnesses against vendored LinuxCNC `inifile.cc`.
-- JS SDK validation is currently limited to the INI WASM wrapper around
-  vendored LinuxCNC `inifile.cc`.
+- JS SDK validation now covers the INI WASM wrapper around vendored LinuxCNC
+  `inifile.cc` and the interpreter-core SDK wrapper around the existing
+  exported C ABI. The interpreter SDK only manages strings, Emscripten file
+  writes, and calls into vendored LinuxCNC execution paths.
 - OPFS validation covers a Node mock of the file-service adapter, the
   host-side path model, generic session snapshot storage, pure-text machine
   file and G-code storage, and a Chromium localhost round trip for those