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>
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>
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>
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 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>
With SMLib integration-overnight + b78bd4a (the fixes of 2026-10-29), three
expectations that held a refusal now build, each checked against its exact answer:
- rig fillets/1207-fillet-box-end-edge-into-unblended-round (was ...-refused): the end
face's top edge of a cube rounded r3 along its top back edge, rounded r1 alone
(tangent chain off), builds. Its round runs on along y through the r3 round's end
until that surface drops below it at y = 17 + sqrt(5): V = 8000 - 20 (9 - 9 pi/4)
- 17 (1 - pi/4) - 0.218236 = 7957.505202 (the last term the section under the round,
integrated exactly); SMLib gives 7957.505245.
- blend_smlib smooth_edges_and_unfinished_tangent_chains_are_refused_saying_why: the
same cube builds, at that volume.
- modify_history_tests::smlib::draft_tilts_a_side_and_keeps_its_name: the rod's side,
a cylinder along the pull, drafts 5 deg to a frustum, radius 5 at the neutral plane
and 5 - 10 tan 5 deg at the top, at its exact volume.
tests/kernel-cases/fillets/KNOWN_FAILING drops 1557-fillet-vertical-corners-after-
bottom-rounds, which passes now; the other eight still fail, so the gate holds
(81 pass, 8 known failing, no regression).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ten cases the pin fixed leave the list (the 1207 corner patch and its together cases, 1390,
4782 reduce-fit, 896). 1557 joins it with its cause: since bodies are read back from their
records (#8625) its bottom rounds come back as SmCylinder where SMLib's blend made SmCone(0),
and the corner-ball trace starts 2.78e-4 off; its fix is in progress.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Four continuity cases for the patch fill. A hole in one smooth sheet (a cubic Bezier profile
extruded, a square trimmed out) patched g2 and g3: every seam reaches the order, corners
included, since round the hole there is one surface. The hole a three-round corner's blend
face leaves, patched g2 and g3: exactly g1 over each whole seam, since at the hole's corners
the rounds meet each other G1 (their curvatures differ by 1/4 or 1/8 per mm) and a patch smooth
there has one curvature; the middle of each seam reaches the order (kernel test).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cargo xtask kernel-cases --known-failing FILE grades a set against its
baseline: it fails on a case that fails and is not listed (a regression)
and on a listed case that passes (fixed: its line goes, so the list only
shrinks). The Fillet rig workflow runs the fillet set that way on pull
requests touching the blend, fillet, corner and continuity kernel files,
crates/smlib, eval*.rs, engine features.rs or the cases: one release
build of solidcraft-cli on a Blacksmith runner, SMLib prebuilt, sccache
on a sticky disk that main and develop commit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New: an r5 curvature corner at a box corner (its patch must seam G2), an
edge running tangentially into a round left out (refused: continues
tangentially), a convex r10.01 round 0.01 past a 10 mm face (built by
subtraction: V = 7139.875, A = 2585.140). The bar and boss arc rounded
together say their crease (15.6 deg r2, 13.1 deg r1); 1390 expects SMLib's
unsupported-corner refusal, the honest reason today; past a full round
the exact fit's refusal names the largest radius that fits, 7.5 mm.
KNOWN_FAILING lists the 18 of 89 fillet cases failing today, each with
its cause.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new `continuity` area: seams whose order is certain by construction, each graded
`exact` (reads its order and not the next) at picked edges with Continuity Analysis's
default stations and tolerances: a box's crease (g0), a chamfer in place of a round (g0),
an r5 round on planes (g1), and a profile closed by a g1, g2, g3 or g4 blend curve between
lines, extruded (g1 … g4). `continuity.edges` may now be a list of points, picked as
`inspect.continuity` picks them, and `continuity.exact` asks for the order and no more.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
expected.json may give `continuity: {order: g0…g4, edges?: "blend" | "corner"}`: the
seams of each round, chamfer face or corner patch with the faces either side of the edge it
replaced, and of each corner patch with its rounds, are measured as Continuity Analysis
measures them (seam_diagnostics at its default 33 stations and default tolerances), and the
case fails naming the worst seam, its faces, the order it reaches and the next order's worst
value. The seams come from the faces' persistent names (doc::naming::blend_seams). The older
`{near, within_mm, …}` form is kept.
Every fillet-area case with a body gets its order: constant rounds and rolling corners g1,
curvature rounds g2, chamfers g0, the corner: g2 patch g2 at its seams.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ten `refused` cases outside the fillets had no `refusal` since #8445 made one required. Each
was run; its refusal is the right answer for the reason its method gives, and that reason is
now its `refusal`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A corner setback must reach past where the corner's rounds' contact lines
meet without one (smlib_blend_setback); short of it SMLib failed with its
own status (1001). The kernel now refuses it before SMLib runs, for the
rolling-ball corner (fillet_setback) and the curvature corner
(fillet_g2_corners) alike, naming the least: on each face at a corner of
planar faces and straight edges the two rails, r tan(psi/2) from their
edges, cross (d2 + d1 cos alpha) / sin alpha along an edge (r on faces
square to each other). Other corners stay SMLib's to refuse.
The rig's `refused` cases now name the reason (`refusal`, a part of the
message, required), so a failure for another reason no longer passes; a
`solid_or_refused` case may name one. Fillets: the setback cases and
783, 3435 pass; 1390, 896, 4782 past-a-full-round and the no-tangent-chain
case are refused for an unclear reason and fail.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
22 hand-written cases in tests/kernel-cases/fillets:
- 1207-fillet-bar-top-edge-and-boss-arc-together (r2, r1, fit reduce,
fit taper, curvature corners): a bar's top edge and the partial base
arc of a boss standing out over the bar's side rounded together. The
rounds' volumes away from the corner, the corner patch within (2r)^3.
SMLib's 3x2 mixed corner fails here (1001) until the fork's fix.
- 1207-fillet-bar-top-edge-after-boss-arc-round (r2, r0.5, no tangent
chain): the edge rounded after the arc; r0.5 fails SMLib's check.
- 9-fillet-corner-*: setbacks not past the radius refused (rolling and
curvature corners), the curvature corner at r1, and the curvature
corner with reduce and taper fits (not supported yet).
- 4782-fillet-*: full rounds (two end verticals at half the width, exact,
reduce, taper), a round at half the wall, radii past the full round
(refused; reduce gives the full round) and a round wider than both
faces (built by subtraction).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every tapped hole now drills the tap maker's tabulated drill. ISO metric takes Yamawa YEU23's
drill size column for cutting taps (printed p.704, M coarse; pp.704 to 706, MF fine): M8 drills
6.8 mm and M12 10.3 mm, where the major less the pitch gave 6.75 and 10.25. A custom metric size
the table lacks keeps the major less the pitch. UNC/UNF (Guhring), G, Rp, Rc and NPT (Yamawa)
were tabulated already. The Thread command's suggested hole for a metric size follows.
The Hole dialog's Tap drill diameter is now a field, the tap maker's drill by default, and the
command's `diameter` with a thread is checked the same way: a drill is accepted from the
internal thread's standard minor diameter (or the tap maker's drill where that lies below it:
Rp, Rc, NPT) to 5% over the tap maker's drill. Outside that the command names the range and
why. The field's tooltip gives the drill, the minor diameter and the range. Presets keep a
chosen drill.
A saved design keeps the diameter it stored, so it builds as before, and editing such a hole
keeps its drill: no preference and no format change. Scripts that give a thread without a
diameter drill the new default; ladder 05/007, 11/003 and rig case threads/2115 follow
analytically, and their golden entries are re-measured from runs (tier 05 re-sorted by time).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LUXeKMoxpM7Vuv8Rb6E3K2
Ladder 06/017's golden entry was edited by hand when the chamfered tip moved to ISO 724's d3.
Re-measured by running the case (solidcraft-cli kernel-cases on SMLib): its counts, area and
volume are the ones written by hand; its time is the run's. The tier's order by time holds.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>