A case's construction field names construction points, axes and planes with the point, line or
plane each must be, and results reads values out of the commands' own replies by JSON pointer.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new plastic area with its KNOWN_FAILING (empty: every case passes) and the
sources whose change reruns it; the README lists the area and the new files and
results fields.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A case's expected.json may name files written to $OUT (json, csv rows, or a DXF's
entity counts and curve lengths per layer) and a command's answer by step, each
matched as a part of what was made.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cargo xtask kernel-cases --coverage lists every built registry command that no recipe.json under
tests/kernel-cases runs and fails unless tests/kernel-cases/EXEMPT lists it. EXEMPT holds 252
commands with no geometry to grade and, under [to cover], 133 geometry commands still waiting for
a case; a listed command a case now uses, or one the registry no longer has, fails the check, so
the to-cover section only shrinks. The gate's build job runs it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The booleans area also reruns on sketch projection from the model. The selection self-test
fails on an area glob that matches a file PATHS-ALL already covers, so a whole-crate glob
cannot creep in.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A plan job (scripts/ci/kernel_rig_plan.py, with its self-test) maps a pull request's changed files
to the areas: tests/kernel-cases/<area>/PATHS for each area, tests/kernel-cases/PATHS-ALL for the
shared core, the ladder whenever any area runs. Areas come from the folders, so a new one needs no
workflow edit. Pushes, merge groups, the release gate and runs by hand run every area. The
kernel-rig check counts a skipped build or shard as passed only when the plan selected none.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The gate passes no secrets to release.yml, so the macOS and Windows signing steps skip as
they do on a fork (no signing secret, no SignPath quota), and the new packages_only input
skips the release job (checksums, update signing, publishing). The call still grants
contents: write, which GitHub checks for the skipped job before the run.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tests/kernel-cases/README.md describes the kernel rig gate for every area, how a pull request
updates its area's KNOWN_FAILING, and the ladder's --gate and --record. The tests skill and
CONTRIBUTING say which pull requests run the native and reference tests, and what the
release gate runs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
release-gate.yml, run by hand on a branch, calls ci.yml as Run workflow with
cross-compilation (every native suite in full, reference, doc and GPU path tests, the whole
action matrix, property tests, web-offline, wasm, Windows FXC and startup), kernel-rig.yml
(every area and the ladder) and release.yml as a dry run (every package and its smoke
tests), and passes only when all three pass. release.yml can now be called (workflow_call).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kernel-rig.yml builds solidcraft-cli once (release, SMLib prebuilt; sccache on a sticky disk
that only pushes to main and develop commit) and hands it, with the rig's runner, to a matrix
of eleven shards: the ten areas of tests/kernel-cases/, each against its KNOWN_FAILING, and
the ladder against its golden. One path filter covers the kernel surface; drafts skip; a new
push cancels a pull request's old run; merge groups always run it, and the release gate calls
it. The areas other than fillets get a KNOWN_FAILING with only its header, to be seeded from
develop after the SMLib pin bump.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>