接入虚拟HAL宏加载非主程序证据

wasm-port/docs/sim-config-coverage-promotion-analysis.md

@@ -229,10 +229,34 @@ inventory `PASS` with matrix `INV`; the added value is explicit browser
 diagnostics evidence and release-gate enforcement that the virtual HAL reports
 are complete for non-Qt sim-config families.
 
-The next practical promotion slice is to design non-main macro/load fixture
-evidence, starting with `axis/rose_engine/rcone.ngc` paired to
-`rcone_demo.ngc`, without executing macro/load rows as standalone browser main
-programs.
+## 2026-06-18 Macro/Load Non-Main Fixture Evidence
+
+The virtual HAL diagnostics evidence now includes an explicit macro/load
+fixture report:
+
+- `VIRTUAL_HAL_SIM_CONFIG_MACRO_LOAD_FIXTURES`
+- `createVirtualHalSimConfigMacroLoadFixtureReport()`
+
+The first required non-main fixtures are:
+
+- `axis/rose_engine/rcone.ngc`
+- `axis/external_offsets/queuebuster.ngc`
+
+The rose-engine fixture is paired with `rcone_demo.ngc` and keeps `rcone.ngc`
+as a non-main macro/load asset. The external-offsets fixture records
+`queuebuster.ngc` as a declared `NGCGUI_SUBFILE` through `eoffsets.ini`; the
+fixture path is preserved for diagnostics, while the manifest-backed source
+evidence is the owning INI and paired LinuxCNC program source. This avoids
+pretending that `queuebuster.ngc` is a standalone browser main program.
+
+Release diagnostics validation now requires
+`virtualHalSimConfigMacroLoadFixtures` to be present and ready. The report must
+keep `inventoryBaselineUnchanged === true`, every row must have
+`nonMainFixture === true`, and `standaloneMainViolations` must stay empty.
+
+The next practical slice is to extend this report with one more non-main family
+such as `gscreen/silverdragon/macros/tool_sensor.ngc`, after proving the owning
+machine files and UI/process boundary do not cross into Python UI emulation.
 
 ## Boundary Statement