先提交到云仓库

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

wasm-port/docs/host-runtime-boundary-handoff.md

@@ -12,14 +12,19 @@ Detailed references:
 - `docs/sim-configs-coverage-handoff.md`
 - `tests/wasm/node/verify_sim_configs_inventory_wasm.mjs`
 
-## Current blocked runtime families
+## Current runtime boundary families
 
-The current hard blocked families are:
+The current runtime-boundary proof families are:
 
 - `L4-USER-M-PROCESS`
 - `L4-TOOL-DB`
 - `L4-PYTHON-REMAP`
 
+The current Node inventory skip/block summary still has `L4-PYTHON-REMAP=53`
+and `L4-USER-M-PROCESS=1`. `L4-TOOL-DB` is no longer a skipped inventory row,
+but it remains represented in the runtime-boundary proof ledger with
+`promotion_allowed=0`.
+
 Current host readiness is summarized by:
 
 - `build/wasm/sim-configs-inventory/runtime-boundary-host-readiness-rollup.tsv`
@@ -32,13 +37,13 @@ Current host readiness is summarized by:
 Current rollup state:
 
 ```text
-host_readiness_status=host_blocked_for_all_opt_in_native_probes
+host_readiness_status=host_ready_for_all_opt_in_native_probes
 family_count=3
-host_ready_family_count=0
-host_blocked_family_count=3
-blocked_families=L4-PYTHON-REMAP,L4-TOOL-DB,L4-USER-M-PROCESS
-missing_host_requirements=halcmd,halrun,linuxcnc,milltask
-ready_opt_in_command_count=0
+host_ready_family_count=3
+host_blocked_family_count=0
+blocked_families=-
+missing_host_requirements=-
+ready_opt_in_command_count=3
 execution_enabled=0
 promotion_allowed=0
 ```
@@ -48,10 +53,9 @@ promotion_allowed=0
 Each blocked family currently has `promotion_ready=0`, `execution_enabled=0`,
 and `promotion_allowed=0`.
 
-The current blocker keys are:
+For `L4-USER-M-PROCESS` and `L4-TOOL-DB`, the current blocker keys are:
 
 ```text
-host_runtime_requirements_missing
 native_runtime_probe_not_passed
 native_pass_evidence_not_ready
 node_inventory_gate_not_complete
@@ -60,25 +64,46 @@ promotion_lock_active
 manual_lock_update_required
 ```
 
-The next unblock action is to provide the missing host runtime requirements for
-the relevant family. Providing host commands is not enough to promote a row; it
-only allows the next opt-in probe gate to be considered.
+For the first Python remap fixture, `axis/remap/stop-lookahead/nc_files`, the
+native lifecycle evidence has been accepted and the Node/browser lifecycle
+gates are complete:
+
+```text
+current_probe_status=runtime_lifecycle_probe_passed
+native_evidence_status=native_pass_evidence_observed
+node_inventory_gate_complete=1
+browser_smoke_gate_complete=1
+node_gate_status=node_inventory_promotion_gate_complete
+browser_gate_status=browser_smoke_promotion_gate_complete
+blocking_reason=promotion_lock_active_manual_review_required
+next_unblock_action=manual_lock_review_required
+```
+
+The Python row still has `promotion_ready=0`, `execution_enabled=0`, and
+`promotion_allowed=0`; the remaining blockers are `promotion_lock_active` and
+`manual_lock_update_required`. This proof-chain state does not promote any of
+the 53 `L4-PYTHON-REMAP` rows.
+
+For rows that still lack native evidence, the next unblock action is to provide
+the missing host runtime requirements for the relevant family. Providing host
+commands is not enough to promote a row; it only allows the next opt-in probe
+gate to be considered.
 
 ## Opt-in probe dispatch
 
 The current dispatch rollup is:
 
 ```text
-dispatch_status=dispatch_blocked_for_all_opt_in_native_probes
+dispatch_status=dispatch_allowed_for_all_opt_in_native_probes
 probe_count=3
-dispatch_allowed_count=0
-dispatch_blocked_count=3
-dispatch_actions=skip_missing_host_requirements
+dispatch_allowed_count=3
+dispatch_blocked_count=0
+dispatch_actions=ready_for_manual_opt_in_native_probe
 execution_enabled=0
 promotion_allowed=0
 ```
 
-These commands remain blocked on this host:
+These commands are opt-in only and must never run implicitly:
 
 ```bash
 ENABLE_MILLTURN_USER_M_RUNTIME_PROBE=1 bash wasm-port/tests/native/probe_millturn_user_m_runtime.sh
@@ -86,23 +111,37 @@ ENABLE_TOOL_DB_RUNTIME_PROBE=1 bash wasm-port/tests/native/probe_tool_db_runtime
 ENABLE_PYTHON_REMAP_RUNTIME_PROBE=1 bash wasm-port/tests/native/probe_python_remap_runtime.sh
 ```
 
-Do not run them unless the generated preflight, family readiness, dispatch
-plan, and dispatch rollup all permit the specific family.
+Only run them deliberately when updating native proof evidence. A passing probe
+does not enable execution or promotion by itself.
 
 ## Native evidence acceptance
 
+For rows still blocked before native evidence,
 `runtime-boundary-native-evidence-acceptance-gate.tsv` currently records:
 
-- `current_probe_status=skipped_missing_host_runtime`
+- `current_probe_status=ready_disabled_by_default`
 - `native_evidence_status=pending_until_native_pass`
-- `skip_evidence_status=skip_valid_until_host_requirements_available`
+- `skip_evidence_status=skip_contract_not_applicable_dispatch_allowed`
 - `node_gate_status=blocked_until_native_pass_evidence`
 - `browser_gate_status=blocked_until_node_gate_complete`
-- `native_evidence_gate=blocked_until_host_requirements_available`
+- `native_evidence_gate=blocked_until_native_pass_evidence`
 - `evidence_acceptance_allowed=0`
 
-A skipped opt-in probe is not a native pass. It only proves that this host is
-correctly blocked until the required LinuxCNC runtime commands are available.
+A disabled opt-in probe is not a native pass. It only proves that this host is
+not executing the family-specific runtime probe by default.
+
+For `L4-PYTHON-REMAP`, the same artifact records accepted native lifecycle
+evidence for the stop-lookahead fixture:
+
+- `current_probe_status=runtime_lifecycle_probe_passed`
+- `native_evidence_status=native_pass_evidence_observed`
+- `skip_evidence_status=native_pass_evidence_observed_skip_contract_closed`
+- `node_gate_status=node_inventory_promotion_gate_complete`
+- `browser_gate_status=browser_smoke_promotion_gate_complete`
+- `native_evidence_gate=native_pass_evidence_accepted`
+- `evidence_acceptance_allowed=1`
+
+This is evidence acceptance only. It does not change `promotion_allowed=0`.
 
 ## Release gate
 
@@ -143,4 +182,5 @@ No blocked family may be promoted until all of these are true:
    deliberately.
 
 Until then, `L4-USER-M-PROCESS`, `L4-TOOL-DB`, and `L4-PYTHON-REMAP` remain
-blocked, inventory-only runtime families.
+locked in the runtime-boundary proof ledger with `promotion_allowed=0`; only
+the inventory rows explicitly eligible for Node/WASM execution may run.