2b620338df
A parameter change evaluates the model and solves the joints inside the command (so that it can refuse a value that breaks a sketch), and `Session::execute` refreshes again after the command and solves every joint a second time, although nothing has moved since. On 40 small parts jointed rigidly to a plate's holes (half of the joints lifted by an expression), changing the lifts' parameter took 0.85 s on main and takes 0.45 s now; changing one part's thickness, 1.96 s and 1.52 s (CLI, medians of 5 runs). The session now keeps the design the joints were last solved for, as the solve left it, and the model that solve read. A refresh that finds the same model, and a design that differs from the solved one at most in its features, leaves the joints as they are: the joints read features only through the model, and a value edit stores the new solutions of the sketches it drove after its solve, so its design is a new one by the time of the second refresh. Placements and bounding boxes come out identical. Test: `a_parameter_change_solves_the_joints_once` counts one solve per change (two before), checks the jointed part still follows the hole, and that a captured move of a jointed part is still solved back. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>