Complete sim config boundary coverage

wasm-port/runtime/sdk/README.md

@@ -23,6 +23,7 @@ Use `src/index.js` for stable imports:
 
 ```js
 import {
+  analyzeIniRuntimeBoundaries,
   createLinuxCncIniSdk,
   createLinuxCncInterpSdk,
   planIniFileContextStaging,
@@ -104,6 +105,20 @@ source manifest text, machine relative path, INI file name, and INI text. It
 uses `planIniFileContextStaging()` with a `configs/sim/<machine>` source root
 and `configs/sim` upward-search boundary.
 
+`analyzeIniRuntimeBoundaries()` is a host-boundary classifier for LinuxCNC
+INI-driven runs. It reads INI text plus optional execution text and manifest
+text, then reports declared HAL, UI, HALUI MDI, Python, tool-database, and
+external user-M process dependencies. User-M accounting is per execution code:
+`executionCodes` lists `M100..M199` codes seen in the supplied execution text,
+while `unstagedExecutionCodes` lists the subset not backed by vendored
+`USER_M_PATH` files. Python accounting keeps UI/DB references separate from
+Python remap runtime references, so a UI handler or DB program does not imply
+Python-remap coverage. It also returns the currently recommended Layer 4
+blocked kind for hard process boundaries such as `L4-TOOL-DB` and
+`L4-USER-M-PROCESS`. The classifier is policy/accounting only: it does not
+execute HAL, task, UI, Python, user-M, or tool-database behavior and does not
+change interpreter semantics.
+
 `runFileWithIniContinueOnError()` uses the same LinuxCNC-backed file execution
 path but keeps the runner loop going after LinuxCNC reports an error, matching
 upstream `rs274 -n 0` regression tests such as `tests/interp/oword-unwind`.