Add blocked runtime gate review coverage

This commit is contained in:
2026-06-12 22:59:57 +08:00
parent 949d5d2756
commit dcab5eaf32
9 changed files with 12494 additions and 37 deletions

348
text4.txt
View File

@@ -621,6 +621,354 @@ Batch 15: blocked runtime host preflight
- Node inventory, browser smoke, and the boundary phase completion summary now
require this host-preflight artifact.
Batch 16: blocked runtime host requirement summary
- Complete as a generated normalized host requirement summary, still blocked
for execution and promotion on this host.
- Generated artifact:
```text
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-requirement-summary.tsv
```
- The artifact expands the host preflight `runtime_requirements` vectors into
one row per required host command/source/module, with:
- requirement name;
- requirement kind (`host_command` or `source_or_module`);
- current availability;
- blocked runtime families that require it;
- blocked runtime families for which it is missing;
- opt-in probe environment variables affected by it;
- whether the missing requirement currently blocks runtime execution.
- Current missing host commands are normalized as:
```text
halcmd available=0 required_by=L4-TOOL-DB,L4-USER-M-PROCESS
halrun available=0 required_by=L4-USER-M-PROCESS
linuxcnc available=0 required_by=L4-PYTHON-REMAP,L4-TOOL-DB,L4-USER-M-PROCESS
milltask available=0 required_by=L4-TOOL-DB
```
- Current available prerequisites remain recorded but non-promoting, including
`python3`, `tclsh`, `axis/db_demo/db_nonran.py`, `linuxcnc.so`,
`tooldb.py`, `interp_python.cc`, `python_plugin.cc`, and the selected
stop-lookahead Python modules.
- This summary does not run probes and does not relax promotion locks. It only
makes the host gap list machine-readable by requirement and affected blocked
family.
- Node inventory, browser smoke, and the boundary phase completion summary now
require this host requirement summary.
Batch 17: blocked runtime host unblock plan
- Complete as a generated host unblock plan, still blocked for execution and
promotion on this host.
- Generated artifact:
```text
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-unblock-plan.tsv
```
- The artifact filters the host requirement summary to only requirements that
are both unavailable and currently block runtime probes. Each row records:
- missing host command;
- affected blocked runtime families;
- affected target programs/families;
- affected opt-in native probe environment variables;
- exact affected opt-in native probe commands;
- remaining missing requirements after that one command becomes available;
- non-executing unblock status and next action.
- Current blocking host commands are:
```text
halcmd
halrun
linuxcnc
milltask
```
- Every current row remains a partial unblock because each affected runtime
family still has at least one other missing host requirement after any single
command is provided:
```text
unblocks_when_available=partial_unblock_other_requirements_remain
next_action=provide_missing_host_requirement
execution_enabled=0
promotion_allowed=0
```
- This plan does not install host commands, run probes, or relax promotion
locks. It only makes the next host-runtime unblock actions and affected
opt-in probes machine-readable.
- Node inventory, browser smoke, and the boundary phase completion summary now
require this host unblock plan.
Batch 18: blocked runtime family host readiness
- Complete as a generated per-family host readiness summary, still blocked for
execution and promotion on this host.
- Generated artifact:
```text
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-family-host-readiness.tsv
```
- The artifact records one row per blocked runtime family with:
- boundary class/kind/target;
- required LinuxCNC runtime family;
- missing host requirement count and list;
- currently available prerequisite count and list;
- opt-in native probe environment variable;
- exact opt-in native probe command;
- current probe and preflight status;
- per-family host status.
- Current rows remain:
```text
L4-USER-M-PROCESS missing=halrun,halcmd,linuxcnc
L4-TOOL-DB missing=linuxcnc,milltask,halcmd
L4-PYTHON-REMAP missing=linuxcnc
```
- Current per-family status remains:
```text
preflight_status=blocked_missing_host_runtime
family_host_status=blocked_missing_host_requirements
execution_enabled=0
promotion_allowed=0
```
- This summary does not run probes and does not relax promotion locks. It gives
each blocked family a single host-readiness row to check before running the
already declared opt-in native probe command.
- Node inventory, browser smoke, and the boundary phase completion summary now
require this family host readiness summary.
Batch 19: blocked runtime host readiness rollup
- Complete as a generated aggregate host readiness rollup, still blocked for
execution and promotion on this host.
- Generated artifact:
```text
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-readiness-rollup.tsv
```
- The artifact reduces the per-family host readiness rows to one overall
decision for blocked runtime native probes:
- total blocked runtime family count;
- host-ready family count;
- host-blocked family count;
- blocked family list;
- unique missing host requirement list;
- ready opt-in command count/list;
- blocked opt-in command list;
- aggregate host readiness status.
- Current aggregate state remains:
```text
family_count=3
host_ready_family_count=0
host_blocked_family_count=3
missing_host_requirements=halcmd,halrun,linuxcnc,milltask
ready_opt_in_command_count=0
ready_opt_in_commands=-
host_readiness_status=host_blocked_for_all_opt_in_native_probes
execution_enabled=0
promotion_allowed=0
```
- The rollup does not run probes and does not relax promotion locks. It gives
the browser, Node inventory, and future automation one single non-promoting
answer: this host is not ready to run any blocked runtime opt-in native
probe.
- Node inventory, browser smoke, and the boundary phase completion summary now
require this host readiness rollup.
Batch 20: blocked runtime opt-in probe dispatch plan
- Complete as a generated per-probe host dispatch plan, still blocked for
execution and promotion on this host.
- Generated artifact:
```text
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-dispatch-plan.tsv
```
- The artifact turns the family host-readiness rows and aggregate host
readiness rollup into one row per blocked runtime opt-in native probe, with:
- boundary class/kind/target;
- opt-in environment variable;
- exact opt-in native probe command;
- per-family host status;
- missing host requirements;
- aggregate host readiness status;
- dispatch action and dispatch permission;
- next action.
- Current dispatch rows remain:
```text
L4-USER-M-PROCESS host_action=skip_missing_host_requirements missing=halrun,halcmd,linuxcnc
L4-TOOL-DB host_action=skip_missing_host_requirements missing=linuxcnc,milltask,halcmd
L4-PYTHON-REMAP host_action=skip_missing_host_requirements missing=linuxcnc
```
- Current dispatch state remains:
```text
host_readiness_status=host_blocked_for_all_opt_in_native_probes
dispatch_allowed=0
execution_enabled=0
promotion_allowed=0
```
- This dispatch plan does not run probes and does not relax promotion locks. It
gives future automation a per-command action: skip each blocked runtime
native probe until the named host requirements are present, then require the
existing manual opt-in command before any promotion gates can move.
- Node inventory, browser smoke, and the boundary phase completion summary now
require this opt-in probe dispatch plan.
Batch 21: blocked runtime opt-in probe dispatch rollup
- Complete as a generated aggregate dispatch rollup, still blocked for
execution and promotion on this host.
- Generated artifact:
```text
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-dispatch-rollup.tsv
```
- The artifact reduces the per-probe dispatch plan rows to one overall
dispatch switch for blocked runtime native probes:
- total opt-in probe count;
- dispatch-allowed probe count;
- dispatch-blocked probe count;
- blocked family list;
- dispatch action set;
- dispatch-allowed command list;
- dispatch-blocked command list;
- unique missing host requirement list;
- aggregate dispatch status.
- Current aggregate dispatch state remains:
```text
probe_count=3
dispatch_allowed_count=0
dispatch_blocked_count=3
dispatch_actions=skip_missing_host_requirements
dispatch_allowed_commands=-
missing_host_requirements=halcmd,halrun,linuxcnc,milltask
dispatch_status=dispatch_blocked_for_all_opt_in_native_probes
execution_enabled=0
promotion_allowed=0
```
- The rollup does not run probes and does not relax promotion locks. It gives
browser smoke, Node inventory, and future automation a single non-promoting
dispatch answer: no blocked runtime opt-in native probe may run on this host.
- Node inventory, browser smoke, and the boundary phase completion summary now
require this opt-in probe dispatch rollup.
Batch 22: blocked runtime opt-in probe skip evidence contract
- Complete as a generated per-probe skip/evidence contract, still blocked for
execution and promotion on this host.
- Generated artifact:
```text
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-skip-evidence-contract.tsv
```
- The artifact joins the opt-in probe dispatch plan with the native pass
evidence contract so each currently skipped probe records:
- boundary class/kind/target;
- runtime probe id;
- opt-in environment variable;
- exact opt-in native probe command;
- host dispatch action;
- skip reason;
- missing host requirements;
- current probe status;
- whether native pass evidence is required now;
- observed native evidence readiness;
- skip/evidence status.
- Current skip/evidence rows remain:
```text
L4-USER-M-PROCESS skip_reason=missing_host_requirements missing=halrun,halcmd,linuxcnc
L4-TOOL-DB skip_reason=missing_host_requirements missing=linuxcnc,milltask,halcmd
L4-PYTHON-REMAP skip_reason=missing_host_requirements missing=linuxcnc
```
- Current evidence state remains:
```text
current_probe_status=skipped_missing_host_runtime
evidence_required_now=0
observed_evidence_ready=0
native_evidence_status=pending_until_native_pass
skip_evidence_status=skip_valid_until_host_requirements_available
execution_enabled=0
promotion_allowed=0
```
- This contract does not run probes and does not relax promotion locks. It
makes the non-executed state explicit: skipped opt-in native probes do not
satisfy native pass evidence until host requirements are present and the
existing manual opt-in probe command passes.
- Node inventory, browser smoke, and the boundary phase completion summary now
require this opt-in probe skip evidence contract.
Batch 23: blocked runtime opt-in probe skip evidence rollup
- Complete as a generated aggregate skip/evidence rollup, still blocked for
execution and promotion on this host.
- Generated artifact:
```text
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-skip-evidence-rollup.tsv
```
- The artifact reduces the per-probe skip/evidence contract rows to one
overall native evidence acceptance state for blocked runtime opt-in probes:
- total opt-in probe count;
- skipped probe count;
- current evidence-required count;
- observed evidence-ready count;
- skipped family list;
- skip reason list;
- unique missing host requirement list;
- current probe status list;
- native evidence status list;
- skip/evidence status list;
- aggregate evidence rollup status.
- Current aggregate skip/evidence state remains:
```text
probe_count=3
skip_count=3
evidence_required_now_count=0
observed_evidence_ready_count=0
skip_reasons=missing_host_requirements
missing_host_requirements=halcmd,halrun,linuxcnc,milltask
current_probe_statuses=skipped_missing_host_runtime
native_evidence_statuses=pending_until_native_pass
skip_evidence_statuses=skip_valid_until_host_requirements_available
evidence_rollup_status=no_native_pass_evidence_accepted_while_host_blocked
execution_enabled=0
promotion_allowed=0
```
- The rollup does not run probes and does not relax promotion locks. It gives
browser smoke, Node inventory, and future automation a single non-promoting
evidence answer: no native pass evidence is accepted while every blocked
runtime opt-in probe is skipped for missing host requirements.
- Node inventory, browser smoke, and the boundary phase completion summary now
require this opt-in probe skip evidence rollup.
Current next implementation recommendations
Generated recommendation source: