Add blocked runtime gate review coverage

wasm-port/docs/full-process-boundary-design.md

@@ -487,6 +487,78 @@ this phase. It combines the worklist, native/Node/browser proof gates, and
 runtime alignment summary so every blocked target has `lock_active=1` until a
 LinuxCNC-owned runtime boundary replaces the pending gates.
 
+## Host Preflight Runbook
+
+The blocked runtime probes are manual opt-in probes. They must not be run just
+because the probe script exists. A future host must first pass the generated
+preflight and dispatch checks for the specific blocked family.
+
+Before attempting any opt-in probe, inspect:
+
+```bash
+wasm-port/tests/wasm/node/verify_sim_configs_inventory_wasm.sh
+cat wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-preflight.tsv
+cat wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-family-host-readiness.tsv
+cat wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-readiness-rollup.tsv
+cat wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-dispatch-plan.tsv
+cat wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-dispatch-rollup.tsv
+cat wasm-port/build/wasm/sim-configs-inventory/native-runtime-probe-execution-plan.tsv
+cat wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-native-evidence-acceptance-gate.tsv
+cat wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-promotion-blockers.tsv
+```
+
+The current host is not ready for any blocked runtime opt-in probe. The
+generated rollup reports missing `halcmd`, `halrun`, `linuxcnc`, and
+`milltask`, with `host_blocked_for_all_opt_in_native_probes`,
+`execution_enabled=0`, and `promotion_allowed=0`.
+
+The opt-in commands remain forbidden while their dispatch rows have
+`dispatch_allowed=0`:
+
+```bash
+ENABLE_MILLTURN_USER_M_RUNTIME_PROBE=1 bash wasm-port/tests/native/probe_millturn_user_m_runtime.sh
+ENABLE_TOOL_DB_RUNTIME_PROBE=1 bash wasm-port/tests/native/probe_tool_db_runtime.sh
+ENABLE_PYTHON_REMAP_RUNTIME_PROBE=1 bash wasm-port/tests/native/probe_python_remap_runtime.sh
+```
+
+A probe may be attempted only when all of these are true for that family:
+
+- the corresponding runtime probe gate reports `runtime_ready=1`;
+- `runtime-boundary-family-host-readiness.tsv` reports the family ready;
+- `runtime-boundary-opt-in-probe-dispatch-plan.tsv` reports
+  `dispatch_allowed=1`;
+- `runtime-boundary-opt-in-probe-dispatch-rollup.tsv` does not block that
+  command;
+- the probe is run manually with its explicit `ENABLE_*_RUNTIME_PROBE=1`
+  environment variable.
+
+Passing a native opt-in probe is not promotion. After a native pass, the row
+must still satisfy:
+
+- `native-runtime-probe-pass-evidence-contract.tsv`;
+- `runtime-probe-gate-alignment.tsv`;
+- `runtime-boundary-promotion-readiness.tsv`;
+- `runtime-boundary-post-native-pass-gates.tsv`;
+- `runtime-boundary-native-evidence-acceptance-gate.tsv`;
+- `runtime-boundary-promotion-blockers.tsv`;
+- Node inventory proof;
+- browser smoke proof where applicable;
+- manual update of `blocked-runtime-promotion-lock.tsv`;
+- documentation updates in this file, `compatibility-validation.md`, and
+  `sim-configs-coverage-matrix.md`.
+
+While the skip/evidence artifacts report
+`skip_valid_until_host_requirements_available` and
+`no_native_pass_evidence_accepted_while_host_blocked`, skipped probes provide
+no native pass evidence. They only prove that the current host is correctly
+blocked.
+
+`native-runtime-probe-execution-plan.tsv` and
+`next-boundary-recommendations.tsv` are planning handoffs, not permission to
+run probes. They name the next recommended boundary work and exact opt-in
+commands, but the host preflight and dispatch rows still decide whether those
+commands are allowed on the current machine.
+
 The first two priorities are the current designed-but-disabled full-process
 blocks: