39 commits, squashed; the originals stay reachable from tag archive/merge-main-develop. These commits sit on several merged branches, so the wave holds their combined result. - 1b17dd7f5 brett19: Merge fixes: every crate and test target compiles on the merged tree, but for crates/geom's hlr - 8f2c11da2 brett19: Drawings hidden lines: read develop's B-rep records - c30ca0216 brett19: Hidden-line fixtures: build develop's records from the fixtures' data - 5dd2509ae brett19: Hidden lines: tests of the bounded edges, face charts and placed revolutions - 1642df0ea brett19: drawing-hlr doc: what is drawn and refused on develop's records - ddcb80c8e brett19: hlr tests: a placed revolution is refused when its placement is not rigid - e4977721f brett19: Hidden lines: a traced intersection is drawn only where its spline lies on both surfaces - b3ef6ae52 brett19: Hidden lines: kernel bodies through the production prepare against closed forms - 4cd2ae062 brett19: Tests from main: the world state is a Result here - 51d7ad09e brett19: A blend's pick measures close edges on their curves, not their polylines - 11a89713c brett19: Merge fixes from the first SMLib test pass - 48fcb7aac brett19: Merge fixes from the ui test pass and the gates - abd739855 brett19: A silhouette takes its facing from the surface's normals - 85114c5a2 brett19: Clippy and rustfmt on the merged tree - 55a46569f brett19: Stepwise open checks every feature under the session's mode - 4627402e4 brett19: Clippy without SMLib: the planar-sheet edge reader is built only with it - 5fbece0ac brett19: STEP import: a ball's halves whose seams are off each other's quarter lines each form within one turn - eb78d20b0 brett19: Lid ring sketch test: find the ring under the pick, not by main's kernel's name - 3048d8c49 brett19: Viewport culling test: each box's triangles from its mesh, not 12 - dc88b80e2 brett19: Timeline chip test: a fillet that really reduces - 876203621 brett19: Edge names: a seam names its one face once; the curve-id test reads every edge kernel-neutrally - 900635710 brett19: rustfmt on the merged tree - b7e83cd7c brett19: Known failing on SMLib: two of main's new tests assume truck's box mesh and fillet torus - 63bde053a jyviko: Locales: Vietnamese for the setback-too-short refusal, now that vi is a complete catalog - 967a1caa6 brett19: Kernel rig: exact volumes for 1213's bent-tube round and 4782's bar round, rel 1e-6 - 82c821d2a brett19: After the merge: clippy's auto-deref, and the mesh-decisions list for the merged tree - 5862ee223 brett19: After the merge: main's new tests on the SMLib kernel - be78372b2 brett19: Twisted sweep: circles about a straight path are exact cylinders (solidcore#2184) - 312d14500 jyviko: 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 - 6f7e51acb jyviko: After the merge: split_move's Result reaches its callers; to_local's duplicated move check goes - 8f0c79b20 jyviko: After the merge: main's two new tests take world_state's Result, as the rest of their files do - 5f4d70061 jyviko: After the merge with main: its new code on develop's exact bounds, types and thread fields - 2b2ab6627 jyviko: Cargo.lock: develop's profile, smlib and step crates at main's 0.30.1 - e6a4b0a9a jyviko: Kernel rig: main's six new sketch-only commands are exempt from a kernel case - 5acbd2e71 jyviko: Cuts leave the bodies their tools can't reach, by exact boxes (#10225 on exact geometry) - d2b202307 jyviko: Kernel rig: main's new view, rendering, appearance and settings commands are exempt from a case - 21db090ba jyviko: Kernel rig: construct.plane.axis_point gets construction cases - c1f45cae2 jyviko: Kernel rig: assembly cases for mass properties, align, find limits and moving items between parts - 084695416 jyviko: Kernel rig: export and print face cases in the import area Co-authored-by: jyviko <2501648+jyviko@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ
2.1 KiB
Change
Start with what this is, in plain words someone new to the project would understand: what it does and who it's for. Don't assume anyone knows the name of your tool, project or feature. Then describe the problem and resulting behavior. Link the issue when applicable.
Changes a default: no
Validation
What did you run, and what were the results? Include expected and measured values for geometry changes.
Screenshots of the behavior (when observable)
Put the picture or video here in the description. A file in the diff doesn't count: a maintainer has to be able to see what this is without opening the changed files.
For observable CAD, UI or model behavior, include actual descriptive screenshots or a short recording from a small reproduction. This includes kernel, geometry, assembly and backend effects that can be shown in the app. Coding agents should run the app and capture the evidence themselves, rather than asking a human for evidence they can produce. Show the actual failure/result, preferably before and after, with brief steps, expected/actual behavior and annotations where helpful.
Flowcharts and Mermaid diagrams cannot substitute for evidence of visible behavior. Use diagrams for architectural reasoning when actual screenshots cannot illustrate the point. Changes with no useful observable behavior may omit screenshot/video evidence. Exclude private designs and sensitive details; attach media or link to an accessible recording rather than committing generated review artifacts.
Integration status
Record the upstream commit and PR status checked before handoff, any conflicts resolved, and validation after integration. Keep up with upstream merges and monitor this PR while the task is active; rebase before pushing and never force-push.