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

View File

@@ -36,6 +36,8 @@ Current baseline:
`wasm-port/build/wasm/sim-configs-inventory/tool-db-process-boundary-summary.tsv`
- Node tool DB process transaction contract artifact:
`wasm-port/build/wasm/sim-configs-inventory/tool-db-process-transaction-plan.tsv`
- Node tool DB native runtime probe gate artifact:
`wasm-port/build/wasm/sim-configs-inventory/tool-db-process-native-runtime-probe-gate.tsv`
- Node Python-remap boundary inventory artifact:
`wasm-port/build/wasm/sim-configs-inventory/python-remap-boundary-summary.tsv`
- Node Python-remap family inventory artifact:
@@ -44,6 +46,8 @@ Current baseline:
`wasm-port/build/wasm/sim-configs-inventory/python-remap-runtime-contract.tsv`
- Node Python-remap native runtime readiness artifact:
`wasm-port/build/wasm/sim-configs-inventory/python-remap-native-runtime-readiness.tsv`
- Node Python-remap native runtime probe gate artifact:
`wasm-port/build/wasm/sim-configs-inventory/python-remap-native-runtime-probe-gate.tsv`
- Node Python-remap native runtime state-plan artifact:
`wasm-port/build/wasm/sim-configs-inventory/python-remap-native-runtime-state-plan.tsv`
- Node Python-remap native runtime fixture-plan artifact:
@@ -52,8 +56,34 @@ Current baseline:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-contract-summary.tsv`
- Node boundary-phase completion artifact:
`wasm-port/build/wasm/sim-configs-inventory/boundary-phase-completion-summary.tsv`
- Node native runtime probe execution-plan artifact:
`wasm-port/build/wasm/sim-configs-inventory/native-runtime-probe-execution-plan.tsv`
- Node next-boundary worklist artifact:
`wasm-port/build/wasm/sim-configs-inventory/next-boundary-worklist.tsv`
- Node next-boundary recommendation artifact:
`wasm-port/build/wasm/sim-configs-inventory/next-boundary-recommendations.tsv`
- Node native evidence acceptance gate artifact:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-native-evidence-acceptance-gate.tsv`
- Node promotion blocker summary artifact:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-promotion-blockers.tsv`
- Node blocked-runtime host preflight artifact:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-preflight.tsv`
- Node blocked-runtime host requirement summary artifact:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-requirement-summary.tsv`
- Node blocked-runtime host unblock plan artifact:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-unblock-plan.tsv`
- Node blocked-runtime family host readiness artifact:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-family-host-readiness.tsv`
- Node blocked-runtime aggregate host readiness artifact:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-readiness-rollup.tsv`
- Node blocked-runtime opt-in probe dispatch plan artifact:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-dispatch-plan.tsv`
- Node blocked-runtime opt-in probe dispatch rollup artifact:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-dispatch-rollup.tsv`
- Node blocked-runtime opt-in probe skip/evidence contract artifact:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-skip-evidence-contract.tsv`
- Node blocked-runtime opt-in probe skip/evidence rollup artifact:
`wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-skip-evidence-rollup.tsv`
- Current Node inventory: `executed 28`, `passed 28`, `skipped 131`,
`unexpected_fail 0`
- Current Node skip/block counts: `ASSET-ONLY 65`, `L4-PYTHON-REMAP 53`,
@@ -160,6 +190,10 @@ Legend:
`ENABLE_TOOL_DB_RUNTIME_PROBE=1` proves the LinuxCNC-owned `DB_PROGRAM`
`v2.1`/`g`/`p`/`l`/`u` protocol, nonrandom state updates, and flat-file
persistence.
- `tool-db-process-native-runtime-probe-gate.tsv`: the execution gate for the
guarded native DB process protocol probe. It combines source proof and host
readiness, records missing runtime requirements, and keeps the DB boundary
non-executing and non-promotable until the manual opt-in probe is allowed.
- `python-remap-boundary-summary.tsv`: one row for each `L4-PYTHON-REMAP`
path. It records Python modules, remap/prolog/epilog functions, NGC-only
subpaths, HAL/UI/HALUI assumptions, the LinuxCNC Python owner set, LinuxCNC
@@ -179,6 +213,11 @@ Legend:
`linuxcnc`, LinuxCNC's Python interpreter/plugin owner source files, and the
configured Python modules for each blocked family, while keeping every row
pending, non-executing, and non-promotable.
- `python-remap-native-runtime-probe-gate.tsv`: the execution gate for the
selected Python remap lifecycle fixture. It combines source proof and host
readiness, records missing runtime requirements, and keeps Python remap
execution blocked until the LinuxCNC host runtime and dispatch gate allow a
manual opt-in probe.
- `python-remap-native-runtime-state-plan.tsv`: one row per blocked
Python-remap family. It records the runtime phases, modules, callables,
NGC-only subpaths, process assumptions, readiness counts, source-alignment
@@ -208,7 +247,68 @@ Legend:
LinuxCNC-owned runtime proof fields for user-M, tool DB, and Python runtime
blockers. When native source proof is available, it also requires that proof
to be consumed by generated worklist/native proof-gate rows without enabling
execution or promotion.
execution or promotion. It also records WASM sim-config inventory artifact
documentation coverage and native generated TSV documentation coverage as
explicit completion criteria. It also records the blocked runtime
worklist/recommendation consistency guard, the blocked runtime promotion gate
consistency guard, the blocked runtime host requirement consistency guard,
the blocked runtime host/dispatch/skip-evidence rollup consistency guard, the
blocked runtime opt-in cross-artifact consistency guard, the native source
proof/runtime probe consistency guard, and the runtime family
contract/alignment consistency guard as explicit completion criteria. The
family contract/alignment check keeps the user-M, tool DB, and Python
contract/readiness/probe artifacts aligned with the aggregate runtime
contract and native-alignment summaries without enabling execution or
promotion.
Browser smoke mirrors this completion-summary criterion list and fails on
criterion drift, so browser-side validation sees the same boundary-phase
gate set as the Node inventory without executing blocked runtime probes.
It also checks selected completion-summary counts against the blocked-runtime
and family-specific artifact rows already loaded by browser smoke, so the
machine-readable completion summary cannot claim a different row count from
the visible gate artifacts.
The Node coverage gate also checks that browser smoke keeps the same
generated WASM/native artifact tokens, fixed-count guards, duplicate-free
guards, fetchability/header guards, documentation-missing guards, completion
count-parity guards, review-document fetches, and native skipped-artifact
empty allowance as the Node inventory gate.
It also checks that `runtime-boundary-contract-summary.tsv` and
`runtime-boundary-native-alignment-summary.tsv` agree on boundary kind,
runtime alignment artifact, alignment row count, and disabled execution and
promotion state.
It also cross-checks user-M, tool DB, and Python family-specific
contract/readiness/probe artifacts against `runtime-boundary-contract-summary.tsv`
so browser validation sees the same runtime-family contract alignment as
Node inventory without executing blocked runtime processes.
Browser smoke also cross-checks `native-proof-alignment-summary.tsv`,
`native-runtime-probe-summary.tsv`, and `runtime-probe-gate-alignment.tsv`
for source-proof readiness, runtime readiness, required native proof, target,
and disabled execution/promotion parity.
It also cross-checks the native runtime probe execution plan, pass evidence
contract, host preflight, dispatch plan, and skip-evidence contract so the
browser smoke sees the same host-blocked opt-in command, missing
requirements, evidence status, and disabled execution/promotion state as the
Node inventory.
It also cross-checks the host-readiness, dispatch, and skip-evidence rollups
for counts, blocked families, missing requirements, blocked commands,
host/dispatch/evidence status, and disabled execution/promotion parity.
It also cross-checks the promotion lock, promotion readiness, promotion
blockers, post-native-pass gates, native evidence acceptance gate, and pass
evidence contract so browser validation sees the same locked promotion state
as Node inventory.
It also cross-checks recommendations, execution plans, host preflight,
family readiness, dispatch plans, skip-evidence contracts, and evidence
acceptance gates so browser validation sees the same opt-in command, proof,
missing requirement, and disabled execution/promotion state as Node inventory.
It also checks recommendation artifact row counts against the generated
user-M probe-gate, tool DB probe-gate, and Python runtime-contract source
rows, so priority handoffs cannot drift from the visible source artifacts.
It also checks each recommendation primary artifact and source artifact list
against the generated WASM inventory artifact set, including duplicate
detection, primary-artifact traceability, and exact per-family source
artifact sets. The Node coverage gate also verifies that browser smoke passes
the `wasmArtifactNames` returned by artifact documentation coverage into this
recommendation source-artifact coverage check.
- `native-proof-alignment-summary.tsv`: one row per native source proof class.
It aligns the native source proof summary with generated worklist/native
proof-gate consumers for user-M, tool DB, and Python runtime blockers.
@@ -217,6 +317,115 @@ Legend:
LinuxCNC owner set and runtime owner evidence, records native, Node, and
browser proof requirements, and names the next boundary-design action before
any blocked family can be promoted.
- `next-boundary-recommendations.tsv`: the generated priority queue for the
next blocked runtime-boundary work. It currently ranks millturn `M128/M129`
state proof, tool DB protocol proof, and Python remap lifecycle proof, while
preserving active promotion locks and disabled execution. The Node inventory
verifies exact per-family source artifact sets, duplicate-free source lists,
primary-artifact traceability, and generated artifact existence for each
recommendation.
- `native-runtime-probe-execution-plan.tsv`: the guarded opt-in execution
plan for blocked runtime native probes. It records the exact command,
required native proof key, current runtime readiness, expected pass status,
missing requirements, gate alignment, and promotion prerequisites. It is not
a probe runner and does not promote rows.
- `runtime-boundary-native-evidence-acceptance-gate.tsv`: one row per blocked
runtime family deciding whether native pass evidence may be accepted. While
probes are skipped for missing host requirements, evidence acceptance is
blocked and Node/browser gates remain blocked.
- `runtime-boundary-promotion-blockers.tsv`: the expanded blocker summary for
non-ready promotions. Current rows record missing host runtime, native
probe not passed, native evidence not ready, Node/browser gates incomplete,
active promotion lock, and manual lock update required.
- The Node inventory also performs a cross-artifact consistency guard across
the blocked runtime opt-in target set. The guard requires the
recommendations, execution plan, host preflight, family readiness, dispatch
plan, skip/evidence contract, native evidence acceptance gate, promotion
readiness, promotion blockers, and post-native-pass gates to agree on the
target, proof keys, opt-in command, missing host requirements, active
promotion lock, and disabled execution/promotion fields.
- The Node inventory also checks documentation coverage for generated
sim-config inventory TSVs. Every artifact emitted under
`build/wasm/sim-configs-inventory/` must be referenced by the current
compatibility, matrix, or full-process boundary docs, so generated gate
artifacts cannot silently appear without review text. The generated WASM
inventory artifact list must remain the exact duplicate-free 54-entry
baseline, and every token plus the fixed-count, duplicate-free, and
fetchability guards must also be listed by browser smoke.
- The same inventory check covers native generated TSV artifacts under
`build/native/` by relative path, including native source-proof,
runtime-probe, `nc_files`, and sim-config baseline artifacts. The native
generated TSV token list must remain the exact duplicate-free 8-token
baseline, and every token plus the fixed-count, duplicate-free, fetchability,
and empty-skipped allowance guards must also be listed by browser smoke.
- Browser smoke mirrors this documentation coverage by fetching the current
compatibility, matrix, and full-process boundary docs and checking the
generated WASM inventory artifact names plus native TSV tokens against the
same completion-summary counts. The Node coverage gate also locks the two
documentation-coverage completion counts to the current `54` WASM inventory
artifacts and `8` native TSV artifacts. It verifies that browser smoke
executes the artifact documentation coverage helper, calls the completion
count-parity helper with the generated completion rows, fetches and joins the
exact compatibility, matrix, and full-process boundary review-document set
used for the missing-reference checks, requires those checks to iterate
`wasmArtifactNames` and `nativeArtifactTokens` against the joined
`documentationText`, fetches generated WASM TSVs by artifact name, fetches
native TSVs by relative artifact token, binds the documentation-coverage
completion counts to the returned `wasmArtifactNames` and
`nativeArtifactTokens` arrays, and keeps completion evidence reviewable when
browser-side count parity is checked. Browser smoke also requires a
non-empty TSV header, duplicate-free expected lists, and fixed artifact/token
counts. This is
documentation/artifact fetchability parity only and does not execute blocked
runtime probes. The native
`build/native/sim-configs/skipped.tsv` artifact may be empty when the native
strict sim-config baseline has no skipped rows.
- The Node inventory also checks native source proof consistency. Native
source proof alignment rows, the native runtime probe summary, and runtime
probe gate alignment must cover the same blocked classes, agree that source
proof is ready, and keep execution and promotion disabled.
- `runtime-boundary-host-preflight.tsv`: the host-facing preflight for the
guarded blocked-runtime native probes. It records each blocked family,
required host/runtime commands, opt-in environment variable, exact native
probe command, current probe status, and keeps execution and promotion
disabled. It does not run the probes.
- `runtime-boundary-host-requirement-summary.tsv`: a normalized requirement
table for the blocked runtime probes. It records each required host command
or source/module, its availability, affected blocked families, affected
opt-in probe environment variables, and whether the missing requirement
currently blocks execution.
- `runtime-boundary-host-unblock-plan.tsv`: the filtered plan for unavailable
host requirements. It records the affected blocked families, affected
opt-in commands, and remaining missing requirements after each single
requirement is provided. It is advisory only and does not install anything
or allow promotion.
- `runtime-boundary-family-host-readiness.tsv`: one host-readiness row per
blocked runtime family. It records missing requirements, available
prerequisites, the opt-in command, current probe/preflight status, and keeps
`execution_enabled=0` and `promotion_allowed=0`.
- Browser smoke cross-checks the host requirement summary, unblock plan,
family host readiness, and host preflight rows. The check verifies
unavailable requirement ownership, available prerequisite ownership,
affected opt-in environments, and exact probe command traceability while
remaining non-executing and non-promoting.
- `runtime-boundary-host-readiness-rollup.tsv`: the aggregate host-readiness
decision for all blocked runtime families. On this host it records zero
ready families, missing `halcmd`, `halrun`, `linuxcnc`, and `milltask`, and
`host_blocked_for_all_opt_in_native_probes`.
- `runtime-boundary-opt-in-probe-dispatch-plan.tsv`: one dispatch row per
guarded native runtime probe. It turns host readiness into a dispatch action
and remains non-promoting; a dispatchable row only means the manual opt-in
native probe may be attempted on a ready host.
- `runtime-boundary-opt-in-probe-dispatch-rollup.tsv`: the aggregate dispatch
switch for blocked runtime probes. Current rows are blocked for missing host
requirements, so no opt-in native probe is dispatchable on this host.
- `runtime-boundary-opt-in-probe-skip-evidence-contract.tsv`: the per-probe
skip/evidence contract. It records the skip reason, missing host
requirements, current probe status, whether native pass evidence is required
now, and keeps every skipped probe non-executing and non-promoting.
- `runtime-boundary-opt-in-probe-skip-evidence-rollup.tsv`: the aggregate
evidence decision for skipped opt-in probes. While all probes are skipped for
missing host requirements, no native pass evidence is accepted.
## Summary