先提交到云仓库

结论：已提交当前 Python-remap proof 链路、runtime/browser/UI/docs 相关变更；保持 L4-PYTHON-REMAP inventory baseline 不直接批量 PASS。

wasm-port/docs/compatibility-validation.md

@@ -200,6 +200,8 @@ wasm-port/build/wasm/sim-configs-inventory/python-remap-native-runtime-probe-gat
 wasm-port/build/wasm/sim-configs-inventory/python-remap-native-runtime-state-plan.tsv
 wasm-port/build/wasm/sim-configs-inventory/python-remap-native-runtime-fixture-plan.tsv
 wasm-port/build/wasm/sim-configs-inventory/python-remap-family-summary.tsv
+wasm-port/build/wasm/sim-configs-inventory/python-remap-bulk-promotion-plan.tsv
+wasm-port/build/wasm/sim-configs-inventory/python-remap-row-runtime-proof.tsv
 wasm-port/build/wasm/sim-configs-inventory/boundary-phase-completion-summary.tsv
 wasm-port/build/wasm/sim-configs-inventory/native-proof-alignment-summary.tsv
 wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-native-alignment-summary.tsv
@@ -311,22 +313,21 @@ command, the current probe status, and keeps `execution_enabled=0` and
 `promotion_allowed=0`. It does not run probes or relax promotion locks.
 `runtime-boundary-host-requirement-summary.tsv` normalizes those preflight
 requirements into one row per host command or source/module prerequisite, so
-missing `halcmd`, `halrun`, `linuxcnc`, and `milltask` can be audited by the
-blocked families they affect. `runtime-boundary-host-unblock-plan.tsv`
-filters that table to unavailable requirements and records the affected
-opt-in commands and remaining missing requirements; it is a planning artifact
-only.
+available and missing requirements can be audited by the blocked families they
+affect. `runtime-boundary-host-unblock-plan.tsv` filters that table to
+unavailable requirements and records the affected opt-in commands and
+remaining missing requirements; it is a planning artifact only.
 `runtime-boundary-family-host-readiness.tsv` reduces the same host evidence to
 one row per blocked runtime family, and
 `runtime-boundary-host-readiness-rollup.tsv` gives the aggregate decision. On
-this host the rollup remains `host_blocked_for_all_opt_in_native_probes` with
-zero ready opt-in commands. These rows are non-executing and non-promoting.
+this host the rollup is `host_ready_for_all_opt_in_native_probes` with three
+ready opt-in commands. These rows are non-executing and non-promoting.
 `runtime-boundary-opt-in-probe-dispatch-plan.tsv` turns each family readiness
 row into a per-probe dispatch action. `runtime-boundary-opt-in-probe-dispatch-rollup.tsv`
-then gives the aggregate dispatch switch; currently every blocked runtime
-probe is skipped for missing host requirements. Dispatch permission only means
-the guarded native probe may be manually run on a ready host, not that the row
-is promoted.
+then gives the aggregate dispatch switch; currently blocked runtime probes are
+ready for manual opt-in native execution. Dispatch permission only means the
+guarded native probe may be manually run on a ready host, not that the row is
+promoted.
 `runtime-boundary-opt-in-probe-skip-evidence-contract.tsv` records why each
 non-dispatched probe is skipped and whether native pass evidence is required
 yet. `runtime-boundary-opt-in-probe-skip-evidence-rollup.tsv` gives the
@@ -403,10 +404,10 @@ coverage: every TSV emitted under
 `full-process-boundary-design.md`. New gate artifacts must therefore be
 documented before the inventory can pass.
 The Node coverage gate also requires the generated WASM inventory artifact list
-to remain the exact duplicate-free 55-entry baseline and the native generated
+to remain the exact duplicate-free 57-entry baseline and the native generated
 TSV token list to remain the exact duplicate-free 8-token baseline. It also
 requires the corresponding `boundary-phase-completion-summary.tsv`
-documentation-coverage counts to remain `55` and `8`, respectively. It also
+documentation-coverage counts to remain `57` and `8`, respectively. It also
 checks that the browser smoke source lists the same generated WASM and native
 artifact tokens and preserves the same fixed-count, duplicate-free,
 fetchability/header, documentation-missing, and completion count-parity guards
@@ -530,6 +531,18 @@ Python runtime lifecycle fixture, `axis/remap/stop-lookahead/nc_files`, because
 it exercises Python runtime phases and configured modules without Python
 callable or NGC-only subpath complexity. It is still a fixture plan only:
 `proof_status=pending`, `execution_enabled=0`, and `promotion_allowed=0`.
+`python-remap-bulk-promotion-plan.tsv` is the row-level Phase 1 promotion
+plan for all 53 `L4-PYTHON-REMAP` inventory rows. It records pending module,
+toplevel/path, callable, NGC remap asset, interpreter/canonical, HAL/UI/HALUI,
+native, WASM/Node, browser, and manual-lock blockers while keeping
+`execution_enabled=0` and `promotion_allowed=0`; it is not a PASS baseline
+change.
+`python-remap-row-runtime-proof.tsv` is the Phase 2 row-runtime proof table.
+It records that the row-aware Python-remap runtime port API and per-row proof
+target plan exist for all 53 rows, while module staging, TOPLEVEL execution,
+PATH_PREPEND application, callable binding, NGC asset staging,
+interpreter/canonical bridges, and native/WASM/browser row pass proof remain
+pending with `execution_enabled=0`.
 When explicitly enabled with `ENABLE_PYTHON_REMAP_RUNTIME_PROBE=1`,
 `probe_python_remap_runtime.sh` follows the fixture `demo.ini` Python path and
 toplevel declarations, imports the vendored modules, verifies `queuebuster`