wangdequan/cnc_wams
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add blocked runtime gate review coverage

Browse Source
This commit is contained in:
wangdequan
2026-06-12 22:59:57 +08:00
parent 949d5d2756
commit dcab5eaf32
9 changed files with 12494 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

209
wasm-port/docs/compatibility-validation.md
View File

@@ -141,14 +141,28 @@ The native harness also emits machine-readable derived artifacts without
changing the `summary.tsv` schema:
```text
wasm-port/build/native/source-probes.tsv
wasm-port/build/native/native-source-proof-summary.tsv
wasm-port/build/native/native-runtime-probe-summary.tsv
wasm-port/build/native/nc-files/summary.tsv
wasm-port/build/native/sim-configs/summary.tsv
wasm-port/build/native/sim-configs/class-summary.tsv
wasm-port/build/native/sim-configs/path-matrix.tsv
wasm-port/build/native/sim-configs/skipped.tsv
```
`class-summary.tsv` aggregates class/status/expected-failure counts.
`path-matrix.tsv` records each path, class, native status, expected-failure
reason, INI, tool table, runtime family, and blocked kind for CI and Node
inventory reconciliation.
`source-probes.tsv` records the native source-probe entry points used by
`verify_native_probes.sh`. `native-source-proof-summary.tsv` records
LinuxCNC-owned source proof for user-M process, tool DB process, and Python
remap runtime blockers without enabling execution or promotion.
`native-runtime-probe-summary.tsv` records the guarded native opt-in runtime
probe status and missing host requirements. `nc-files/summary.tsv` records the
Layer 1 native `nc_files` baseline, and `sim-configs/skipped.tsv` records the
Layer 2 native sim-config skipped or expected-skip accounting.
The Node inventory layer writes its own machine-readable artifacts:
@@ -163,19 +177,34 @@ wasm-port/build/wasm/sim-configs-inventory/user-m-process-state-targets.tsv
wasm-port/build/wasm/sim-configs-inventory/user-m-process-native-state-alignment.tsv
wasm-port/build/wasm/sim-configs-inventory/tool-db-process-protocol-gates.tsv
wasm-port/build/wasm/sim-configs-inventory/tool-db-process-native-protocol-alignment.tsv
wasm-port/build/wasm/sim-configs-inventory/tool-db-process-native-runtime-probe-gate.tsv
wasm-port/build/wasm/sim-configs-inventory/python-remap-boundary-summary.tsv
wasm-port/build/wasm/sim-configs-inventory/python-remap-runtime-gates.tsv
wasm-port/build/wasm/sim-configs-inventory/python-remap-native-runtime-alignment.tsv
wasm-port/build/wasm/sim-configs-inventory/python-remap-native-runtime-readiness.tsv
wasm-port/build/wasm/sim-configs-inventory/python-remap-native-runtime-probe-gate.tsv
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/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
wasm-port/build/wasm/sim-configs-inventory/native-runtime-probe-execution-plan.tsv
wasm-port/build/wasm/sim-configs-inventory/blocked-runtime-promotion-lock.tsv
wasm-port/build/wasm/sim-configs-inventory/next-boundary-worklist.tsv
wasm-port/build/wasm/sim-configs-inventory/next-boundary-recommendations.tsv
wasm-port/build/wasm/sim-configs-inventory/boundary-proof-gates.tsv
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-native-evidence-acceptance-gate.tsv
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-promotion-blockers.tsv
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-preflight.tsv
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-requirement-summary.tsv
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-unblock-plan.tsv
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-family-host-readiness.tsv
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-host-readiness-rollup.tsv
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-dispatch-plan.tsv
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-dispatch-rollup.tsv
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-skip-evidence-contract.tsv
wasm-port/build/wasm/sim-configs-inventory/runtime-boundary-opt-in-probe-skip-evidence-rollup.tsv
```
The current skip/block summary is `ASSET-ONLY=65`, `L4-PYTHON-REMAP=53`,
@@ -243,6 +272,133 @@ blocked dependency row, records the required native/Node/browser proof, and
keeps `execution_enabled=0` until the corresponding LinuxCNC-owned runtime
boundary exists. The tracked matrix and inventory guard also require those two
rows to remain non-representative in Node/browser until that proof exists.
`runtime-boundary-host-preflight.tsv` is the host-facing preflight for the
blocked runtime probes. It records each blocked family, the required LinuxCNC
runtime commands, the opt-in environment variable, the exact native probe
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.
`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.
`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.
`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
aggregate evidence decision. While probes are skipped for missing host
requirements, no native pass evidence is accepted and every blocked family
remains `execution_enabled=0` and `promotion_allowed=0`.
`native-runtime-probe-execution-plan.tsv` records the exact opt-in command,
required native proof key, current runtime readiness, expected pass status,
missing requirements, and promotion prerequisites for the three guarded native
runtime probes. On this host all rows remain
`plan_status=blocked_missing_host_runtime`.
`runtime-boundary-native-evidence-acceptance-gate.tsv` decides whether native
pass evidence may be accepted for each blocked runtime family. It currently
blocks evidence acceptance until host requirements are available and the
native opt-in probe passes. `runtime-boundary-promotion-blockers.tsv` expands
each non-ready promotion decision into concrete blocker keys such as missing
host runtime, native probe not passed, Node/browser gates incomplete,
promotion lock active, and manual lock update required.
`next-boundary-recommendations.tsv` is the generated priority handoff for the
next runtime boundary work. It ranks millturn user-M, tool DB, and Python
runtime lifecycle work, while keeping `execution_enabled=0` and
`promotion_allowed=0`. The Node inventory verifies the exact per-family
`source_artifacts` set, duplicate-free source lists, and `primary_artifact`
traceability for each recommendation, and requires every referenced artifact
token to exist under the generated sim-config inventory artifact directory.
The Node inventory also runs a cross-artifact guard over the blocked runtime
opt-in target set. It requires recommendations, execution plan, host preflight,
dispatch plan, skip/evidence contract, native evidence acceptance gate,
promotion readiness, promotion blockers, and post-native-pass gates to agree
on the same target, proof keys, opt-in command, missing runtime requirements,
active promotion lock, and non-executing/non-promoting state.
The browser smoke mirrors the promotion and opt-in gate consistency checks by
cross-checking the promotion lock, readiness, blocker, post-native-pass, native
evidence acceptance, pass-evidence, recommendation, host-preflight, family
readiness, dispatch, and skip-evidence artifacts. This browser-side parity is
non-executing and keeps every blocked runtime family locked until native,
Node, browser, and manual promotion gates all agree.
It also cross-checks `runtime-boundary-host-requirement-summary.tsv`,
`runtime-boundary-host-unblock-plan.tsv`,
`runtime-boundary-family-host-readiness.tsv`, and
`runtime-boundary-host-preflight.tsv` so missing and available host
requirements, affected opt-in commands, and family probe commands cannot drift
between the host-readiness artifacts.
It also checks that `boundary-phase-completion-summary.tsv` counts match the
blocked-runtime and family-specific artifact rows the browser has already
loaded, so completion criteria cannot drift from the generated gate artifacts
seen by browser smoke.
It also cross-checks the 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 the
Node inventory, without running any blocked runtime process.
It also checks `next-boundary-recommendations.tsv` row counts against the
generated user-M probe-gate, tool DB probe-gate, and Python runtime-contract
source rows, so recommendation priority handoffs cannot drift from their
machine-readable source artifacts.
It also checks each recommendation's `primary_artifact` and `source_artifacts`
against the browser-visible generated artifact set, including duplicate
detection, primary-artifact traceability, and exact per-family source artifact
sets, while keeping execution and promotion disabled. The Node coverage gate
also confirms the browser recommendation source-artifact check uses the same
`wasmArtifactNames` returned by the artifact documentation coverage helper.
It also fetches the compatibility, matrix, and full-process boundary docs in
browser smoke and checks the documented artifact names/tokens for the generated
WASM inventory TSVs and native TSVs. The same browser check fetches those TSV
artifacts, requires a non-empty TSV header, and verifies the expected
artifact/token lists are duplicate-free with fixed counts, mirroring the Node
documentation coverage gate without executing native runtime probes. The native
`build/native/sim-configs/skipped.tsv` artifact is allowed to be empty when the
native strict sim-config baseline has no skipped rows.
The same Node inventory run also checks generated artifact documentation
coverage: every TSV emitted under
`build/wasm/sim-configs-inventory/` must be named in
`compatibility-validation.md`, `sim-configs-coverage-matrix.md`, or
`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 54-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 `54` 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
before browser-side artifact coverage can pass. It also checks that browser
smoke actually executes the artifact documentation coverage helper, fetches
each generated WASM artifact by artifact name, fetches each native TSV by
relative artifact token, calls the completion count-parity helper with the
generated completion rows, still fetches and joins the exact compatibility,
matrix, and full-process boundary review-document set for that coverage check
before checking for missing artifact references, requires the browser
missing-reference loops to iterate `wasmArtifactNames` and
`nativeArtifactTokens` against that joined `documentationText`, keeps
completion evidence reviewable for browser count parity, binds the
documentation-coverage completion counts to the returned `wasmArtifactNames`
and `nativeArtifactTokens` arrays, and preserves the native skipped-artifact
empty allowance for `build/native/sim-configs/skipped.tsv`.
Native generated TSVs under `build/native/` are checked the same way by their
relative artifact path. This catches native baseline/source-proof/runtime-probe
artifacts that are generated but not described in the compatibility, coverage,
or full-process boundary documentation.
It also checks native source proof consistency: the native source proof
alignment rows, native runtime probe summary, and runtime probe gate alignment
must cover the same blocked classes and agree that source proof is ready while
execution and promotion remain disabled.
`user-m-process-state-targets.tsv` expands the `millturn` M128/M129 process
boundary into per-pin proof targets: two user-M codes, three axes, and four
`ini.[xyz]` HAL pins per axis. Each row records the source Tcl file, remap
@@ -302,6 +458,10 @@ keeping `proof_status=pending`, `execution_enabled=0`, and
vendored `DB_PROGRAM`, drives the LinuxCNC `tooldb.py` `v2.1`/`g`/`p`/`l`/`u`
protocol, verifies nonrandom startup/update/load/unload state and persistence,
and reports `runtime_protocol_probe_passed` without enabling promotion.
`tool-db-process-native-runtime-probe-gate.tsv` combines the DB source proof
and host readiness into the execution gate for that guarded native probe. It
records `runtime_ready`, missing requirements, source proof readiness, and the
non-promoting gate status before any manual opt-in run is allowed.
`python-remap-boundary-summary.tsv` is the machine-readable companion for the
Python remap inventory batch. It has one inventory-only row for each
`L4-PYTHON-REMAP` path, records Python modules, remap/prolog/epilog functions,
@@ -323,6 +483,11 @@ prerequisites for guarded probes by family: `python3`, `linuxcnc`,
LinuxCNC's `interp_python.cc` / `python_plugin.cc` owner source files, and the
configured Python modules. It is a readiness gate only and keeps every row
`proof_status=pending`, `execution_enabled=0`, and `promotion_allowed=0`.
`python-remap-native-runtime-probe-gate.tsv` combines the selected Python
runtime fixture, source proof, and host readiness into the execution gate for
the guarded native lifecycle probe. It remains non-executing and
non-promoting until `linuxcnc` is available and the dispatch gate permits the
manual opt-in probe.
`python-remap-native-runtime-state-plan.tsv` records the next native runtime
probe target set by family: LinuxCNC Python phases, configured modules,
callables, NGC-only subpaths, process assumptions, readiness counts, and
@@ -352,6 +517,50 @@ disabled, and proof that blocked runtime families carry LinuxCNC-owned user-M,
tool DB, and Python runtime evidence fields. It also records native source
proof alignment when the native proof summary is available, plus the aggregate
native stdout alignment summary for user-M, tool DB, and Python runtime gates.
The same completion summary now includes documentation-coverage criteria for
generated WASM sim-config inventory TSV artifacts and native generated TSV
artifacts, so artifact generation and review documentation stay in lockstep.
It also exposes 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 completion criteria, so review
can see those gates without reopening every individual TSV. The family
contract/alignment guard checks that the user-M, tool DB, and Python-specific
contract, readiness, probe-gate, and fixture/state-plan artifacts agree with
`runtime-boundary-contract-summary.tsv` and
`runtime-boundary-native-alignment-summary.tsv` while keeping execution and
promotion disabled.
The browser smoke consumes the same `boundary-phase-completion-summary.tsv`
criterion list and fails on criterion drift. This is a browser-side parity
check for generated gate artifacts only; it does not execute blocked native
runtime probes or allow promotion.
The browser smoke also checks that `runtime-boundary-contract-summary.tsv`
points at the same runtime alignment artifact, row count, boundary kind, and
disabled execution/promotion state reported by
`runtime-boundary-native-alignment-summary.tsv`.
It also cross-checks `native-proof-alignment-summary.tsv`,
`native-runtime-probe-summary.tsv`, and `runtime-probe-gate-alignment.tsv` so
browser validation sees the same source-proof readiness, runtime readiness,
required native proof, target, and disabled execution/promotion state as the
Node inventory.
The browser smoke also cross-checks `native-runtime-probe-execution-plan.tsv`,
`native-runtime-probe-pass-evidence-contract.tsv`,
`runtime-boundary-host-preflight.tsv`,
`runtime-boundary-opt-in-probe-dispatch-plan.tsv`, and
`runtime-boundary-opt-in-probe-skip-evidence-contract.tsv`, keeping the
current host-blocked probe status, missing requirements, opt-in command,
evidence status, and disabled execution/promotion state aligned.
It also checks the host requirement summary and unblock plan against family
host-readiness and preflight rows, including unavailable requirement
ownership, available prerequisite ownership, opt-in environment variables, and
execution command traceability.
It also cross-checks `runtime-boundary-host-readiness-rollup.tsv`,
`runtime-boundary-opt-in-probe-dispatch-rollup.tsv`, and
`runtime-boundary-opt-in-probe-skip-evidence-rollup.tsv` for family/probe
counts, blocked families, missing requirements, blocked opt-in commands,
host/dispatch/evidence status, and disabled execution/promotion parity.
`native-proof-alignment-summary.tsv` aligns native source proof rows with the
generated worklist and native proof gates for user-M, tool DB, and Python
runtime blockers. It is proof-consumption accounting only and keeps execution

72
wasm-port/docs/full-process-boundary-design.md
View File

@@ -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:

211
wasm-port/docs/sim-configs-coverage-matrix.md
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