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>
A pull request whose author is an owner, member or collaborator of the repository runs
Clippy, Native Linux tests, GPU path tests and the reference tests without the
approved-for-ci label, scoped to the affected packages as before; others still wait for the
label. The reference tests leave the pull request fast lane: they run when solidcraft-cli is
selected. ci.yml can also be called (workflow_call) by the release gate, and runs as Run
workflow does. Pushes, merge groups and the nightly run are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`cargo xtask kernel-cases --ladder --gate` grades every ladder case against
tests/kernel-cases/ladder/golden.json and fails on a changed status or count, better or
worse, or a case with no golden; times stay report-only, since they are the machine's. A
right change is re-recorded with --record "why" in the same pull request.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SMLib's parallel projection (CreateParallelProjectionCurves) gives every curve where the
projecting lines cross the face: a line projected down onto a ball came back as its top and its
bottom, each split at the pole, and the link's first wire was half the bottom. A projection onto
a surface is where those lines first hit it (owner's decision, as mainstream CAD does): a curve
is now kept only when the first hit on the body's mesh along the line through its middle is the
curve itself (within 4 chord tolerances), and the pieces that meet end to end are joined in
whatever order and direction they come, a piece run the other way exactly (its knots and
control points reversed; a line's, circle's or ellipse's parameter mirrored). The ball's top
is then one wire from x = -10 to 10.
three_d_sketch_curves now expects that exact curve: one wire, its ends at (±10, 0, √300), every
point of its exact curves on the sphere of radius 20 in y = 0 over the top, to the projection's
own tolerance (a millionth of the body's size), and sweeps_and_pipes_follow_3d_sketch_curves
pipes along the whole joined top. Both pass on the pinned SMLib (90aabff): the pieces lie 9.1e-6
off the sphere against a 4e-5 tolerance and meet at the pole within 4.7e-8 rad, since the fork's
8d95600 keeps the pole's exact tangent in StepBackFromSingularity.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
path_points took any wire with three or more fit points as a fitted spline, and a 3D arc keeps
its start, through and end points as its fit: the pipe along a quarter arc of radius 20 ran
along the cubic through those three points and came out 388.06 mm³, not π·2²·10π = 394.78.
A wire with its exact arc (Wire::arc) now goes to the kernel as that circle, from its start
counter-clockwise about its normal through its sweep (kernel::curve_path of the record circle).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Design defaults gains a Surfaces section with one setting,
surface_extrude_symmetric_per_side (off by default). When it is on, new
symmetric surface extrudes go their distance each way, as they did
before they matched solid extrudes. The app hands it to the session
before every command and each frame, and it stays with the user across
tabs and new designs, like the metric tap drill rule.
The Surface Extrude dialog now sends a feature's stored convention only
when the feature is already symmetric, so a one-sided one switched to
Symmetric takes the new reading, as in the solid Extrude dialog.
Labels in en, ar, he, ja, zh, de and ko.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A symmetric surface.extrude given no convention now splits its distance
evenly around the start plane (10 mm: 5 mm each side), the way
solid.extrude reads it, instead of going the distance each way. Both
commands take their default from one function, which a session setting
(surface_extrude_symmetric_per_side) can turn back to the per-side
reading for surface extrudes. timeline.edit and timeline.redefine give a
one-sided surface extrude made symmetric the same default.
Saved designs are unchanged: every surface extrude saved its convention
(legacy_per_side), and one saved before the marker existed reads per side
as it always did. The help of both commands says how the distance is
read. The 3830 kernel case, recorded with the per-side reading, now says
so explicitly.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tangency-labs/smlib#57 on top of 60b1c6a. It fixes the two engine tests the earlier pin broke:
press_pull_on_curved_faces and a_shell_fillet_does_not_follow_a_gone_edge_onto_a_smooth_seam,
with their expectations unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The barrel's arc has its centre across the axis, so its side is the inner (lemon) zone of a
spindle torus, which SMLib's torus does not describe (its meridian is on the X side): SMLib
(revolve-spindle) sweeps it as the exact rational surface of revolution. shell_of_a_revolved_barrel
asserted an analytic torus of major radius -10. As the owner decided, it now asserts what
matters: two flat caps and the curved side, the closed-form volume, 14 mm round at mid height,
and after the shell the two offset faces (the inner wall and floor; truck's side was in halves).
Needs SMLib with revolve-spindle (pin bump).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>