87 Commits

Author	SHA1	Message	Date
jyviko	f74c6605c4	Fillet: Mitre or Swept corners where two rounds meet (#11498) ... * SMLib wrapper: a swept or mitred turn for constant rounds (Turn) Brep::blend_dropping takes a Turn: Mitre (the default, as before) or Swept, which sets solidcore's FilletSession::set_swept_turns before the corners are made. A swept turn solidcore refuses at CreateFilletCorners comes back as Error::TurnRefused with its reason and place (NoRoom at a concave side edge, else CornerUnsupported). Swept is for Blend::Round only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel: fillet rounds turn in a mitre or swept (FilletTurn) fillet_removing, fillet_max, fillet_max_each and fillet_each take a FilletTurn and hand it to SMLib, through the reblend of earlier rounds at a later corner too. A swept corner solidcore does not build is refused as invalid input with its reason and place: no smaller radius builds it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Design: a fillet saves its turn, mitre (default) or swept FeatureKind::Fillet gets `turn` (FilletTurn: mitre, the default and not saved, or swept), one pending format file. Evaluation hands it to the kernel, pattern copies included, and refuses a swept turn with a style, fit, corner or setbacks the kernel's swept corner does not take (SWEPT_TAKES). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * solid.fillet: the turn parameter, and the command's input and output schemas `turn: mitre|swept` on solid.fillet, refused when unknown or with options a swept corner does not take. solid.fillet now has its contract (FilletParams) and reply type (FilletResult), registered with checked!, and leaves schema/unconverted.txt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Fillet dialog: a Turns choice, Mitre or Swept A Constant radius fillet's Turns row sends `turn: swept`; choosing a narrowed radius or a curvature corner puts it back to Mitre, and Swept puts those back. Its tooltip says what each does where two rounds turn round a corner edge. New strings in a pending locale file (en, de, ja, ko, zh); glossary entry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Fillet turn: the schema tests' fixes and the complete catalogs' strings The no-contract example in the schema tests is solid.chamfer now that solid.fillet has one; the reply test checks the mid-radii form against the contract (solidcore refuses that law's corner yet, #430) instead of building it; Arabic, Hebrew and Vietnamese, complete catalogs, get the new strings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Fillet schema test: variable and spline forms checked against the contract solidcore fails a variable round on a box edge at this pin (status 1001, as variable_radius_on_a_box_edge), so the reply test checks those forms against the contract instead of building them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Fillet turn: the swept rig cases pass; the MCP no-contract example is solid.chamfer cov-fillet-turn-swept-boss-base-r1 and cov-fillet-turn-swept-pocket-sharp-corner-refused-r1 pass now that solid.fillet takes `turn`: off the rig's known-failing list. The MCP bridge test's example of a command without a contract was solid.fillet, which has one now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ --------- Co-authored-by: jyviko <2501648+jyviko@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-03 20:36:00 -05:00
Nathan Dane	fbd30b0bd0	Panels: inspect and change layouts through commands (#11304) (#11454) ... * claim: #11218 * Panels: add shared layout rules and retained content runtime * claim: #11304 * Panels: inspect and change layouts through shared commands (#11304) * Panels: account for layout commands in geometry coverage	2026-11-03 13:55:50 +00:00
jyviko	ea772a0438	Merge develop into main: SolidCraft on the SMLib kernel (v1.1.0-alpha) (#11351) ... * UI: rim and wall picking tests for a circle of arcs that is one wall A circle drawn as two half arcs now extrudes to one full-turn wall with its seam edge, and each rim is one closed edge (tangency-labs/smlib#67). The tests keep their intent on that body: a rim clicked once is one item, measured and highlighted whole and picked from either side; a wall picked either side of its seam is the same surface, lit whole, and toggles off from the other side; every face is its own patch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillets: a later round at a corner where earlier rounds meet blends them again with it The owner's ruling of 2026-10-30: a later fillet on an edge at a vertex where earlier rounds already meet in a mitre makes the corner rounding all of them at once makes, one smooth patch, the mitre gone. A body made by constant-radius rounds keeps what they were made on and which edges they rounded at which radius; a later round reaching such a corner blends the earlier rounds' edges (from the earliest of those meeting there on) with the new edges in one SMLib blend of the body before them. The result's history is put over the body the later round was given: an earlier round's face is that face trimmed anew (its name kept), the corner patch and the new rounds are the later fillet's. A picked mitre seam has no round of its own: it is refused unless a new edge of its radius meets it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a later r3 round at an r2 mitre, through the Fillet feature, makes the all-at-once corner Two box edges rounded r2 in one fillet, then the upright edge at their mitre r3 in a second fillet (tangent chain on, so the seam comes with it): 10 faces, 7928.743041 mm³ as fillet_radii of the box gives, the r2 rounds' names kept, the r3 round and the corner patch the second fillet's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel: a body's record of rounds goes with its history, and can be read back The rounds that made a body are over the body its history is over: a new history (an operation carrying a step's result back to its own operands) leaves the record out, so a later round never reads one history against another body. Body::rounds gives the record and Body::with_rounds_of takes one back, checked (edges of the body before them, a fillet's radii, the body's history over that body), for a saved model to keep it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Model cache: a body made by rounds keeps them, so a later round blends them the same after opening A design gave another body when opened from its model cache: the rounds a body was made of lived only in memory, so a later round at their mitre was built sequentially (or refused, as too large) after opening and blended with them when evaluated anew. The saved model now records, per kernel body made by rounds, the body they were made on (a place in the bodies, stored once though no state holds it) and the edges with their radii; reading it attaches them back down each chain, and a thinned model keeps those bodies with the bodies made from them. Model cache format 7. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a corner patch of rounds 2/3/4 takes no more than the strips leave in its block three_rounds_at_a_corner bounded the patch's extra cut at 3 mm³ beyond the strips, a figure with no derivation; SMLib's all-at-once body at radii 2, 3, 4 takes 3.099 (V 7878.579574 against strips 7881.678). That body is the strips' outside the block its patch lies in: its rounds are the strips' cylinders ending at a's section y = rc, b's x = 20 − rc and c's rails where they meet a's and b's (the patch's four corners, now asserted), so the patch takes at most what the strips leave in that block (11.86 at 2/2/3, 32.69 at 2/3/4). The lower bound is that block; the upper one, at most the strips' volume, stays. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: the io crate's hand-built saved models list their rounds, as format 7 records do Model cache format 7 (f3cf0c4f3) records a `rounds` list in every saved model, and reading one without it is refused ("saved model: rounds"), as is a model without any of its other lists: the states, the preview and the thinned model all came back empty. The io tests' saved_model and timeline_model wrote format-6 records, so six tests (the round trip, the repeated part stored once, and the four too-big-for-the-file cases) read nothing. Their bodies are none made by rounds: the list is empty, and every expectation stays as it was. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * SMLib: pin eaa998a (tangency-labs/smlib#68, #69, #70) Batch 4: drafts and loops, mitre corners, rim chamfers, rulings, tight box, stitch, point classification, eased corners. Batch 5: a face's tight box divides its cells at the surface's knots (thread boxes exact); a cylinder, cone, sphere or torus is extended along its own circles. Batch 6: a revolution's extension closes its turn; a dropped point's foot is the converged one. The C API is ABI 5 (smlib_blend_dropping and smlib_brep_classify_point are new; nothing existing changed), so the binding expects 5. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a strip's tangent and curvature run-offs are the distance long across the surface SMLib measures an extension's distance across the surface (smlib_extend_sheet corrects CreateExtendedSurface until the parameter line through the side's middle is that long), so each run-off of the cylinder strip, swept 20 along z, adds 5 x 20: 10 pi/2 20 + 100 = 414.159 for both. The parabola-length formula (418.18) was truck's. Ruling d2 (2026-10-30). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: one smooth angle, and a round too small to change the part is refused The blend's tangent angle is the shaded view's half degree (smooth_edges::ANGLE), one value for smooth. A constant round lies r (sec(d/2) - 1) inside the crease it replaces (about r d^2/8); below the edge's tolerance it changes nothing and is refused before SMLib (which answered SM_ERR_INVALID_INPUT), naming the smallest radius that rounds, tolerance / (sec(d/2) - 1). d is the least turn along the edge (tangent_edge::least_angle_along, at tangent_all_along's stations). Ruling d3 (2026-10-30). The block's tolerance is 2e-5 mm, not 0.1 um: at 1 deg the smallest radius is 0.526 mm, so R2 and R20 reach SMLib, which still calls an edge within 2 deg smooth (SmEdge::GetBlendEdgeuse); that test is ignored until SMLib uses 0.5 deg. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: the knife-edge chamfers name SMLib's cause, a cusp's ball radius of 0 smlib_chamfer turns the distance into a ball radius d sqrt((1 - c)/(1 + c)), c the faces' binormals' dot (capi chamfer_radius); at #851's cusp the binormals agree, the radius is 0 and the call is SM_ERR_INVALID_INPUT before the fillet executive runs (gdb: chamfer_edges sees radius 0; the dump's why is empty). SolidCraft hands every chamfer to SMLib, so the ball-contact chord (the ball of radius d: 3.822 wide at d = 2, 159.2365 removed) is SMLib's to build. Ruling d4 (2026-10-30). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel tests: a corner round wider than its faces overflows and takes the corner's other edges R21 on a 20 mm cube's edge builds (6107.529370, closed form, to 2e-12). With R5 on the corner's other edges the R21 takes the faces they lie on, so the body is R21's alone; SMLib fails that blend (status 1001, fillet error 4, Unable to Trim Rail Curve) and the test is ignored until it builds. It replaces the refusal test that expected TooLarge. Ruling d8 (2026-10-30). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a 1 degree crease rounds, and the knife edge's chamfers build, on SMLib smlib-batch-4-rulings With SMLib's smooth limit at half a degree (422e6f1) the 1 degree crease rounds R2 and R20 (the test is no longer ignored), and with a cusp's chamfer the ball of radius d (d231547) the The 0.5 one stays, for its own cause (the chamfer face left apart from the body). Two corner cases the same SMLib (replay/1.0.1 and those commits) builds come off too. Needs SMLIB_REV at that SMLib once it is pushed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel, doc: an overflowing round goes first; an edge it removes is gone, and the fillet says so SMLib (smlib-batch-4-rulings 0e83cca, SMLIB_ABI_VERSION 5) rounds the edges whose rounds overflow their faces first and then what is left of the others; smlib_blend_dropping says which picks' edges the overflow removed whole. The smlib crate binds it (Brep::blend_dropping), the kernel returns those picks (fillet_removing), and a fillet notes them as its warning: "the edge at (0, 0, 10) was removed by the larger round, so it is not rounded" (a 50 x 50 x 20 block, R21 on its bottom front edge with the front left upright: the block is R21's alone, in closed form). Ruling d8: [21, 5, 5] on a 20 cube builds as R21 alone (6107.529370); the test is no longer ignored. R25 with R2 at a corner (blend_corner) builds the same way, R25's alone in closed form, where it was refused. The rig's 1080 notched block outline at R8 builds now and comes off the known-failing list. Needs SMLIB_REV at that SMLib once it is pushed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: the knife edge's 0.5 chamfer builds SMLib's trim took a fillet meeting its face at more than 78 degrees for one with no side (smlib-batch-4-rulings 971e567); the chord of the knife edge's 0.5 chamfer meets the flat face at 81 degrees. The case comes off the known-failing list. Needs SMLIB_REV at that SMLib once it is pushed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a 15° tapered text builds, every letter grown, exact where its outline gives it Owner ruling d6: the letter t of "tres long" was drafted inward by SMLib (its loop's normal, summed from the cross products of its chords, pointed down; fixed in SMLib). With the fix every letter grows, and the join builds at 3° and 15° by the Round rule and by the default rule (tangent for spline outlines), where before 15° was expected to be refused. Exact where the outline derives it: a letter's section at height z is its outline offset by e = z tan a, by the Round rule of area A + P e + C e² while the offset trims nothing (Steiner; C half each loop's turning less tan(t/2) - t/2 at each reflex corner), so the letter is A h + P k h²/2 + C k² h³/3. Each extruded alone, the t at 3° and s, l and o at 3° and 15° are checked to 1e-6 (SMLib measures them within 1.3e-9; its mass properties integrate to 1e-8). The concave joins of r, n, g and e are tighter than e already at 3° (their swallowtails trimmed: r 1.1e-3 under the formula), the t's by 15° (9.9e-5 over), and on the block the letters grow into each other, so the whole word is checked for what holds exactly: one closed body with the block, and half-way up every point of each straight letter's outline inside the solid (the t drafted inward failed that). With SMLib's fix (smlib-batch-4-text-loops 82133b2). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: a sloped basin's mitred rim rounds are checked tangent along their contact lines 1080-fillet-sloped-basin-1-mm-rim-r0-5-4-edges asked G1 at every blend seam. Its front wall leans 19 over 20 and the others 10 over 20, so at each rim corner the two mitred rounds meet the sloped corner edge at different heights (0.155625 and 0.276393 below the top): the deeper round runs on past the corner edge and is cut by the plane of the other's wall, a crease by construction, the gap below the shallower round filled on that plane. The check now measures the rounds' contact seams, on the top and on each wall, where the rounds are tangent. The volume is unchanged. With SMLib smlib-batch-4-mitre (1c15364): the case passes (V 144530.427946 against 144530.427909, 15 faces, sound); before it, only the four corner creases failed the check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * smlib: Brep::classify_point says exactly where a point lies against a body Binds the fork's smlib_brep_classify_point (SmBrep::Point3DClassify at the body's own zone tolerance): inside, outside, or on the boundary within that tolerance of a face, an edge or a vertex. A box and a cylinder just off its curved wall in measure's tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * kernel: Body::classify_point decides inside, outside or on the boundary exactly SMLib's point classification at the body's own tolerance, on the exact faces and edges, in place of a mesh at a chord of 2e-3 of the body's size (about 0.4 mm on a 200 mm part). A point within the tolerance of a face, edge or vertex is OnBoundary, never decided by a ray. A mesh body's triangles are its exact shape: on them within the record's tolerance, else by ray crossings. The kernel's own probes move to it; Body::contains goes once its last callers have. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * doc: a hole decides whether it exits at its drill point's shoulder exactly Material past the depth needs a body with the point inside, air before it needs every body to have it outside; a point within a body's tolerance of the exit face is neither. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * engine tests: probes ask for the exact point class Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * ui, cli tests: probes ask for the exact point class Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * kernel: Body::contains, the mesh test, is gone Every caller asks Body::classify_point now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NvoxKQ2rEZvcXNQnhE3Sgs * kernel tests: the rim chamfers running off their rims build, on SMLib 737c392 chamfer_wider_than_sloped_basin_rim_builds and a_rim_loop_chamfer_running_off_its_rim_builds waited for SMLib to build the cliff overflow (CloseRemovalRegion refused it, SM_FILERR_NO_ROOM). The pinned SMLib builds it (eddf0ede4, bba9914b6): both pass on aarch64 Linux and are no longer ignored. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: the cases SMLib 737c392 builds come off the known-failing list The gate on aarch64 Linux reports 16 fillet cases FIXED with the pinned SMLib: the sloped and equal-slope basin rim chamfers and rounds past their rims (1080-*, 5835-*), the pocket rim chamfer past the floor, and the three pocket rim rounds now mitred at the pocket's corners (every-pocket-*). No other area's gate reports a case fixed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: the re-blend's removed picks formatted as rustfmt lays them out Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: blend_smlib laid out by the 2024 edition's rustfmt Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Skills: the tests skill's unit-test example stays under the 3600-character limit Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet: the radius-too-large choice in plain nouns "If too large: Stop and say so / Largest that fits / Narrow where needed" becomes "Face limits: Exact radius / Largest radius / Narrowed radius", in every language of the catalog, with the error and the tip that name them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: a round that would cut through its wall into a hollow is refused The owner's rule of 2026-10-30: a round running past a rim of its faces into open air builds; one whose section would remove material through to a hollow behind its edge (a slit into the hollow, a cut through the part) is refused as too large, so the fillet names the largest radius that fits. Decided exactly in the section of a straight convex edge between planar faces: the round's centre is at depth r below both planes, and it opens where its arc uncovers a boundary point strictly inside the wedge with no material beyond it toward the centre (the body's exact point classification). Looked at: straight edges parallel to the round's (a hollow's corner), cylinders about parallel axes (a rounded corner), and a picked concave parallel edge's own round, which fills the corner. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: 1668's R7 past the inside corner is refused at 4 + 2 sqrt2 The round's centre (32 - r, 42 - r) leaves the hollow's corner (30, 40) outside its circle, opening the wall, where sqrt2 (r - 2) = r: the case expects the refusal naming 6.828. 2852's R30, refused naming 25.24, now passes too: both come off the known-failing list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * xtask: known-failing grades a nextest junit report against tests/KNOWN_FAILING_TESTS `cargo xtask known-failing --junit PATH` reads nextest's junit (a file, or every .xml under a directory, so all of a run's junit artifacts at once) and fails on a test that failed and the list does not name, and on a listed test that passed (FIXED: take its line off, as the kernel rig's gate does). A listed test that did not run is neither, since a pull request tests only the packages it touches. The list has the rig's KNOWN_FAILING format (`<test> <cause>`, sorted, the rig's own parser), with `<test>` nextest's `<binary id>::<test name>`; `cargo xtask lists` checks it is sorted. The list starts empty. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * CI: the test jobs grade their junit against tests/KNOWN_FAILING_TESTS Native Linux tests and the GPU path test shards no longer fail on any failed test: nextest's "tests failed" exit (100) goes to `cargo xtask known-failing --junit`, which fails on a failure the list does not name and on a listed test that passes. Any other nextest exit (a build error, a bad filter) still fails the step at once. The tests skill says to list a failing test with its cause, in place of ignoring it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: the known-failing list takes develop's 10 failing tests Develop 38fd4a4f6 (CI run 41157648345, after the SMLib eaa998a pin) fails 10 cargo tests; each is listed with the cause its failure message gives. Seven are SMLib refusals or results off their derived volumes (fillet, chamfer and shell), the cli action matrix and naming corpus among them; the two corner_g2 tests are the fitted G2 corner patch bulging past the box, which the explicit G2 corner fixes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Reference tests: the eight cases that fail on SMLib eaa998a name their cause as known failures Develop 38fd4a4f6's Reference tests fail 34, 35, 77, 78 and 81 (STEP export finds fillet edges 4.6e-5 to 6.1e-5 off their surfaces against 2e-5), 37 (the apex blend 0.193 off), 80 (the taper-to-fit area) and 83 (thicken status 1001). Each expected.json names its cause in known_failure, which the oracle already reads: a known failure that passes fails the job. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Sweep path: a curve of several pieces is turned round whole The path chain oriented its first piece, not its first curve: a first curve of several exact pieces (a fit spline, an ellipse, a projected free-form edge) was never turned round, so a path whose next curve meets it at its start was refused as "not connected end to end". The chain now orients curve by curve: the first runs toward the second where they meet at one end only (else from the end nearest the profile), each next one starts where the previous ended, with one joint tolerance for both questions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * SMLib: pin 2fc375f (tangency-labs/smlib#71, #72, #73) A sheet's side is extended exactly the distance asked, or the call says it cannot (#71); NVIDIA's -Werror build passes again (#72); a body splits by a sheet of several faces as it is, smlib_split_body_by_sheet (#73). The C API is ABI 6 (the new entry), so the binding expects 6. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: Extend grows a surface of several faces face by face A surface body of more than one face (a fit-point spline's spans extruded, #3830) was refused. Each face with a picked edge is now extended alone by SMLib's extension of its surface, and the faces are sewn back together, each the face it was. A side that lengthens onto a face meeting it tangent takes that face along, past its edge continuing the picked one; across a crease the neighbour grows only when its edge is picked too, otherwise the extension is refused. Faces whose lengthened sides no longer meet are refused. Up to a target keeps the pieces every grown face lies in. 3830's extensions now build; its split still fails (the tool point picks one span, and a face tool cuts with that face's surface alone), so it stays on the list with that reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: Split Body by a face of a smooth sheet cuts with the whole sheet A face tool cut with that face's surface alone, so a face of a surface body made of spans joined tangent (a fit-point spline extruded, #3830) cut nothing where its span ends inside the body. Split Body by a face of a surface body now takes the faces joined to it tangentially (the exact check Extend uses, within the one angle for smooth) and slices with them as they are, through SMLib's slice by a sheet (smlib_split_body_by_sheet, tangency-labs/smlib 7a01f1b), its sides those of the picked face. A sheet that only nicks the body cuts nothing, as before; a lone face, or a face of a solid, still cuts with its surface extended. 3830 comes off the booleans list. Its answer counted the two halves of the cup and not the surface that cut it, which stays as a body of its own (4879 removes its surface for that reason): three bodies, the volume unchanged. Needs SMLib 7a01f1b pinned (SMLIB_REV, prebuilt; its SMLIB_ABI_VERSION 6, which crates/smlib now expects) to link. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a cylinder strip's run-offs are 100 pi + 100 to 1e-6, SMLib's exact area The tangent and curvature run-offs of the quarter cylinder r 10 strip, 5 across the surface, are its section swept 20 along z: exactly 10 pi/2 20 + 5 x 20 = 414.159265. measure is SMLib's integration on the exact surface (1e-8), not a mesh, so the run-off check is 1e-6 relative and the 'measured on meshes' notes go. Red until SMLib's extension is solved to its distance (smlib-extend-converges 590d8a1): eaa998a's curvature run-off is 4.986 long, area 413.882. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * kernel: an extension SMLib cannot make exact says so, naming the length asked Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Sketch: a control spline can carry its own knots and weights A sketch spline over control points was always the clamped uniform B-spline over them, so a free-form edge whose knots are not evenly spaced (or whose weights are not 1) could only come into a sketch as one curve per Bezier span. A control spline now may save `nurbs`: its clamped knots and its weights. Its points, polyline, exact pieces (one a knot span; conics for a rational quadratic), the solver's distance and curvature, links, parallel re-projection and inspect.sketch all read them; a loaded design's are checked. One pending format file (spline-knots). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Sketch projection: a free-form edge comes in as the one exact spline it is A projected spline edge of several Bezier spans came into the sketch as one curve per span (#1508), so a G2 round's bottom edge was 16 curves and a path naming the corner named one span of it (#3604). The kernel now reads such an edge (a spline, or an elliptical arc of several spans) as the one clamped B-spline it is over the edge's interval, its knots and weights its own, and the sketch takes it as one control spline whose ends sit on the edge's vertices. Planar regions still read edges span by span. The 3604 case builds with its original path and leaves KNOWN_FAILING. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: blends past an outer rim of their faces build, on SMLib smlib-blends-past-rims The owner's ruling: a round or chamfer that runs past an outer edge of its face into open air builds, tangent where it has room and cut by the face beyond where it runs out. SMLib's branch smlib-blends-past-rims builds them by the rig's analytic answers. Off the known-failing list: the disc's rim past its 2 mm wall (190), the hole's top rim R12 past the plate's bottom, the chamfer past the cylinder's bottom (2893), each closing on the wall continued as itself, and 926's chamfer ending on the boss's wall, which now builds to its answer too. The sloped basins' R4 rim rounds (1080, mitred rounds built together where one overflows) build to their analytic volumes (to 6e-9), and stay listed with that reason: their continuity check (g1 at every blend seam) takes in the mitres' creases, G0 by the mitre ruling. 2893-chamfer-two-distances-elliptical-rim is graded as a solid (the owner: it builds) and stays listed, waiting on the ruling on unequal chamfers along a rim whose angle varies. 5158-fillet-round-just-past-a-10mm-face stays listed with its cause found: the round passes 5e-6 under the box's top back edge, inside the body's tolerance. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Naming: test that a round of a round's end has no seam with that round's faces The r1 round of a block's top edge, chained onto the end curve of the r2 round of its arc at a cylinder (rig fillets/every-block-cylinder-crease- top-edge-after-arc-round-r1), ends where it runs into the cylinder. That edge is no seam of the r1 round: the cylinder is a face of the r2 round, not of the r1. blend_seams takes it for one today (the r2 round's name F3:blend:F1:+z|F2:side holds a | of its own), and the rig reads it as a contact seam at 60 degrees. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Naming: a blend's seams split its edge's name at the | between its two faces A blend face's name holds the edge it replaced, <face>|<face>, and a side of that edge can be a blend face whose own name holds a |. Whether a face is a contact of the blend was read as the edge's name starting or ending with the face's name next to a |, so the r2 round's own face F2:side read as a contact of the r1 round F4:blend:F1:+y|F3:blend:F1:+z|F2:side. The edge's name is now split into its two faces, a blend side read whole as the two faces of its own edge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fillet rig: five refused blends build, off the known-failing list 926 (the chamfer ending on the boss's wall), the oblique cut's r0.1 round, the every-block r1 round (its seam with the cylinder is no contact seam, after the blend_seams fix), the up-down squares' concave chamfers and the shelled box's lip chamfer build with SMLib branch smlib-blend-refusals (f8650b8 and later). 1207 r0.5 passes SMLib's check on its rails now and stays listed for the next cause: its end rib on the boss, which starts where the round and the boss are tangent. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the trough and the pocket whose floors fall to a drain build SMLib now offsets a vertex where four faces meet (two walls and two facets at the floor's corners, four facets at the drain) to two vertices joined by a new edge (tangency-labs/smlib branch smlib-shells). Both volumes match their closed forms. The pocket's lining, hanging from the top's rim round the pocket, stands apart from the slab's outer walls with the cavity rising between them to the open top: the case says two shells in the one body. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the plate with a hole through its arc side shells open at its far end SMLib's merge now intersects the offsets of an edge's faces where they could not be mated along it (the hole's offset poking out through the half-round side's; tangency-labs/solidcore#1795): one closed valid solid with the one face open, as the owner ruled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the ring cut frame and the up-down join shell SMLib's inset now keeps only the regions that are cavity, not the one the offsets close where they overlap (between the two faces of #545's 0.5 floor, round the up-down join's two empty octants). The frame's core under the recess is hollowed to a sealed void, so the case says two shells and its closed form, 21044 mm³. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: #616's lid shells open at a rib's side, with the 0.15 lip SMLib keeps the skirt top's offset where its loops wind the other way under the opening, the cavity's floor (the owner's ruling of 2026-10-31: build it; a lip thinner than the wall is no break-through). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Known failing tests: the action matrix's shells and chamfers as they fail with SMLib batch 7 The ring cut frame's and the up-down join's shells build now, and so do the up-down join's and modern-plastic's chamfers (SMLib smlib-blend-refusals). #616's lid in the corpus still fails SMLib's loop check, the shelled box shelled again at an inner wall is unchanged, and the oblique cut of a cylinder's fillet still fails SmSurfOfRevolution's Test #7: 3 actions of 7. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * SMLib: pin 26cc451 (batch 7: rounds past a rim, blend refusals that build, shells) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Known failing tests: the shell after a cut whose end touches an arc side builds on SMLib batch 7 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Surface fair test: the energy falls strictly, the face moves, and the edges are read after the fair Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Sketch scaling test: the first dimension sets l1 to 40 and scales both joined rectangles about the origin Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Frames tests: a pick on a moved component or an instance removes the exact round and bore volumes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Issue 1080 tests: the rib's rounds and the mitred corner chamfers and rounds have their exact volumes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Engine tests: lip_after_boss checks each lip's and groove's exact band, hole_as_deep_as_the_plate each hole's exact bore Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Robustness tests: lip_after_boss and hole_as_deep_as_the_plate live once, in the engine's tests.rs with exact volumes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Engine tests: loft_cut goes; loft_spacing's hollow elbow covers its section counts and more Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel loft test: the square-to-circle loft has the oracle's exact ruled volume, without printing Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tessellation lens test: the lens's triangles fill exactly the rhombus through its arcs' midpoints Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Pattern test: six chamfered holes take exactly five more holes' bore and chamfer rings Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel pocket floor fillet test: the corner rounds and the floor loop round add their exact volumes, by Pappus at the corners Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Shell regression: the saddle-corner shell opened on the top box's side has its exact volume Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * SMLib history test: every operand's order is the identity on its record's faces and edges Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Boolean history tests: the SMLib module's box-minus-sphere, box-minus-cylinder and box-union-box copies go; the top-level ones check more Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Modify history tests: shell, offset and thicken are one test each through the public API, with the volumes, refusals and history the SMLib copies checked Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Chamfer history test: the chamfer after each box cut is exactly one face on the painted block too Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Grid test: a pole side's face is the five triangles fanned from its one grid node, none degenerate Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel tests: the twelve ignored print-only debug tests and surveys go; coplanar_curved_booleans checks the flush-capped cylinder cuts and unions they printed Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel: the #883 board fixture generator is an example, not an ignored test Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * STEP import test: a seam sphere whose meridian stops short of the pole imports as the whole 2 mm ball Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Material tests: the nine copies in material_properties go; the persistence file checks the library copy's card and formats 20 and 21 in one loop Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Sample test: one loop checks every sample builds cleanly and without a panic; the robustness copy goes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Known failing: the non-antipodal seam sphere import, refused for a loop of no (u, v) area Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: rustfmt the board fixture example and the coplanar asserts Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the two 3871 cone cases were byte-for-byte the 258 cases; the 258 cases carry their sources Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: a volume or area can be graded as a hand-derived range where analysis only bounds it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: fillets keeps one case per regime; 17 replications of a case in the same regime go The sloped-basin chamfers and rounds at 0.5 mm rims repeat the 1 mm rim's regimes; two of the three knife-edge chamfer tips, the r1 and box r3 curvature corners, the r1 tangent corner, the 1 mm pocket-rim and hole-rim chamfers short of the floor and the r1 together-round each repeat a kept case's regime and grades. #854 moves to 851-chamfer-arc-top-edge-9-5, and the cases that cited a dropped one cite the kept one or state its formula. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: five cases outside fillets repeat a kept case's regime and go A square cut is the slanted plane's ordinary crossing; the cam's half turn is the quarter turn's contact at a symmetric angle; the r15 slab stands inside the same coincidence tolerance as the r10; the 90 degree unfold and the 40 degree flange repeat the 72 degree and 20 degree cases' formulas. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 3243 rim and tooth join graded on its volume (rim plus the trimmed tooth less their 0.01 mm overlap) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 3782 emboss on a cylinder graded on its volume, area, faces and box (the wrapped 4 x 5 badge raised 1 mm) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 3604 G2 swept-tool cut graded on a volume range (filleted box minus the swept corner section) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4505 coil joined through a cylinder wall graded on its volume, area and box (cylinder plus the wire's screw-swept segment outside r 76) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4879 window cut through a thickened spline revolve graded on a volume range and its faces Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4623 join of crossing pleated loft skins graded on its volume and box (both skins less their overlap) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 831 tapered glyph extrude graded on a volume range and box (the font's S drafted in by 10 deg) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 2357 ring of 90 cylinder segments graded on its volume and box (the segments less their 90 joint overlaps) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4542 fluted wall joined on a revolved base graded on its volume and box (the base by Pappus plus the fit-spline ring) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 1985 and 2243 STEP-export enclosures graded on their volume and box (the outline less the cavity, plus gusset and standoffs) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: both 4092 loft, ribs and pad unions graded on their volume and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 1525 graded on its volume (the convex body's exact 2 mm inward offset), faces and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 1494 graded on its volume (box and cylinder less the 1 mm-offset cavity, sharp to rounded concave edges) and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4492 graded on its box and a volume range (the face's 19 mm sweep added, within the block's sides) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 745 graded on its volume (the end moved 1 mm plus the spline boss's exact area), faces and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 4567 graded on its volume (the revolved spline less its revolved 2 mm offset), faces and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the up-down squares shell graded on its volume (the columns less the 0.346 mm-offset cavity, sharp to rounded concave edges) and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 545 graded on its volume (the frame less its 0.5 mm-offset cavity, sharp to rounded concave edges), its sealed pillar void and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the shell-again case graded on its volume (the shelled box less the 0.5 mm-offset cavity in its walls) and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the arc-sided plate shell graded on its volume (sharp to rounded at the hole's bottom), faces and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 616 graded on its volume (the lid less its 0.5 mm-offset cavity, sharp to rounded concave edges) and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 391 graded on its volume (the shelled housing, sharp to rounded at the flange, less the letters' 0.6 mm deboss) and box Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: shell/3576 was the ladder's drafted box with rounds shelled, recipe for recipe; the ladder case grades it and carries #3576 and #3573 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the two 851 chamfers of 2 graded on their volume (the cone's sweep, and its union with the front edge's prism) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the chamfered corner of the lipped shell graded on its volume (the chamfer's triangle through the wall) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the concave round into the peg's cylinder graded on a volume range (the torus it must add, the band it can't leave) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the two folded 72 degree trays graded on their volume (flat area x thickness) and the walls' reach Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the flanged rhombus graded on its volume (flat area x thickness, all four reliefs cut) and its walls' ends Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the base with two adjacent flanges and a hole graded on its volume (base, bends and panels folded) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the flange beside the ledge graded on a volume range (the flange's two readings of its length) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the two G0 window patches graded on the box the part they close keeps Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the hub's six swept grooves graded on its volume (the revolved hub less each tube's part inside it) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the cut mirrored loft graded on the box its sections pin Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the three modelled-thread joins and the fine M48 graded on their volume (the basic profile's groove, Pappus) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the oblique-cut round graded by its seams (tangent, not curvature-continuous); the flanged rhombus says what it tests (its reliefs stay apart at 60 mm) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 3841 is 168's rim touching its coin along a circle, and 4092's reduced recipe is its report less a flange clear of the failing join; the kept cases carry their sources Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the oblique-cut round keeps its old grade until the new blend algorithm lands Its seams grade needs the continuity check to skip the body the round is not on. Fillet cases wait for the new algorithm. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: 1985's enclosure is 78 x 77 (74 and 73 inside, 2 mm walls); its volume 38063.827 by hand Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the three spline walls' face counts wait for the one-wall decision; their volumes grade them Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * STEP import: a face bounded by seams alone runs its loop the other way, never turns over A loop that uses each of its edges once each way (a whole torus within its tube and ring seams) is the same set of uses run backwards, so it says nothing of the face's side. One written clockwise in (u, v) turned the face over, against its same_sense: the torus came in inside out with a warning. Such a loop is now reversed and the face keeps its side. Test: seam_only_torus_imports_as_a_whole_ring, both orders of the two seams, volume 2π²Rr². Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * STEP import: a face bounded by a slit alone is the whole of its closed surface A loop that runs out along a chain of edges and straight back (a meridian from a sphere's pole stopping short of the other, out and back) encloses no (u, v) area, yet on a closed surface it bounds all of it less a cut of none. The reader only read such a face when the slit already ran pole to pole (and moved the sphere's frame onto it only then), so the 2 mm ball whose meridian stops at 2.5 rad was refused for its empty loop. The slit is now made the face's seams, so its loop bounds the surface's whole domain: on a sphere, a revolution whose profile ends on its axis, or a spline closed round u that collapses at both ends, the slit's meridian is run on to both poles, out and back (a sphere's frame put on the slit first, whichever two points it joins); on a torus, the circle the slit lies along is closed and the other circle through its start is the second seam. The seams on a sphere are its own meridians (angle 0 on the equator), so their pcurves are exact lines on its form. Tests: non_antipodal_seam_sphere_imports_as_a_whole_ball passes (its known-failing line goes); seam_only_torus_imports_as_a_whole_ring adds a torus bounded by a slit along its tube. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: the test-peg's concave arc and front top edge rounded together stay within the body's box A new fillet case, report-fillet-concave-arc-and-front-top-edge-together-solver-residues: the reported part's bar (with the sketch solver's residues) whose sides run tangent into the cylinder, its concave arc and front top edge rounded r2 together. The plane of the front face bounds the whole body, so every blend lies within the unblended body's exact box (SMLib's tight box); graded to 4e-5, the corner patch's own tolerance. On SMLib 2fc375f the corner patch stands 0.0374 out of the front face (box y min 0.0205): listed in KNOWN_FAILING. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: the test-peg corner at r5 and r7 Two more fillet cases, the reported part's concave arc and front top edge rounded together at r5 and r7, with the same exact-box containment check (graded to 4e-5, the corner patch's tolerance). On SMLib 2fc375f the corner patch stands 0.128 (r5) and 0.230 (r7) out of the bar's front face (box y min -0.0699 and -0.1723): listed in KNOWN_FAILING. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: blends that end where their face runs tangent into another Fifteen fillet cases on the test-peg's shape with clean numbers: a bar 40 x 16 x 10 whose far end is a half disc R8, a disc R8 standing 10 on its top, joined, so the front face runs tangent into the cylinder along x = 40 and the front top edge (convex) meets the concave arc of the top tangentially there. Each blend ends on a face tangent to the one it rolls on. - Rounds: both edges together at r2 and r5; one after the other in either order at r2, and at r1.5 and r3; the front edge alone as a curvature round, whose end on the cylinder is a semicubical cusp. The containment invariant (the unblended body's exact box, to 4e-5) and G1 seams, or the analytic volume where the blend has a closed section. - Chamfers: the front edge alone and the concave arc alone (analytic volumes: the section along x up to the wall, the cone's spandrel ring clipped by the sides), both together, and one after the other (1 then 2). - STEP: the peg written to STEP and read back, its front edge rounded (analytic) and both edges rounded together. - A cone: the peg drafted 5 deg, whose front face runs tangent into a cone along a generator, its front edge alone and both edges together. The quadratures are tanh-sinh, converged to 1e-13; SMLib's own volumes of the passing analytic cases agree to 4e-9. A sphere is left out: a plane meets a sphere tangentially at a point, not along a seam, so it is not this ending. On SMLib 2fc375f eight fail, listed in KNOWN_FAILING: every chamfer that ends tangent (status 1001, SmFilletNx1Corner), the two rounds together (the corner patch 0.0374 at r2 and 0.128 at r5 out of the front face, and the rounds meeting with normals 180 degrees apart where their contact lines on the top cross), the same on the STEP-read peg (status 1001) and on the drafted peg (its corner refused as unsupported). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: fillet corners graded curvature-continuous, the default to be Six fillet cases that pick their edges with no type, so they take the fillet's default, which the owner has ruled is to be curvature-continuous (G2) at every corner, with circular rounds kept as an option. Each grades every seam of the rounds and of the corner patch G2, on one valid body: - an oblique convex corner (a block drafted 15 deg); - a four-edge and a five-edge apex corner (pyramids lofted to a point); - a pocket's concave corner; - a mixed corner (a step: one concave edge, two convex); - a corner beside a cylinder (the top corner of a half cylinder). All six fail on SMLib 2fc375f, listed in KNOWN_FAILING: today's default is the circular round, whose seams jump in curvature by 1/r. On the five-edge apex the corner patch also meets two rounds at 8.45 degrees (G0). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: the test-peg's front chamfer builds With the SMLib fork's smlib-tangent-ends (a rail's end on its side edge is the rail/edge crossing), report-peg-front-chamfer-d2 passes. Its line leaves KNOWN_FAILING, for the pin that carries that fix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: the curvature-continuous corner cases pick the curvature fillet The six corner cases added in 3a854104a took the fillet's default type, on the premise that the default would become curvature-continuous. The default stays the circular round, so each case now asks for the curvature fillet itself (type curvature: curvature-continuous sections and corner patches) and keeps its grading: every seam of the rounds and of the corner patch G2, one valid body. They are renamed from cov-fillet-g2-default-* to cov-fillet-g2-*. The oblique three-edge corner (a block drafted 15 deg) and the pocket corner pass. Four fail, as KNOWN_FAILING now says: - the corner beside a cylinder: the curvature fillet builds its sections only between planar faces; - the four- and five-edge apex corners: refused because the default setback is shorter than where the rounds' contact lines meet (3.90 and 3.51 mm from the apex); - the mixed corner: SMLib sets back a corner only where its edges are all convex or all concave. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Rig: the test-peg's concave chamfer, alone and after the front chamfer, builds With SMLib's tangent end as an event of the fillet's trace (blend-end-event 6d73e4f), the concave chamfer's rail on the cylinder ends where it crosses the seam along which the front face runs tangent into the cylinder, continued past the vertex, and its end rib on the front face is built from there. report-peg-concave-chamfer-d2 and report-peg-front-chamfer-d1-then-concave-chamfer-d2 pass and leave KNOWN_FAILING. The two chamfers together still fail, now at the mixed-convexity corner where they meet: its line says so. Rig against SMLib 0cc48bd: no area regresses (963/993 pass, 961 on a87c502), ladder 168/168, kernel lib only its listed failures. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: constant rounds of the exact classes, and a tee's round A plane cutting a cylinder or a cone at an angle, a sphere or a cone coaxial with the other face, a cone and a cylinder touching one ball, two pipes touching at a point: their rounds' centre lines are rational, so the rounds are rational surfaces of degrees fixed by the construction ((4, 2), (2, 2) revolved, (6, 2), (12, 2)). The tee's centre line is not rational; its round is graded on its volume. Volumes from the divergence theorem over the exact pieces, at rel 1e-6. The six that SMLib 0cc48bd traces are listed in KNOWN_FAILING with what they come out as. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the exact-class rounds pass on SMLib's classified exact rounds The rounds now come as the rational surfaces their classes give, closed ones as two faces split at their seams, the touching pipes' as four: one splines entry a face, each of the class's degrees. Their KNOWN_FAILING lines go. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * SMLib: pin 7ac037e (the new blend's tangent-end event, zero-speed G2 ends, and its exact-class rounds) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the fillets known-failing list is the 22 cases that fail on SMLib 7ac037e Twelve listed cases build on the new blend's end event and exact classes, or were already built on develop: they come off the list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: #316's bottom rounds as large as the wall, or larger, shell with a step wall at the opening, not refused Where the round meets the open bottom the cavity's wall steps down along the bottom's normal, so the round meets it at 90 degrees and the opening is exactly the picked face. The cases are renamed and graded on the exact volumes, and come off the shell known-failing list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Merge fixes: every crate and test target compiles on the merged tree, but for crates/geom's hlr world_state, view::bounds, home_camera and scene return Result on develop; new main code takes that with ? or session_world. New fixtures carry the spline's nurbs. ForeignCopy::of returns Result. occurrence_placement_with walks the path with its moves, since the placement index holds pending_moves only. The hlr port is separate and still to come: this commit does not compile as it stands in crates/geom/src/hlr. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Drawings hidden lines: read develop's B-rep records Edges come from the record's edge list, cut to their interval (C3::of_edge), and faces from its face list; a cylinder, cone, sphere or torus chart takes its bounds from where its NURBS form lies on its label (S3::of_face). A rigidly placed revolution has main's revolution chart; other placements stay refused. Moving a body to its centre goes through Brep::moved. Loops are read against the natural normal of the face's parameters where a chart wraps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Hidden-line fixtures: build develop's records from the fixtures' data Fixtures keep their bounded curves and surfaces and their own edge numbers; a private builder makes the canonical record, and the local prepare puts the edges back in the fixture's numbering. Assertions are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Hidden lines: tests of the bounded edges, face charts and placed revolutions Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * drawing-hlr doc: what is drawn and refused on develop's records Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * hlr tests: a placed revolution is refused when its placement is not rigid The new model has one record for main's Revolution, which was drawn, and its PlacedRevolution, which was refused. An identity placement is now the former, so this test's fixture takes a non-rigid one. The refusal it asserts is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Hidden lines: a traced intersection is drawn only where its spline lies on both surfaces A leader off either surface is refused like a curve with no spline to follow. Tests: a traced rim drawn on the circle and plane within tolerance, the same leader 1 mm off refused, and kernel bodies with arcs through the production prepare against closed forms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Hidden lines: kernel bodies through the production prepare against closed forms Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Tests from main: the world state is a Result here Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * A blend's pick measures close edges on their curves, not their polylines A polyline can be a chord off its edge, more than two edges are apart near a tangent point. A pick exactly on a ball's rim took the straight edge the rim is tangent to, and solidcore built a chamfer of that edge with a clean check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk (cherry picked from commit c786db6bf4) * Merge fixes from the first SMLib test pass Model cache key covers the crates develop's kernel adds under doc (profile, smlib, step). A piece taking a name also takes the feature that made it: SMLib lists a cut's pieces in another order, and the swap left the name on a piece of the wrong feature. A replaced analysis keeps its status slot. A command with no world picks does not place the model first, so assembly.mass_properties answers for a flattening placement. FeatureCommon loses the touching key the merge added; only the contracts that read it take it. Two of main's tests listed as failing on SMLib, with why. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Merge fixes from the ui test pass and the gates Main's thread.direction keys go with develop's thread hand, which replaced them. Vietnamese for the messages develop added while main made vi a complete catalog. CGA and 1-bit themes set develop's comb and section hatch colours. A ribbon button with a persistent effect is pressed only while its tool runs, so persistent_ribbon_pressed alone decides how its effect is shown; other analyses stay pressed while on. Two of main's ui tests listed as failing on SMLib, with why. Gates: fixed thread tables become slices, one collapsed if, rustfmt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * A silhouette takes its facing from the surface's normals A flat triangle beside the outline can tip the other way from the surface it approximates, and its edges joined the outline. On SMLib's sphere that made 192 segments instead of the equator's 64, 100 curves and 95 profiles from the tight fit of #7989. Each corner's normal is used where it is close to the triangle's own; a mesh without such normals (none, zero, not numbers, or averaged across creases) keeps the triangle's normal, as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Clippy and rustfmt on the merged tree Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk * Stepwise open checks every feature under the session's mode OpenSteps::start evaluated under the default check mode, and finish kept those results under the session's mode: an each_step or off session opened in steps recomputed nothing. start now takes the mode (the app passes its session's), and a mode that changed before finish evaluates the design again under the new one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Clippy without SMLib: the planar-sheet edge reader is built only with it Its one caller is in the smlib-only sheets module, so without the feature it was dead code and clippy -D warnings refused the kernel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * SMLib: pin d01d7b0 (the new blend's one Gⁿ section generator: the chord, circle and curvature sections, and the variable rounds as the union of their balls) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the section orders, chord, circle and curvature section, on planes and against a cylinder Eight fillet cases for the blend's cross-section by its order of contact with the faces, each graded on its analytic volume at rel 1e-7 and its exact continuity (the order, and not the next): - a box's top back edge chamfered 3 (G0), rounded r3 (G1) and curvature-rounded 3 (G2): the areas cut off the corner s^2/2, (1 - pi/4) s^2 and 113/756 s^2, the last by the default thumbweight's definition; - a pipe R10 dipping into a plate, its concave edge chamfered 2 (the chord between the contacts of the ball SMLib rolls for that setback, radius 1), rounded r2 and curvature-rounded 2, each section's added area by Green's theorem along the plate, the section and the pipe's arc; the order-2 section is built from the faces' feet of the point at distance d from both, which on the pipe are not linear in d; - a boss root curvature-rounded 2, the square corner's section revolved (Pappus); - a variable round r1 to r5 along a box edge (rel 1e-5): the balls' envelope is a circular cone, and the volume is the cone's sections integrated along the edge. Three fail today and are listed: the two curvature rounds whose faces are not a square corner of planes (SMLib's quintic blend curve, not the order-2 section: rel 6.5e-7 and 1.2e-5) and the variable round (great circles, not the envelope's: rel 4.8e-5). The other five pass on SMLib 7ac037e. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the curvature fillets' expected bodies from the order-2 section at thumbweight 0 SMLIB_BLEND_CURVATURE's section is now the order-2 G^n section at thumbweight 0. Between two planes square to each other it cuts A = 0.154192655384275 s^2 off the corner, its first moment about either face 0.0291753295725360 s^3 (Green's theorem on the section): the curvature cases built on that corner (862, 2708, every-box-edge, every-hole-top-rim, every-l-bracket, every-block-cylinder-crease, the three-edges-at-bar-corner reports, 3604's fillet) take their volumes from it by their own methods, the peg's front blend 23.3237146876 (its section along x up to the wall). Between planes the section's t^3 term vanishes (their feet are linear in the distance): the box edge case is exactly G3. The boss root is a certified fit, G3 to the plate and G2 to the wall at Continuity Analysis's tolerances: at least G2. The boss root and the pipe on the plate pass on SMLib's section and leave the known-failing list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Curvature fillets: the section's default thumbweight is equal area, so the round's volumes are the circle's On the round's rails the order-2 section takes off what the ball's circle does: (1 - pi/4) s^2 at a square corner, first moment 0.0474559669443 s^3 (w = -0.5252123889). The kernel and engine tests and the curvature rig cases take their volumes from it by their own methods; the pipe on the plate from its own wedge (70.52878 degrees, w = -0.8544103493). The G2 corner patch's seam test is listed until the corner step. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: four G2 corners wait for the corner step: their patch meets the new section's rounds G1 at one face seam Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the turn at a corner of two rounds, Mitre (the default) and Swept, at a pocket's floor and a boss's base, by exact volumes A round's spandrel A = (1 - pi/4) r^2 and its first moment about its wall M = r^3 (5/6 - pi/4): Mitre adds L A -+ 2 M per edge (cut at, or run on to, the corners' bisector planes), Swept turns the section about a convex corner's edge, (pi/2) M a corner, and refuses a concave corner rounded less than the ball. The pocket's tangent chain round its R3 corners is a torus each. Graded to 1e-7, where Mitre and Swept differ by 6.6e-6. The Swept cases are listed until solid.fillet takes a turn. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: a junction family: oblique wedges 30 to 150 degrees rounded and chamfered (exact), bosses upright and tilted, pipe tees and a Y junction Four are listed with their causes: the equal-pipe tee (its exact conic-pair rounds meet at the ellipses' crossings in a corner the old corner code cannot join), the tilted bosses (1001, before the blend rework too) and the Y junction (refused for room at its triple points). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Variable rounds: graded by the union of their balls (their envelope), not the balls' great circles The smlib crate's laws and ladder 005, 006, 007 and 012 take the volumes the balls' envelope removes; the law with a corner is its own test, listed as failing until the corner step. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel tests: variable rounds graded by the union of their balls, the removed volume to 1e-4 of itself removed_by_balls integrates, in each plane square to a right-angled edge, the corner the union of the balls leaves (by rays from the edge, the least entry over the balls), cut to the body's section. The law with a corner through a middle point is its own test, listed as failing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel tests: a spline radius whose balls fold over one another at its peak is refused Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: the variable round on its cone passes (the round is the balls' envelope) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: three rounds of different radii at a corner listed: the corner's transition kinks with the balls' touch circles Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Ladder: the variable rounds graded to 1e-6 by the union of their balls; 012 by its law going on past the edge At the default 1e-3 the great circles' volumes (4e-6 off) passed too. SMLib builds each within 1.6e-7. The golden takes the new volumes and areas; counts unchanged. The G2 corner test listed as failing passes on SMLib's step 3 and leaves the list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Reference tests: the variable rounds 77, 78 and 81 pass on SMLib d01d7b0; their known-failure marks come off The new section builds their edges on the surfaces, so STEP export no longer finds them 4.6e-5 to 6.1e-5 off. develop's Reference tests (60393a718) report all three as passing while marked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * STEP import: a ball's halves whose seams are off each other's quarter lines each form within one turn A sphere split into two halves along a circle about its axis, each half covering a pole with no seam, gets a seam per half from the first vertex of its loop to the pole. The circles between the halves group their frames so they turn together, and when the two seams are not a whole number of quarters apart no one turn fits both: the group kept its frames, a half's form ran past one turn, SMLib's trim (SMLib and solidcore alike) across the form's end crossed the face, and the mesh folded over the ball (a rotor's ball showed torn; its half had 196 times its area in triangles). When no one turn fits the group, each spilling face is now turned on its own to start on a quarter line. On the rotor file this also clears three other faces that were filled leniently and a 0.076 mm edge gap; regression test in step_in/tests.rs with the area and volume of each half. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz (cherry picked from commit b3188e005d427043b918267449c2336a1777e54f) * SMLib: pin 5e8c9c1 (the new blend's corners: Ball and End/Join; exact fold and room checks with fit sizes; overflow in place; the round as its definition) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel tests: a law's dip shows its corner ball's sphere, a peak's two rounds cross (the reasons had them swapped) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Reference tests: the variable rounds 77, 78, 80 and 81 expect the union of their balls A variable round is the envelope of the balls rolled along the edge, which takes less than a quarter round in each section. The expectations are now that union, the law continued past the edge's ends along its end slopes, integrated by Gauss-Legendre panels in x and t; 2, 4 and 8 panels agree to 1e-9 of the body's values, and 77's removed volume matches a brute-force union of balls to 2.5e-10. The nearest-ball search now scans the balls the ray meets around ball x (|x - s| < r(s) sqrt(sin 2t)) on their own, which near the faces and where 78's radius closes to 0 are narrower than the global scan's step. Regenerating keeps each case's known_failure. 79, a constant radius, is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Known failing: the law corners' kernel and crate tests and rig 1207 pass on SMLib 48ea616 SMLib builds a variable round's law corners as its balls' union (the corner ball's zone at a dip, the sides' crossing at a peak): the kernel's corner through a middle point (39.5410) and the crate's 4 -> 2 -> 4 law (39.5421) pass. Rig 1207 (the bar's top edge rounded after the boss's arc, r0.5) builds and grades on the same SMLib; it failed on c820346. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Kernel rig: every fillet and chamfer case rounds its tangent chain The owner's ruling of 2026-11-01: the rig and the ladder round with tangent_chain true, how a user's default pick behaves. The 38 fillets-area recipes and the ladder's 07-fillets/016 and 018 that passed false now pass true. The shell recipes keep theirs: a shell's tangent_chain is its open-face chain, a different feature. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the partial-selection cases kept as -partial-chain copies, tangent chain off Where a case's point is one edge of a tangent chain rounded alone, a copy keeps tangent_chain false as its own case (SMLib rounds exactly the picked edges, ending at the smooth vertex); their expectations stay as they were, to be re-derived: - fillets/1207-fillet-box-end-edge-into-unblended-round-partial-chain; - fillets/every-fillet-after-fillet-curvature-front-then-side-r3-partial-chain; - fillets/1207-fillet-bar-top-edge-after-boss-arc-round-partial-chain, renamed from ...-no-tangent-chain: with the chain on it is exactly 1207-fillet-bar-top-edge-after-boss-arc-round, which the rig already has; - ladder/07-fillets/020 and 021, the r5/r3/r7 and r5/r3/r2 corners (016 and 018) with the r3 on its edge alone: with the chain on, the r3 runs on along the r5 round's end arc and down the vertical edge the third round was to take. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the concave arc between the block's tangent sides kept with tangent chain off fillets/every-block-cylinder-tangent-concave-arc-r2-partial-chain: the pick takes one piece of the concave half circle, which SMLib splits; with the chain off its other pieces are left out, and the blend is refused at the piece's end (the base gate's outcome). With the chain on the case rounds the whole half circle. The copy keeps its expectation, to be re-derived. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: two chains that now build graded by their exact volumes With the tangent chain on, two cases round more than the edge they pick, and their old expectations were the single edge's: - 1207-fillet-box-end-edge-into-unblended-round: the r1 chain is the end face's top edge, the r3 round's end arc and the back upright; 34 A + (pi/2) A (3 - c) by Pappus on the arc: V = 7953.139216 (it built 7953.139216, the old 7957.505 passed only inside 1e-3), 10 faces. - 851-fillet-top-front-then-front-left-upright: the upright's chain runs up the first round's end arc on x = 0 and along the left top edge, so the corner becomes the R2 ball's eighth: V0 less the first round's spandrel to the wall (35.344727) less 27 (4 - pi) + 2 pi/3: V = 9530.777979 (built 9530.777987), 10 faces. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: a curvature chain round a round's end refused for its size; the concave half circle builds - every-fillet-after-fillet-curvature-front-then-side-r3: the side edge's chain runs round the first curvature round's end curve, whose radius of curvature has a weighted mean of 3 (its setback) and is unbounded at the ends, so somewhere below 3: the size-3 blend's contact line folds back on itself. Refused, "larger than the faces beside its edges allow", as ladder 07-fillets/016's r7 on the r5 arc. (It was solid or refused for running on tangentially.) - every-block-cylinder-tangent-concave-arc-r2-no-tangent-chain: the chain takes every piece of the half circle and ends at the convex edges it runs on into; it builds the analytic 19091.9620, so the outcome is solid (the refusal alternative was the chain-off one's). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Known failing: two 851 chains whose corner piece is a ball of tube-centre radius 0 851-fillet-arc-then-top-front and 851-fillet-top-front-then-upright: with the tangent chain on, each R2 chain runs along the end curve of an R2 round on a curved face (the arc round's end on the front face; the first round's end on the wall), where the rolling ball sits on that round's own centre line, so the piece is the ball about (39.2538, -19, 8): the three-edge rolling-ball corner. SMLib fails with status 1001; the same piece on a plane end arc builds (front-left upright). Expectations unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Ladder: 016 and 018 refused, their r3 chain takes the vertical edge; 020 and 021 recorded With the tangent chain on, 016's and 018's r3 runs on along the r5 round's end arc and down the vertical edge, so the third pick (60, 40, 8) is 3 from both of that round's contact lines and names no edge: refused, asking for a point along one edge. The corners they were made for are 020 and 021 (the r3 alone), whose golden entries are 016's and 018's (021 measured on f12a101). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel tests: three rounds at a box corner end on one rational patch on the ball's sphere, not an analytic sphere SMLib's Ball corner is always the rational patch exactly on the sphere (owner ruling, blend design §23), so the corner counts as an 'other' face beside the three cylinders and six planes. The removed volume still checks the corner against r³ − πr³/6. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the curvature round on a pipe on a plate is listed: a seam grades G3 where exactly G2 is wanted Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel tests: the box-and-fillet wire fixture records the round's cylinder frame as SMLib now keeps it The round's cylinder keeps the frame it was made on when it is turned (SMLib's SwapUV no longer re-derives it): its origin sits at x = −20 on the same axis line, (x, 2, 8) along x, radius 2. Same cylinder; one number in the record moves. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Known failing: two kernel tests' reasons as they fail on SMLib 5e8c9c1 (a partial selection running into an unblended tangent edge) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: two curvature rounds get 600 s, past the 180 s default, while G2 certification is slow (tangency-labs/smlib#96) On the CI runners the boss root and the hole rim, both size-2/size-1 curvature rounds, build correctly but take more than 180 s: the order-2 section's span certificate and the round's definition are evaluated station by station. The per-case limit is the one the thread cases use. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Lid ring sketch test: find the ring under the pick, not by main's kernel's name On SMLib the lip join's exact history names the lid underside's ring a piece of the lid's own start (F14:start#[...]), as the naming rule says for a face that came from the feature's input; main's kernel named it after the case's top it rests on (F2:top). The test looked the ring up by that name and so stopped before the attachment it guards. It now takes the underside piece under the pick point, which the cap certificate attaches on either kernel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Viewport culling test: each box's triangles from its mesh, not 12 SMLib meshes a 10 mm box in 108 triangles, so the hard-coded 12 a box stopped the test before it reached the culling. The expected counts are now each body's span in the scene. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Timeline chip test: a fillet that really reduces The R20 fillet with fit reduce on one top edge of a 10 mm box builds on SMLib without a reduced-radius warning, so the fixture had no warned feature. It now rounds the four vertical edges at R6, reduced to the full round (5), as the copy-warning test beside it does, and checks the warning says so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Oracle: 34-chamfer-then-fillet and 35-fillet-curved-curved pass on SMLib 5e8c9c1 (their STEP edges are on their surfaces) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Known-failing: the shell of a fully rounded box opened at one face fails on SMLib 5e8c9c1 (tangency-labs/smlib#102) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Known-failing: the action matrix's oblique cylinder cut fillet passes on SMLib 5e8c9c1; two shells still fail Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the boss root's curvature round gets the rig's 1800 s cap: on the CI runners, 8 cases at a time, its G2 certification passed 600 s (tangency-labs/smlib#96) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: a case's continuity can ask for an order per seam (seams: [{order, edges, exact}]) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the pipe on a plate's curvature round meets the plate G2 and the pipe G3, 40307.8856312 (option B's order-2 jets, tangency-labs/solidcraft#10845) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Edge names: a seam names its one face once; the curve-id test reads every edge kernel-neutrally A seam's two sides are the same face, and edge names list each face an edge bounds once, so SMLib's extruded circle names its side's seam F2:side:c1, with no separator. The name grammar now says one face also means a seam. The #5858 test no longer counts one '|' an edge: every part of every edge name is a whole face name of the edge, one per face it bounds, two for the rims and one only for the side's seam (checked to run bottom to top on the circle). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * rustfmt on the merged tree Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Known failing on SMLib: two of main's new tests assume truck's box mesh and fillet torus Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * SMLib: pin f916a8d (a round on a definition face is its definition; the G1 setback fill certified convex, setbacks too short refused naming the least; the G2 certificate halves a span no level can certify at once) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Fillet: a setback too short for its corner is refused naming the least that builds (smlib_blend_fit_size) SMLib's setback corner takes a G1 fill only once certified convex, and refuses a setback too short for that as SMLIB_ERR_NO_ROOM with SMLIB_FIT_SETBACK_AT_LEAST, the smallest setback that builds. The kernel reads it (solidcraft-smlib binds smlib_blend_fit_size) and names it; the Fillet dialog says it in plain words. Other room refusals keep their words. The r5 box corner set back 5.5 is refused naming 5.962, which builds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel tests: three rounds of different radii at a corner meet in SMLib's setback corner Each round runs whole to its section square to its edge at its setback (the owner's rule, at least 1.5 r, scaled to the least at which the G1 fill is certified convex), and the hole is the setback split: one patch per round and the triangle in three quadrilaterals, 15 faces, G1. Outside the box the sections span the body is the three strips', so its volume is theirs within that box's. A later r3 round at the mitred corner makes the body all three at once make (7928.142563938, 15 faces), as the engine and the model-cache tests have it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel tests: SMLib's own corner between curvature rounds is curvature continuous, as the G2 patch is Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the boss root's and the hole rim's curvature rounds take the default timeout again (37 s and 34 s on the box under the rig's parallel load, tangency-labs/smlib#96) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Agents: model decisions use exact geometry; a mesh is for display, export, previews and mesh bodies Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * xtask: mesh-decisions, model decisions use exact geometry; today's 176 mesh decision sites are listed and the list only shrinks Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Sheet metal: cuts and holes pass over sheets and bends by their exact boxes, never a mesh's A primitive cut skips the sheets kernel::apart (exact bounds grown by the record tolerance) finds clear of its tool; the bend check leaves the clear case to kernel::boolean, which answers it from the same exact boxes with no intersection work. The mesh-box helpers are gone, and their four lines leave xtask/mesh-decisions.txt (172 sites left). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Agents: AGENTS.md loses a stray merge-conflict marker line at its end Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Locales: Vietnamese for the setback-too-short refusal, now that vi is a complete catalog Main made vi a complete catalog; develop's new message (ui.fillet_error_setback_short) had no vi entry, so every_complete_catalog_carries_every_english_message failed on the merged tree. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: exact volumes for 1213's bent-tube round and 4782's bar round, rel 1e-6 1213: the loft is a cubic skin through the five sections (ellipses between them), not a torus; its volume 131601.597487935 by quadrature less the exact rolling-ball removal 233.662461919 gives 131367.935026 (was a Pappus estimate on a torus, 131360.148, at rel 5e-4). 4782: the section's area in closed form, 25 pi/3 - 5 sqrt(75) + 25, so V = 630.2934873 (was a grid estimate, 630.293125). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Kernel rig: the boss root's and the hole rim's curvature rounds take 600 s again: under CI's parallel load they pass the 180 s default (develop 820b7b6) They take 37 s and 34 s alone on the box, but CI runs 8 cases at once on slower runners. Their G2 certificate cost is the open item (tangency-labs/smlib#106, moved to solidcore#2344). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * After the merge: clippy's auto-deref, and the mesh-decisions list for the merged tree Develop's list was taken on develop alone. Main's code (tap-marking reach, cut and hole box checks, join pieces, print faces, placed measuring, selection items, imported mesh payloads) and the branch's own exact_edges and named_vertex use meshes too; three listed functions were renamed by main (face_outline and plate_recesses into FaceSlice, paste into build). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * After the merge: main's new tests on the SMLib kernel - Cut To the far side of a curved wall (#8634): the tool stops past the first crossing of the face ahead of the profile; SMLib's whole bore is one face that a line crosses twice, so the single-crossing rule found none and the cut took nothing. - Clearing view analyses goes through refresh_display, as main's #10687 made the others, so an open feature editor keeps OK and Cancel after Zebra. - vi, a complete catalog on main, gets the setback-too-short message. - fillets/KNOWN_FAILING: 4782's cause is now its continuity check (SMLib f916a8d builds the expected volume). - Known failing, as main's tests assume truck: the spline wall's spans as one mesh patch, a hole touching an edge at a point leaving one body, and a copy of a copy's triangles matching a fresh mesh. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEu4Lr3moCCisdZShKz * Twisted sweep: circles about a straight path are exact cylinders (solidcore#2184) A twist about a straight path maps a profile circle centred on the path's line onto itself, so its swept wall is exactly the cylinder. The skin through the stations stayed within 3.9e-9 of it (6.6e-9 on the outer wall), and a boolean with another body on that cylinder failed with status 1001 (solidcore#2184; the kernel's handling of a B-spline face lying on a cylinder stays open there). sweep_controlled now builds those walls exactly when the path is lines along the profile's normal and there is no end scale or rails: a profile whose every loop is such a circle is swept untwisted, and such holes in another outer loop are cut as exact cylinders from the skinned sweep of the rest. Other loops, and an axis-centred arc inside a loop of other curves, are skinned as before; a failed cut falls back to skinning all. Regression test in smlib_sweeps_tests.rs: #2184's tubes joined at 10, 16, 18, 20 and 30 degrees give one closed body of 11.5625 pi with cylinder walls; a twisted hexagon with the bore keeps a cylinder bore. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdcgEtwSrdwZxqTQp5MfnU * After the merge: a hole that misses is found by exact boxes; a face is a one-face patch; main's mesh-box helpers gone - `hole_misses` (main's #10701, through brett's branch) decided from the targets' mesh boxes. It now uses their exact boxes (`Body::exact_bounds`). An unknown box still leaves the hole not known to miss. - With #10303's two shortcuts and `hole_misses` off the mesh, `body_box`, `mesh_box` and `padded_box` have no caller left, and are deleted. - `project`'s intersection link passes its one face to `meeting_edges` as a one-element patch. This branch picks one face, not #9009's mesh patch. - xtask/mesh-decisions.txt drops the six sites that no longer use a mesh here: `apply_traced_with`, `cut_end_past_face`, `beyond_cylinder_reach`, `hole_misses`, `body_box`/`mesh_box`/`padded_box`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * After the merge: split_move's Result reaches its callers; to_local's duplicated move check goes `frames::split_move` returns a Result on this branch: an unplaceable model is an error, not a silent no-split. - Move/Copy of a component (main's #9914) propagates it, as its other calls do. - `to_local` had the solid.move check twice after the merge (brett's Option one and ours). Ours stays, after the no-picks/not-placed return. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * After the merge: main's two new tests take world_state's Result, as the rest of their files do Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Native B-rep: a ball patch is its own surface kind, read from and written to SMLib's flat kind 6 SMLib's flat arrays now carry the corner of three equal rounds as `SURFACE_BALL_PATCH` (kind 6): its net as a NURBS face's block, with its sphere's centre and radius as its definition (ids 36 and 166). The record reads it as `ball_patch {center, radius}`, a label like the analytic kinds, with the net as its `nurbs`. A plain sphere with a form won't do: the net is not a piece of SMLib's sphere NURBS, so SMLib's `IsNurbSurfaceSphere` would refuse it. Written back, a ball patch is kind 6 with the same definition, which SMLib takes once its net is certified on that sphere. Elsewhere: - Offsets classify it as its sphere, so its offsets stay exact and collapse at the centre. - Face kinds count it as a sphere: fillet_three_edges_at_a_corner's corner is now `sphere`, no longer `other`. - STEP, which has no ball-patch entity, gets the net as the face's B-spline surface, pcurves included. - Iso curves and SSI of the label are refused; the face's form is what evaluates. Test: a_rounded_cubes_ball_patches_go_round_with_their_spheres. The cube's eight corners are ball patches about the corners pulled in by r. Points of each patch lie on its sphere to 1e-12. The patches are kind 6 again after import, with the same definitions bit for bit, and the closed-form volume holds. Format: pending/ball-patch-faces.rs. Docs: docs/native-brep.md and the rig README's `surface_types` (`ball_patch`). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * SMLib: pin v1.1.0-alpha (a18bbe5): the generic blend's step-4 corners, the Ball's sphere patch through the flat arrays, all-target CI Since f916a8d: - #120: every target again, plus the warnings fix; - #121: the Ball's patch as flat kind 6 with its sphere, read by the previous commit; - #122: tests gated on counts; - #123: the Mixed corner; - #124: the End at a smooth vertex; - #125: four or more rounds, and open setbacks; - #126: the equal-area thumbweight guard; - #127: the trunk merge. The SMLIB_PREBUILT checksums are from the release prebuilt-a18bbe5…, written by `scripts/fetch-smlib.sh --pin`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * smlib export tests: rustfmt's line for the rounded cube's edge midpoints Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: the fillet and ladder results on SMLib v1.1.0-alpha, the new failures recorded with their reasons Fixed (off the known-failing list): the Mixed corner's peg cases and the concave arc with the front top edge (smlib #123), and the 40° boss junction (smlib #124). Eight cases in all. New failures, recorded as they are, each with its reason. They passed on f916a8d. - **Six cases grade a blend seam G0 where G1 (or G2) is wanted,** at the end of the round's contact seam, after smlib #124's End at a smooth vertex. Two of them also shift in volume. - **Four cases come back unsupported** after smlib #125, which leaves setbacks to the Setback's corners only. - **Ladder 07/012** makes 9 faces, 20 edges and 13 vertices, where its golden had 8, 18 and 12. Its golden entry is the new result, with the reason added. Whether each change is by design or a defect is being established. A defect is fixed in solidcore, where the End and the Setback are being brought over (#2364, #2365), not in the frozen SMLib. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel ladder: 07/021 and 06/018 recorded as they are on SMLib v1.1.0-alpha, each with its reason Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel ladder: a golden case marked unstable is gated on its status, and 06/018 is marked On SMLib v1.1.0-alpha, 06/018 makes 597 or 594 edges from the same input: the union's post-process keeps pointers to edges it has deleted. A golden entry's `unstable` reason makes the gate compare that case's status only and name it in its output; recording keeps the reason, and only an edit of the golden removes it. v1.1.0-alpha.1 fixes the cause and removes the mark. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * After the merge with main: its new code on develop's exact bounds, types and thread fields - The sheet cut's cull (#10301) and the tapped wall's (#10227) use each body's exact box (`exact_box`), not its display mesh. - model.threads replies with develop's thread fields: form, hand (right, left or both) and starts. - surface.boundary's schema checks a network curve's continuity as the handler does, and words a list entry's error as it does. - Main's new tests take develop's Hole fields and world_state's Result. - mesh-decisions: contact_sweep's triangle check is now `depth` (main split `hits`). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Known failing: the 14 cargo tests SMLib v1.1.0-alpha fails, with what each sees; two cases that pass now Develop's CI after the a18bbe5 pin (run 41522001173) fails 14 tests that passed on f916a8d, and passes two listed ones. Each new line says what the test sees on v1.1.0-alpha; v1.1.0-alpha.1 fixes the setback hole's cause. shell_tangent_chain_that_opens_every_face_explains_how_to_keep_walls and oracle 37-pyramid-apex-blend pass and leave their lists. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Cargo.lock: develop's profile, smlib and step crates at main's 0.30.1 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: main's six new sketch-only commands are exempt from a kernel case sketch.construction_line (and its horizontal and vertical forms) and sketch.spline.insert_point, remove_point and reverse change only the 2D sketch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Cuts leave the bodies their tools can't reach, by exact boxes (#10225 on exact geometry) - The per-target cut loop skips a body whose exact box lies clear of every tool's, as main's version did with mesh boxes. The sheet culls (#10226, #10301) and this one now leave the far sheets and bodies alone: a_cut_leaves_bodies_it_cannot_reach_as_they_were passes and leaves the known-failing list. - a_cut_still_runs_where_its_tool_touches_grazes_or_meets_a_curved_face: a tool 0.5 µm clear of the block is now left out (exact boxes; 0.5 µm is far past the bodies' tolerances); touching and 0.1 mm in still cut. - Known failing, with reasons: main's edge lookup by a stored point (#11286, on the display mesh) is not taken; SMLib refuses the wrong-way chamfer for its tangent chain first. - EXEMPT: main's eight new sketch-only commands. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: main's new view, rendering, appearance and settings commands are exempt from a case 62 of the commands main added change no geometry: the view and render panes, rendering lights and results, appearance tools, settings profiles, point clouds (drawn as points, never a body), the selection, two sketch edits, component links and History bar visibility, edit.repeat, timeline.play, inspect.compare_picture (a picture against the outline), and component.paste_from_design, which pastes the app's cross-window clipboard that no command fills. Each joins EXEMPT's first section under its family's reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: construct.plane.axis_point gets construction cases The plane through a box edge and its far corner, graded against its closed-form normal (0,-2,3)/sqrt(13) through the origin, and the refusal of a point on the axis. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: assembly cases for mass properties, align, find limits and moving items between parts - assembly.mass_properties: two boxes (2 g/cm3) in a rigid group: mass 0.006 kg, centre (18.333,5,5), inertia diag(0.1, 1.0333, 1.0333) kg mm2 by the parallel-axis theorem. - occurrence.align: a block's end face onto a base's top face: a quarter turn about y, centre (70,20,20), box (65,15,10)-(75,25,30). - joint.find_limits: a slider between two stops: min -20, max 10 mm. - component.move_features, browser.reparent and component.move_sketches.to_parts: items moved into a turned and moved part keep their world place (volumes, centres and boxes by hand). The mass case assigns a material it creates, so material.create and material.assign leave EXEMPT. PATHS names the new command modules. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ * Kernel rig: export and print face cases in the import area - file.export_step, export_stl, export_3mf, export_obj: a 30x20x10 box written and read back (the meshes converted to a solid): V 6000, A 2200, 6 faces, box (5,-10,0)-(35,10,10). - file.export_urdf: a hinged arm on a grounded base: 3 links, 2 joints, and the base's mesh, written in metres, reads back as the 1 x 0.5 x 0.2 box (V 0.1, A 1.6). - body.print_face: a cylinder's flat end is accepted, its side refused. PATHS adds the URDF writer and the print face modules. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ --------- Co-authored-by: jyviko <2501648+jyviko@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: brett19 <brett19@gmail.com>	2026-11-02 22:53:32 +00:00
Colin Faulkingham	c4808e4715	MCP: clean up empty scratch folders on shutdown (#7836) (#7929) ... * claim: #7836 * fix(mcp): remove empty scratch directories on command exit	2026-11-02 13:57:48 +00:00
bherbruck	21fc384e40	Control channel: a new connection has five seconds to show its token (#10961) ... A client could connect and send nothing, or only blank lines, and hold one of the 16 connection seats for as long as it liked. All reads before the token now share one five-second deadline; the connection is then closed without a reply. An authenticated connection may idle as before. `solidcraft-cli mcp --connect` used to open a connection at start and hold it until the first tool call. It now only checks that the app is there, and the first call connects. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-02 04:23:23 +00:00
Dahak Builds	251573a5a4	MCP: compare the model with a reference picture (#1486) (#6416) ... * claim: #1486 * Compare picture: overlap and edge offsets of the model against a reference picture (#1486) inspect.compare_picture lays the model's silhouette over the part found in a PNG or JPEG and slides it to the best overlap: overlap (0..1), the model's edges against the picture's in mm at nine stations, and an overlay PNG. The MCP tool compare_picture runs it and hands the overlay back as an image block. inspect.silhouette grows a reusable silhouette::outline for the model side. * chore: re-trigger checks (defaults line already present in PR body) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n: carry the Compare Picture label in Arabic, Hebrew and Vietnamese too The complete-catalog guard (every_complete_catalog_carries_every_english_message) failed because the pending file covered only en/ja/zh; ar, he and vi are complete catalogs and need the key as well. * Compare picture: one uniform scale, capped fit, sturdier part finding Review on #6416: fit no longer stretches the axes apart (width is the default, both scales uniformly by width and reports aspect_mismatch); the fitted model takes the same MAX_GRID cap as the picture; the border flood seeds only from border pixels near the border's main colour, reads alpha, retries at a stricter step, and says which case failed; the slide searches the whole placement range instead of a tenth around the centre; the model's holes get the picture's fill rule; crop becomes crop_px / crop_fraction with explicit units. Pins #1486's bracket (overlap 0.865, bottom -10 mm at the upright) and adds a regression test per problem. * Compare picture: alpha only for a see-through border, part_fills_crop, outline-only wording Review re-test on #6416: one translucent backdrop pixel no longer switches the read to alpha — alpha decides only when most of the border is see-through, and any ink is then part, so a part drawn at alpha 100 survives; part_fills_crop: true takes the crop box as the part itself, for one view cropped tight off a board where the part takes most of the border and the flood would keep the backdrop strip instead; a third backdrop pass compares each pixel to the border's main colour, so a white part on (245, 245, 245) JPEG at quality 75 separates; the command, tool and docs descriptions now say the compare is outline only: holes are not compared. A banded light backdrop stays a follow-up. A test per case. * MCP compare: format the picture tests Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Dahak Builds <dahakbuilds@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: bherbruck <brennen.herbruck@gmail.com>	2026-11-01 18:30:18 +00:00
Dahak Builds	176c22acaa	MCP: explain when an unknown command id is actually an MCP tool name (#10678) (#10680) ... * claim: #10678 * MCP: explain when an unknown command id is actually an MCP tool name --------- Co-authored-by: Dahak Builds <dahakbuilds@users.noreply.github.com>	2026-11-01 15:36:04 +00:00
NOWN-DEV	a69a7c6ffe	Inspect: measure names_only lists every world body without measuring (#10402) ... A caller that only needs the bodies' names (assembly occurrences included, e.g. "Body2 (Part:2)") had to measure every body, or read document.inspect, which lists definition bodies only. `inspect.measure {names_only: true}` returns each world body's name and its definition's name, honouring the `bodies` filter; an unknown name is refused before anything is measured. The MCP `measure` tool passes it through, directly and as a batch step; `summary` leaves such a list as it is, since there is nothing to narrow. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-01 02:12:23 +00:00
rvmzym5xv8-star	0fb2e9b06b	MCP batch: refuse a command entry with an unknown key (#7854) (#7865) ... * claim: #7854 * MCP batch: refuse a step with an unknown key (#7854) A step's parameters under another key (`args`) were dropped and the command ran without them. The batch is now refused before its first step, naming the key. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * MCP batch: a step carrying `expect` is refused, saying it is the batch's argument #9904 gave batch an `expect` argument and tested that a step carrying one runs with nothing checked. That is the silent drop this branch refuses: the step is now refused before it runs, and the error says `expect` belongs to the batch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-31 16:26:23 +00:00
froglemonade2	e2a7a45c44	MCP: batch and execute take expect {volume, bodies, bbox} and flag a mismatch (refs #3380) (#9904) ... * MCP: batch and execute take expect {volume, bodies, bbox} and flag a mismatch (refs #3380) An optional `expect` argument on the `batch` and `execute` tools: the volume (with a relative `tol`, default 0.002), body count and bounding box (0.05 mm) the agent computed before building. Once the call has gone through the server measures the design as the `measure` tool does and the reply gains `expectation: {ok, measured, expected, mismatch}`. A mismatch flags the tool result `isError` with the mismatch text first; the design is kept as built. A malformed `expect` is refused before anything runs. Without `expect` nothing changes, and a batch step carrying one is a step with a stray key. In 29 logged agent sessions every agent computed these numbers beforehand and then spent a `measure` call plus a comparison by hand after every stage; one missed a 0.25 mm skin until it compared. Volume and body count are kernel-independent checks. Refs #3380 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * MCP expect: filter then map for the bbox coordinates that are off (clippy) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * MCP: expect's coordinate text helper no longer shares a name with the JSON reader Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> Co-authored-by: bherbruck <tenbee91@gmail.com>	2026-10-31 09:48:08 +00:00
froglemonade2	9b31d29443	MCP: server instructions that say how to plan, build and verify (refs #3380) (#9903) ... The `initialize` instructions were one paragraph of command shapes. Replace them with version-neutral guidance: read `skill_reference solidcraft-modeling` first, plan the numbers, build in a few `batch` calls, the primitive routes and the fillet-shell-inside-holes order, what follows a parameter, `measure` after each stage with a coalesced parameter check, and `timeline.edit` / `parameters.change` / `edit.checkpoint` to fix instead of rebuilding. The Assistant's system note gets the same pointer; docs/mcp.md says so. `instructions_name_only_real_tools` now checks the command ids as well as the tools, and `instructions_recipe_builds_a_parametric_shelled_box` builds a part the way the instructions describe and checks its volume, axes and parameters. Refs #3380 Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-31 09:09:53 +00:00
froglemonade2	e16647a63f	MCP: measure summary and body_topology faces: cylinders for small verification replies (refs #3380) (#9853) ... * MCP: measure summary and body_topology faces: cylinders for small verification replies (refs #3380) `measure {"summary": true}` replies one short object per body (name, volume_mm3, bbox, faces, closed) with body_count and total.volume_mm3, as a tool and as a batch step. `body_topology {"faces": "cylinders"}` replies only the cylindrical faces, the kernel's split halves merged by radius and axis line into {radius, origin, axis, extent, names}, and no edges. Both defaults are unchanged. The merge uses only what model.faces and model.edges already reply. Measured on a 13-feature enclosure, body_topology is 74 KB and measure 1.1 KB per body; agents filter them with scripts, and seven of 29 benchmark runs asked for exactly a cylinders-only listing. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * MCP: keep body_topology's cylinder merge next to check_parameters' without a name clash Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> Co-authored-by: bherbruck <tenbee91@gmail.com>	2026-10-31 08:56:37 +00:00
froglemonade2	c528964363	MCP: check_parameters tries parameter values and puts the design back (refs #3380) (#9910) ... A new tool that checkpoints the design, sets every value in one parameters.change, reports measure, errors and cylinder axes, and restores the checkpoint, so the loop set_parameter / measure / body_topology / set back costs one call and one rebuild. Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-31 08:24:41 +00:00
Rick Morgans	66bd64cc5e	Engine: one contract check for a call, used by the preflight, the bridge and the app (#9339) ... `schema::issues(id, params)` looks up the command's typed contract and lists what is wrong with the parameters (none without a contract or for an unknown id). The batch preflight, the MCP bridge's pre-send check and the app's check of a design-switching command each did that lookup themselves; they now call it. No behaviour change. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-30 10:21:06 +00:00
Rick Morgans	92af4a21c8	Control channel: a per-request param_check level, applied and confirmed by the app (#9184) (#9185) ... * claim: #9184 * Control channel: a request's own param_check level, applied and confirmed by the app (#9184) `engine.execute`, `engine.batch` and `engine.script` take an optional `param_check: "off"|"warn"|"strict"` in their params. The app runs the request at that level through the same `run_checked` path and batch preflight a headless session uses, puts its own level back, and every reply says the level it ran at as `param_check` beside `ok`. A command that switches designs keeps the app's level; any other word is refused. Readings and exports answered on a copy off the window thread keep the level too. `control.capabilities`, answered at once on the control-server thread, lists what the channel does beyond the methods every version has: `{"param_check": ["off", "warn", "strict"]}`. An older app answers "unknown method". The MCP bridge asks it once per connection. When the app lists the level, every call and batch goes with it and the app checks against its own commands; otherwise the bridge checks before sending, as #9073 does. At strict, a reply that doesn't say the app checked the call is an error, and the next calls are checked by the bridge. Also: `add_param_warnings` takes the reply by `&mut`, and `with_param_check` sits beside `Remote::new`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Control channel: a design-switching command is checked at the request's level Review fixes for #9184. `component.edit_in_place`, `component.finish_edit`, `view.next_tab` and `view.previous_tab` ran at the app's own level and echoed `off`, so a misspelt call went through at strict. They now have their parameters checked at the request's level before they run (and still run at the app's own level, as each design keeps its own), and the reply echoes the requested level. The MCP bridge at strict now requires the echo to match its level, not just to be there. `param_check` is read only by `engine.execute`, `engine.batch` and `engine.script`; other methods ignore it. The off-thread test now shows the design change computing off the window thread before it is refused. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-30 07:24:41 +00:00
Rick Morgans	4a781b8cd8	MCP: --param-check checks calls to the running app (#9072) (#9073) ... * claim: #9072 * MCP: --param-check checks calls to the running app (#9072) `mcp --connect` (and `mcp` once it bridges to an app) took `--param-check` and forwarded every call unchecked, while the app's own session is always off. `Remote` now checks each `engine.execute` and `engine.batch` against this server's command contracts before sending: `strict` refuses a call, or a batch with such a step, without sending anything, and `warn` adds `param_warnings` to the app's reply (each step's result in a batch). A command with no contract here goes to the app unchecked. `Auto` carries the headless session's level over when it bridges to a late app. `batch_preflight::contracts` is the contract half of the existing preflight, for a runner in another process. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-30 00:33:42 +00:00
Christian Hammacher	aae2c5e417	Assemblies: edit a linked component in place, with the assembly around it (#7672) (#7819) ... * Links: update linked designs that changed while the assembly's tab was away A design coming back to its tab compares the modification time and size of its linked design files with what they were when it went to the background, and runs Update Links on the worker thread for those that changed: saved in another tab, another window or by a checkout. Preference update_changed_links (Design, Linked designs) turns it off. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Docs: the assembly guide says linked designs update when their tab returns Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Links: Vietnamese strings, now that vi is a complete catalog Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Links: remember what each design last read, so an update that fails is tried again A design's linked files are now recorded as the design last read them: when Update Links reads a link without an error, or when the link is first seen. Coming back to the tab reads again what differs, one link per run, so a file that cannot be read holds up no other and is tried again the next time, and a part changed while the assembly was shown is taken up on its next return. Closing several tabs together reads nothing on the way, and the web build, which keeps no file times, looks at nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Links: no read during a save-changes prompt, records for adopted designs and missing files A tab shown to answer "save changes?" reads no link before its save, and Cancel there or on a batch lets the tab left in front read what it skipped. A design opened in place of the blank one records its links at once, a link whose file is missing is recorded as missing so it is read when the file comes back, and a read queued for a design that is no longer shown by the time it starts is dropped. More changed links than can wait at once are read on the next return. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Assemblies: edit a linked component in place, with the assembly around it Activating a linked component opens the design it comes from in a tab of its own, with the rest of the assembly drawn faded around it where the component sits, so the part's own history, browser and commands are at hand. Finish Editing in the browser saves the part, goes back to the assembly and closes the part's tab when the edit opened it; coming back to the assembly updates the changed link (or Finish Editing runs Update Links when that is turned off). Update Links in the part also reads the assembly's links again, off the window thread, and redraws the assembly around the part; a result for an assembly changed meanwhile is dropped with a message. The part is an ordinary tab, so saving, autosave, recovery, closing and quitting treat it as any other design. The model scene's ghost triangles are now drawn (only the preview's were). Preference edit_linked_in_place turns it off. Builds on the update of changed links when an assembly's tab returns. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: a double-click opens it, Activate only activates A double-click on a linked component edits it in place, in the browser as on a face in the view (around the placement clicked), and the component's menu gets Edit in Place. Activate and the browser's radio button make it the active component as they always did, so a linked component can still be activated without opening its design. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Double-click on a component's face: edit a linked one in place, activate any other A double-click on a face in the view activates the component the body belongs to, at that placement, as a double-click on its row does; a linked one is edited in place. Bodies of the design itself or of the active component are left alone, and so is a double-click with a modifier. One preference, double_click_components, covers both gestures. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: fixes from review An edit whose part never opens is forgotten instead of starting on a later open of the same file, and the web build starts the edit after its synchronous open. Finish Editing goes on only for a save into the linked file and in the part's own tab, waits for a "changed on disk" answer, and says so when the part was saved elsewhere. Showing the assembly no longer drops a refresh, which now records the links it read so coming back reads nothing twice. The faded assembly is worked out once per picture, a bad mesh index skips its whole triangle, and the last two status texts come from the catalogs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: Finish Editing on the MODEL tab and the mouse's back button Finish Editing is a command now, component.finish_edit, with its schemas: the app window answers it, anywhere else nothing changes, as with view.fit. While a linked design is edited in place the MODEL tab ends with a FINISH EDITING panel, pinned at the right as FINISH SKETCH is, with a new left-arrow icon; the browser keeps only the line naming the assembly. The mouse's back button, or a keyboard's Back key, finishes too unless a dialog, tool or sketch is open. The assembly guide describes editing in place. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: fixes from the second review Saving the assembly waits while it reads its links for the part Finish Editing waits for dialogs, tools, sketches and prompts open in the part, also when run as a command The assembly reads the edited part explicitly when it does not check its links on its own The FINISH EDITING panel cannot be customized A tab opened by an edit stays that edit's to close when the part is entered again The mouse's back button finishes editing; the keyboard's only while no text field has focus Refreshing the assembly keeps its selection and active component Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: fixes from the third review component.finish_edit run as a command opens nothing and answers with an error when it cannot finish; engine.batch and engine.script refuse it A double-click or Edit in Place while a dialog, tool or sketch is open in the assembly keeps it open What changes in the assembly while it reads its links without changing its document stays: picks, activation, components dragged but not captured Showing the assembly while it reads its links starts no second read A new or opened design in the part's tab ends the edit Finish Editing keeps the part's tab open while its agent chat runs Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: Update Links run as a command in the part refreshes the assembly too Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: the ribbon button reads Finish Edit, as Finish Sketch does A bare "Finish" took the catalogs' surface-finish translation (German "Oberfläche"). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: fixes from the fourth review Finish Edit waits while the part's agent is in the middle of its turn, instead of keeping the tab of any chat open A part saved while its assembly refreshes is read again when the edit finishes: the refresh records the files as it found them A double-click on a linked component while something is open in the assembly says so instead of activating it Commands are recognised in any spelling the engine takes, so engine.batch and engine.script cannot slip Finish Edit through Update Links run as a command refreshes the assembly from the control channel only, not for the app's own reads Moves of components the refresh removed are not carried over, and a refusal is one message The command description and the guide say that the command does not save the part Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: the command is Finish Edit, as Finish Sketch is Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: a command to start it, and fixes from the full review Added component.edit_in_place {component, path?}: the double-click and Edit in Place in the menu run it, and as a command it asks nothing, so a network location not allowed yet or a design open elsewhere makes it fail instead Finish Edit asked by the part's own agent finishes once that agent's turn ends; the button still waits for the turn The parameters and design properties panels, with text typed and not applied yet, hold up entering and finishing an edit A refresh is not taken up under an undo, a queued command or a feature still being computed in the assembly Refusals say what holds them up (a refresh, a file being read or written) instead of nothing The browser strip names the assembly that is refreshing, not any assembly The schema description says the command does not save the part Korean strings for every new message Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: fixes from the second full review The MCP batch tool refuses component.edit_in_place and component.finish_edit as steps instead of sending them one by one Edit in Place asked while the assembly's agent is in its turn opens the part once the turn ends; a double-click then is refused rather than stopping the agent Both commands answer queued: true when they wait for the agent's turn, and stopping the agent forgets what it queued An undo, a queued command or a delete check running in the design holds up entering and finishing an edit A refresh redraws every edit of the assembly, the parts in other tabs too In an assembly never saved, a double-click activates the linked component as before The control and MCP docs list the new batch and script refusals, and the commands list every way they fail Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: fixes from the third full review The MCP batch tool refuses the two commands however a step names them, an execute step too A queued Edit in Place is checked fully when asked for, a second one is refused, and both queued requests wait for what runs in the design instead of being dropped Disconnecting the agent forgets what it queued, as stopping it does Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Edit in place: help text for the Finish Edit button main now requires help for every toolbar command (#7134), and Finish Edit is one. Written in every language the branch's catalog carries. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-28 15:57:44 +00:00
Mateusz Sych	e181015fd1	MCP save: a folder the agent opened or saved a design in stays in scope (#7181) (#7216) ... * claim: #7181 * MCP save: a folder the agent opened or saved a design in stays in scope (#7181) The agent's default folders held the open design's folder only while that design stayed open there, so after a new design, an opened STEP file or a save-as elsewhere a save beside the earlier design was refused, while the same save through the control port worked. The MCP server now keeps, for the rest of its run, the folder of every design file a call opened or saved (open, save, and doc.open, file.save, file.save_as through execute or batch, path given in full) and, headless, of every design open in its session. Such a call only succeeded because the folder was already in scope, so naming a path adds nothing. The folders get the open design folder's terms (inside home or temp, not hidden, hidden entries unreachable), at most 16. Bridged, they go to the app as design_folders, which it judges the same way. The save tool description and docs/mcp.md say how to add a folder with --allow-path. * MCP scope: a design's folder is the folder its file resolves to (#7181) A link in another folder to a design inside the agent's folders passes the scope check, which follows it, but its own folder was what got remembered (and, for the open design, what counted while it was open). Take the folder of the file as the check resolves it. * Control test: a hidden file the export format accepts (#7181) --------- Co-authored-by: MateuszSychXpl <151755914+MateuszSychXpl@users.noreply.github.com>	2026-10-28 12:22:20 +00:00
bherbruck	03b8f4138b	New designs save as .sc; .solidcraft files still open (#7325) ... * claim: new designs save as .sc Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * New designs save as .sc; .solidcraft files still open and keep their name on Save DESIGN_EXT is now "sc"; DESIGN_EXTS lists sc, solidcraft and solvecraft and every open path (dialogs, drag-drop, recent files, CLI, MCP, links, the web picker) accepts all three. Save of an opened .solidcraft file writes that file; Save As, autosave, recovery and crash reports use .sc. Windows, macOS and Linux register .sc alongside the older extensions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Update UI tests for the .sc default extension Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-27 22:41:40 +00:00
sascha2101	e1ff3fa9c0	Batch: refuse a step that would fail at its turn before the first step runs (#5853) (#6781) ... * claim: #5853 * Batch: refuse a step that would fail at its turn before the first step runs (#5853) engine.batch and the MCP batch tool checked only a batch's shape up front. A misspelled command id in a late step was found at its turn, after every earlier step had run, and then all of it was rolled back: a 160-step batch with a typo as its last step ran for a minute and changed nothing. solidcraft_engine::batch_preflight::check finds, before anything runs, the first step the batch would certainly refuse at its turn: a step without a command, an unknown command id (the error names the closest ids, as at the step's turn) or, with strict parameter checking, a call that breaks its command's typed contract. Anything that depends on the design is left to the step's turn. - engine.batch (control channel) checks against the app's registry and its session's level; view.pick, which the app answers itself, passes. - The MCP batch tool checks when the commands run in its own process (headless, with --param-check from the backend). A running app may be another version with other commands and checks the batch itself; its reply's not_run is passed on. - The refusal is the failing step's reply with completed 0, undone 0, not_run listing every step and a note. Tests that used an unknown command only to make a late step fail now use a step that fails at its turn (a bad extrude distance), so they still test rollback, timings and file.new as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FN5eEMrqWWXqi65FcK8GXq --------- Co-authored-by: sascha2101 <221609842+sascha2101@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-26 11:11:10 +00:00
Matthew Knutson	816bcf10de	Every new command comes with input and output schemas (#2829) (#4035) ... * Every new command comes with input and output schemas A test fails for a command without a contract or an output type, unless it is a planned! placeholder or listed in schema/unconverted.txt, which holds the 400 commands that predate the rule and only shrinks: the test also fails when a listed command has its schemas, when the list names a command that doesn't exist, or when it isn't sorted. `checked!` now takes only the command's id and checks the contract that id publishes (`run_checked_as`), so the contract enforced is always the one described. Another test runs every command that has a contract in strict with an unknown key, so a contract is never published without `checked!`, under the command's own id, enforcing it. A new book page, Command schemas, explains how to write a contract and a reply type, the tests to add, the shared field types and how to add one, with a checklist; the failure messages point to it. "Adding a command", CONTRIBUTING.md and AGENTS.md now include the schemas, and the MCP tool description and docs/mcp.md no longer list the converted commands. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * List the commands added on main since: view.layout, view.history_layout, view.normal_to Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Command schemas guide: what participants and targets do, checking the evaluation, warning-free replies - `participants` changes the result for some features and nothing for others; where it and another key override each other, or where it has no effect, say so in that key's description or in the summary. - The example primitive's `targets` default to every body in the feature's component, not the bodies it meets; they're ignored when `participants` lists bodies. - Check what each value does where the feature is evaluated, not only how the handler reads it. - A reply test runs every form in Warn and checks for no `param_warnings` (Strict for a reply that isn't an object). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * List the 43 commands added on main since: frame, component, render and others Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * List the 11 commands added on main since: browser folding, standard views, parameter sweep, path flange browser.collapse_all, browser.expand_all, inspect.parameter_sweep, sheet.path_flange and the seven view.* standard views (back, bottom, front, isometric, left, right, top) landed on main without schemas; the gate flags them, as intended. 457 commands listed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Schema rule warns instead of failing for now A command without input and output schemas prints a warning listing it (test output and a CI annotation). SCHEMA_RULE_STRICT in coverage_tests.rs (or SOLIDCRAFT_SCHEMA_RULE_STRICT=1) makes it fail again. Docs say "should, and will become required". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: bherbruck <brennen.herbruck@gmail.com>	2026-10-26 01:43:02 +00:00
raykholo	309eda87a2	Agent skill for reproducible bug reports (#3983) (#3984) ... * claim: #3983 * Agent skill for reproducible bug reports (#3983) skills/solidcraft-reporting has an agent gather the version, steps and exact error, reproduce the problem in a fresh design (a command script or one batch with rollback off), shrink it while it still fails, check the numbers with measure and a screenshot, keep private designs out, search for duplicates, and write the report in one shape: Reproduced on, Steps with a minimal script, Expected, Actual, Attachments. Listed in skills/README.md and docs/mcp.md; the bug template's steps field points agents to it. The skill-name check now covers its files. * Reporting skill: GitHub takes a design only as a .zip	2026-10-25 17:56:18 +00:00
bherbruck	dfde1e032d	mcp setup: add SolidCraft to the AI clients on this computer; plain mcp finds a late app (#6379) ... solidcraft-cli mcp setup (alias install) and Help > Connect AI assistants edit each installed client's own configuration in place, with this program's absolute path: OpenCode, Claude Desktop, Claude Code, Cursor, Codex, Gemini CLI, Copilot CLI, Windsurf, Zed and VS Code. Only the solidcraft entries change; a stale path is refreshed and an entry the user changed is left alone. Plain mcp keeps looking for the app while its headless session has no work, and says on every tool result that it is headless when the app was not found. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-25 11:57:51 +00:00
DuBearte	a5f7f5a921	Batch: consecutive parameter edits can rebuild the design once (#5822) (#5839) ... * claim: #5822 * Batch: consecutive parameter edits can rebuild the design once (#5822) An agent's batch of parameter edits, one parameter per step, evaluated the design once per edit: an edit early in the timeline rebuilds nearly all of it, and 21 such edits ran for minutes. engine.batch and the MCP batch tool take coalesce_parameters (default false). With it, each run of consecutive plain parameter edits (parameters.change with only a name and an expression, or with changes) is set as one parameters.change {changes}: one rebuild for the run. Any other step ends a run, so later steps see the design up to date. Every step still gets its own result (coalesced: the run's length); the run is one undo step. A run whose combined edit is refused (a new parameter, which changes can't make; a bad expression) runs step by step, so a refused edit is still named by its own step. The app's off-thread evaluation computes the run the same way. The grouping is solidcraft_engine::batch_params, shared by both runners. 21 parameter edits on a plate with 21 extruded bosses (in-process MCP, ci profile): 40.1 s step by step, 3.5 s coalesced, the same volume. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Batch coalescing: say a run skips the states between its edits; test it against step by step (#5822) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-25 01:48:31 +00:00
Dahak Builds	adbd2adf89	view.pick: map screenshot pixels to exact geometry (#6304) (#6329) ... * claim: #6304 * view.pick: map screenshot pixels to exact geometry (#6304) A read-only command that answers, for screenshot pixels (window or model frame) or world-space rays: body, face index, exact world point and outward normal, depth, occurrence/component for placed parts, and the nearest edge/vertex within edge_px. Faces are raycast through the same per-body pick index the mouse uses; flat faces are solved exactly against their plane, curved faces take the mesh hit with the normal interpolated from the mesh's surface normals. Section-aware: faces on the removed side do not stop a pick and the cut cap answers with section_cap. Never touches the selection, camera, document or undo. Exposed as control ui.pick and as view.pick through engine.execute and engine.batch (and through them MCP execute and batch). --------- Co-authored-by: Dahak Builds <dahakbuilds@users.noreply.github.com>	2026-10-25 01:24:39 +00:00
raykholo	0520910bfd	Control: name the token file and spot a stale one when a call is unauthorized (#4664) (#4670) ... * claim: #4664 * Control: name the token file and spot a stale one when a call is unauthorized (#4664) When the app refuses a token that the MCP client read from a token file, the error now names that file, when it was written and how long ago, without printing the token. The app also writes `<port>.pid` beside the token file (its process id and, on Linux, its start time) and removes both at exit; when that process has exited, the error says the token file is stale. The process check runs only after a refusal, and the token file itself stays one line, so existing clients keep working. Document force-quit leftovers and the MSIX AppData redirection. * Bench assistant: read the token out of the new ClientToken Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> --------- Co-authored-by: bherbruck <brennen.herbruck@gmail.com> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-10-24 17:28:12 +00:00
SS-EN	6c6ffe4802	MCP: wait out long requests, honest batch outcomes, batch tool aliases (#2901) ... Rebased onto main as one commit (was 120d26f7, df488f9a, db9d1073 plus merges of main). - A request the app reports as still running (#1618) is waited for on the same connection through `control.pending`; past the wait the error says it was not cancelled and will still apply (or only write its file), later calls are not sent behind it, and the new read-only `pending` tool returns its result once it lands. - A failed batch says what really happened: `rolled_back` only when the design is back where the batch started (as #3288 / #3242 on main: the app's `rolled_back` is believed; for an older app, every completed step undone; only a rollback asked for is reported as one), plus `applied`, `not_run` and `failed.still_running`. - A batch step may name a tool (set_parameter, list_commands, describe_command, execute, measure, inspect_design, undo, redo, export, save, open, new_design, crash_reports); screenshot, body_topology, batch and pending are refused before anything is sent. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-24 02:41:41 +00:00
raykholo	3bca787213	MCP tools: unknown command ids suggest the closest ids (#4846) (#4915) ... * claim: #4846 * MCP tools: unknown command ids suggest the closest ids (#4846) An unknown command id in `execute` or `batch` now lists up to three closest ids, and an id with parameters packed into it says to pass them in `params`.	2026-10-23 13:44:07 +00:00
raykholo	36a354e3a7	Agent chat: serve the bundled skills' reference through an MCP tool (#4966) (#4970) ... * claim: #4966 * Agent chat: serve the bundled skills' reference through an MCP tool (#4966) The bundled skills start with "read reference.md", but SolidCraft's own chat turns the agent's file tools off, so its agent could not follow them. The MCP server gains a read-only `skill_reference` tool that returns a skill's documents from copies built into the binary. It takes a skill name and a file name from a fixed list, never a path, and refuses an unknown skill or file with the available ones. The skills point to it, and docs/mcp.md and skills/README.md describe it.	2026-10-23 13:43:54 +00:00
Taha Zarif	a05a0f1053	Fix/mcp stdio bounded request lines (#4972) ... * test(mcp): reproduce whitespace bypass of request-size limit Add a source-level regression that rejects a JSON-RPC request larger than MAX_LINE even when most of it is whitespace, plus bounded-stdio framing coverage and invalid UTF-8 recovery. * fix(mcp): bound stdio line buffering and validate raw request size Consume oversize JSON-RPC lines in bounded memory while keeping the following request available. Reject whitespace-padded lines before trimming, preventing a request-size cap bypass. * docs(mcp): keep server framing comment idiomatic	2026-10-23 13:43:52 +00:00
Mateusz Sych	fdec948abc	Control channel: control.running lists what the app is running, across connections (#3654) (#3689) ... * claim: #3654 * Control channel: control.running lists what the app is running, across connections (#3654) control.pending answers only for the connection that asks, so a second client, the MCP bridge after a reconnect or a script saw {"pending": null} while the app was busy. control.running answers for the whole app, the same on every connection and at once (the connection's own thread answers it, also while it is busy with a timed-out request): every request the app has been sent and not answered yet, oldest first, with its connection, id, method, command id (or a batch's step count), seconds since it arrived and whether it still waits its turn. A timed-out request stays listed until the app answers it, also after its connection closed. Parameters are never shown. The window marks a request started when it takes it (ControlRequest.started), which tells queued from running. The MCP server gets a read-only `running` tool. --------- Co-authored-by: MateuszSychXpl <151755914+MateuszSychXpl@users.noreply.github.com>	2026-10-21 00:54:33 +00:00
Luke Jones	26c0c19ef7	Preserve imported part names and IGES assembly structure (#1609) ... Build on #1426's import components and nested STEP assembly instances. Replace placeholder solid labels with meaningful part or instance names. Translate IGES groups and subfigure instances through the existing STEP component path, preserving nesting and placements and sewing surfaces within each group. Bound assembly walks and reuse work buffers. Related to: - tangency-labs/solidcraft#1386 - tangency-labs/solidcraft#1426 Co-authored-by: Codex <noreply@openai.com>	2026-10-21 00:39:08 +00:00
Dahak Builds	2b1cb2c4e1	MCP batch: rollback restores the original document (#3242) (#3288) ... * claim: #3242 * MCP batch: rollback restores the design the batch began in (#3242) A failed batch with rollback: true reported rolled_back: true even when the design never went back. Two defects, both fixed: - file.new (and any document-replacing command) replaced the session with it, taking its checkpoints down too, so a batch that failed after file.new had nothing to restore. Session::replace_design now carries the checkpoints over to the fresh session: the checkpoint belongs to the batch, not to the session that happened to be holding the document. - rolled_back echoed the requested flag. It now reports whether the design is actually back: the app answers engine.batch with a new restored field, and the MCP tool reports restored && rollback. An app that predates the field falls back to undone/completed. * Batch: answer with main's rolled_back field after the merge (#3242) Upstream #2900 put the real restore check on engine.batch as `rolled_back` while this branch named it `restored`; the merge kept main's control test and this branch's field, and CI caught it. Standardize on main's wire name: the app answers `rolled_back`, the MCP tool reads it (fallback for older apps unchanged), docs and tests follow. The checkpoint carry-over across file.new is unchanged. --------- Co-authored-by: DahakBuilds <dahakbuilds@users.noreply.github.com>	2026-10-21 00:15:36 +00:00
SS-EN	c7bd467be7	joint.inspect: show agents what each joint is attached to (#3453) ... * joint.inspect: what each joint is attached to, for agents A read-only `joint.inspect {joint?}` gives each joint's definition: for each side the occurrence, its component and path, the snap as saved, and what each persistent face/edge name refers to (the feature that made it, and the sketch and curve a swept side came from), whether the origin resolves and why not; plus kind, offset, angle, flip, values with limits, expressions, the motion links it is in, and its solve errors and conflicts. Its id ends in `.inspect`, so agent gates treat it as reading only. MCP `inspect_design` includes the definitions when the design has joints (`joints: false` leaves them out). joint.list and joint.inspect share the motion-link JSON. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n: catalog entries for Inspect Joint (en, ja, zh) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-20 14:21:54 +00:00
Matthew Knutson	953fd7d5f8	Typed parameter contracts and JSON Schemas for solid.box and solid.extrude (#2829) (#2611) ... * Spike: typed parameter contracts and JSON Schemas for solid.box and solid.extrude The schema RFC's spike (plan/schema-spike.md). solid.box and solid.extrude get typed contracts with generated JSON Schemas (2020-12), checked in front of the unchanged handlers by a per-session level: off (the default, which changes nothing), warn (the call runs and gains param_warnings) or strict (the call is refused and the design left alone). Also engine.describe and the MCP tool describe_command, `solidcraft-cli mcp --param-check off|warn|strict`, a FeatureResult type for feature replies, and an env-var audit recorder (SOLIDCRAFT_PARAM_AUDIT) used to check the contracts against every test. Local spike branch; not for upstream as is (see the results report). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Parameter contracts: put the audit recorder behind a feature; drop two ignored test keys The audit recorder is now on only in a build with the engine's `param-audit` feature and `SOLIDCRAFT_PARAM_AUDIT` set. Its code is still compiled, linted and tested without the feature. `scripts/param_audit.py` summarises a test run's audit logs, and the schema module's docs give the steps for converting a further command. Two tests passed keys their command ignores, which the audit found: `position` on `solid.box` (`hole_face_tests.rs`) and `symmetric` on `solid.extrude` (`face_tests.rs`). Both are removed, so the tests build what they always did. Comments no longer call the contracts a spike. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: bherbruck <brennen.herbruck@gmail.com>	2026-10-20 10:45:08 +00:00
Brazz	26f42ae09b	Snapshot: draw a see-through appearance see-through, and show a tool body inside its target (#2329) (#2330) ... * Snapshot: draw a see-through appearance see-through, and give the CLI --body, --tool and --section A headless picture dropped a body's opacity: the scene carried only a colour, so a design with a translucent appearance was drawn opaque by `solidcraft-cli snapshot`, by MCP screenshots and in a design's thumbnail, although the window has always drawn it as glass. There was then no way to look at the body a cut would remove inside the material it meets: only a volume to measure and reason about, which hides exactly the errors a picture makes obvious (a tool that stops short, or lands in the wrong place). - `SceneMesh` carries the body's opacity; `view::build_scene` takes it from the design (`model_body_opacity`), and a selected body stays solid so the selection colour reads. - The GPU capture routes a see-through body into the scene's glass at its own alpha, as the viewport does; the CPU rasterizer draws the solid bodies first (they own the depth buffer), then the see-through ones blended over them, far sides before near sides and without writing depth, so what lies inside shows and a line between the two is not hidden. - `snapshot --body NAME:opacity=0.3,color=#rrggbb`, `--tool NAME` (that body solid in the tool colour, the rest see-through) and `--section z=27` run the commands the app itself runs (`appearance.assign`, `inspect.section`): the options are shortcuts, not a second renderer. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Tests: measure the tool colour as it is drawn through a see-through target The tool-colour filter was derived on paper and demanded a red more than twice either other channel, which the target in front of it tints away (measured: (200, 108, 85) through opacity 0.3); and the colour check painted the tool, which a solid target hides. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fmt * Snapshot options: strip the colour's # rather than slicing it; README Slicing `value[1..]` on an input-derived string is what the house rules ask us not to write, even where a length check has already made it safe. The error a failed assignment reports now names the body rather than claiming it came from --body, since --tool reaches it too. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * --tool: assign the bodies around the tool in groups, not one command at a time Each appearance.assign is an undo step with a document snapshot behind it, so one per body made --tool cost grow with the size of the design for no reason: the bodies around the tool all get the same opacity, and the ones that share a colour can be named in one call. A design whose bodies all wear the default grey now costs two commands whatever its size. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Rasterizer: say where its glass and the GPU's differ Splitting each see-through body by facing orders its own two layers; it does not sort across bodies, which the GPU does. Worth stating rather than leaving a reader to find it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: bherbruck <brennen.herbruck@gmail.com>	2026-10-19 16:10:45 -04:00
SS-EN	fb82ccb273	Timeline/MCP API: suppress lists, dotted edit keys, set_parameter expression (#2899) ... Timeline and MCP edits take suppress lists, dotted edit keys and parameter expressions.	2026-10-19 10:14:23 -04:00
bherbruck	9eb1540a34	Docs: describe SolidCraft as independent CAD (#2768) ... Reword comments, docs and package descriptions so they describe SolidCraft's own behaviour instead of comparing it to another product. The trademark notice, the commercial-CAD rule and the navigation preset name stay as they were. Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-10-18 21:16:11 -04:00
DuBearte	b04e0801d6	Per-command timings for script runs and batches (#1868) ... Thanks @DuBearte.	2026-10-17 07:26:20 -04:00
DuBearte	9194f4be09	Screenshot of a hidden window: at once, and say so (#1677) (#1707) ... Thanks @DuBearte.	2026-10-16 08:26:08 -04:00
Irakli Kourtis	1a0b33fcf3	Headless pictures draw on the GPU, with the viewport's pipelines (CPU rasterizer as last tier) (#1555) ... Thanks @jyviko.	2026-10-15 22:19:26 -04:00
bherbruck	a13124acdd	Import glTF 2.0 files (.glb, .gltf) as mesh bodies (#1512) ... glTF files open, insert and drop like 3MF/STL/OBJ: a component named after the file, the node tree as nested rigid components, repeated meshes as occurrences, metres to mm, Y up turned to Z up by default (up: z keeps axes), materials as PBR appearances. Bounded, hostile-input tested reader; no new persisted data. Closes #1505. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 17:27:29 -04:00
bherbruck	27529d9742	Imports become components; STEP assemblies as nested components (#1386) (#1426) ... * Imports become components: a STEP assembly's tree as nested components (#1386) Every imported file (STEP, IGES, 3MF, STL, OBJ: inserted, dropped, opened as a design, or file.insert_step / file.insert_mesh / doc.open from scripts, the CLI and MCP) now comes in as a new component named after the file, with its Import feature inside it. A STEP assembly's products become nested components; a part placed more than once is one component with an occurrence per placement, and the Import feature skips the file's later copies (`skip`, format 21 note). The contents are held as one rigid group (rigid joints, glyphs hidden); moving an inner part is refused until component.unlock ("Unlock Contents") releases it. Y up turns the import's component. Replies report component, component_name and occurrence. Undo is one step; designs with loose imports are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Keep an import's rigid group hidden when the window loads the file in the background Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Import instances' skip list is format 22: format 21 ships in 0.12.0 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Catalog entries for Unlock Contents Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 11:04:49 -04:00
bherbruck	1744fbb262	Measure: centre-to-centre for holes, diameters for circles and arcs, slot sizes (#1392) (#1419) ... Measure now reads the picked item's exact shape (cylindrical faces, circular and arc edges, sketch circles, arcs and lines, profiles, planes, points): - A circle, hole or arc shows Ø, R and its length (circumference, or arc length and angle). - A slot (a sketch profile, or a half-cylinder end of a slot in a solid) shows its width, centre-to-centre length and overall length. - Two items where one is round measure from the centre or axis by default (axis to axis, axis to plane, edge or point), with the closest and farthest distances listed too; the panel switches between centre, min and max, and the canvas line follows. - inspect.measure and MCP `measure` (new `items` argument) add diameter, radius, center_distance, min and max; existing fields are unchanged. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 10:27:13 -04:00
NOWN-DEV	b3df2c382b	snapshot --camera and saved views; grid: false / axes: false for headless renders (#1313) ... solidcraft-cli snapshot takes --camera JSON and --view with a saved view name (through view.apply, as the MCP screenshot does), plus --no-grid and --no-axes; the MCP screenshot and ui.render take grid/axes, the headless render skips a hidden origin axis, and the app's ui.render follows the Grid and Origin switches. Closes #1245.	2026-10-15 02:59:56 -04:00
NOWN-DEV	0ee5e97db5	STEP import takes up for Y-up files and names for the bodies' names (#1312) ... file.insert_step and doc.open on a STEP file take `up` (turn a Y-up file so its up is +Z) and `names` (names for the imported bodies). The MCP tool and the app's control requests pass them through; an import without them works as before. Tests in the kernel's STEP reader, the engine, MCP and the file-load UI; docs/step-import.md and docs/mcp.md describe both.	2026-10-15 02:18:55 -04:00
Mateusz Sych	81d9b7e04a	Agent skill for mechanisms: joints by coordinates, loops, links, motion (#1315) ... A solidcraft-mechanisms agent skill with a worked example that a test replays through the MCP server (the actuator follows the hinge with the stated stroke and the drive stops at the rod's limit); the skills index and docs/mcp.md list it.	2026-10-15 02:13:48 -04:00
Mateusz Sych	1473893b08	MCP: a bridged server starts without the app and connects once it runs (#1298) ... The bridged MCP server starts when no app is listening, says so in its instructions and in each tool error, and connects on the first call after the app starts. A batch that could not be sent says the app is not running. docs/mcp.md describes it.	2026-10-15 02:13:18 -04:00
NOWN-DEV	5c6f70cc00	Faces by name in the face commands; model.faces gives a point on each face (#1243)	2026-10-14 20:18:13 -04:00
selune	a261aaa841	Render: integrated workspace, preview image jobs and opaque PBR (#1046) ... Lands the Render workspace (R3), bounded preview-image jobs with cancellation and atomic PNG export (R4a), and opaque PBR looks as one change. - Render workspace: an overlay-free product preview on the installed GPU device. Returning to Design restores its camera. render.scene and render.settings.apply are added. - Image jobs: render.preflight/start/status/cancel/export run bounded CPU preview jobs. Export captures the job, overwrite choice and document, and checks the caller's file scope before writing. - Opaque PBR: looks can carry metal fraction, roughness and dielectric IOR. The product viewport and preview PNG use them; geometry and mass are unchanged. The v1 catalog export refuses PBR rather than dropping it. - Render setups and PBR looks are saved under design format 21. Labels are in en/de/ja/ko/zh/ru. Supersedes #706 and #800. Refs #620, #673, #756, #1004. Contributed by @0xlillith. Co-authored-by: lillith <35337584+0xlillith@users.noreply.github.com>	2026-10-14 19:24:36 -04:00