按text25.txt规划,实现L4-PYTHON-REMAP接入数控系统仿真系统

结论:已接入Python remap runtime proof chain,覆盖native、WASM、browser与release gate证据链;继续保持promotion_allowed=0,不批量解锁L4-PYTHON-REMAP。
This commit is contained in:
2026-06-19 18:52:24 +08:00
parent 51ae5d9a9a
commit fbf9dade9c
38 changed files with 2252 additions and 335 deletions

View File

@@ -589,6 +589,19 @@ private module paths:
- `saveToolDbFile()`, `loadToolDbFile()`, `saveToolDbTranscript()`, and
`loadToolDbTranscript()` for OPFS persistence of the DB flat file and protocol
transcript artifacts.
- `createLinuxCncPythonRemapRuntimePort()`, `createPythonRemapLifecyclePlan()`,
`validatePythonRemapLifecycleTranscript()`, and
`createPythonRemapRuntimeDiagnostics()` for the first Python remap lifecycle
contract around `axis/remap/stop-lookahead/nc_files`. Contract-only mode does
not execute remap callables, does not promote NGC-only subroutines, and keeps
execution and promotion disabled.
- `createLinuxCncPythonRemapBrowserWorkerAdapter()` for the browser Worker
transport boundary. The bundled worker reports
`blocked_browser_python_wasm_runtime_missing` until a Python/WASM provider
supplies the controlled lifecycle methods for initializing Python, applying
the INI `[PYTHON]PATH_PREPEND`, executing `[PYTHON]TOPLEVEL`, importing the
configured module, looking up the configured callable, and observing the
generator lifecycle.
These helpers only move and validate host files. Parameter and tool-table
effects still come from the LinuxCNC-backed interpreter SDK methods they call.