eb29c4b2d8
* claim: sheet.* typed parameter schemas * Sheet metal feature commands: typed parameter contracts sheet.flange, sheet.perforate, sheet.hem, sheet.fold, sheet.unfold, sheet.refold and sheet.convert read their parameters by hand, so a misspelt key or a value of the wrong shape was ignored or failed late, and describe_command had only prose for them. Each now has a contract in schema/sheet.rs, checked in front of the unchanged handler, and returns FeatureResult. The values no shared type fits (sheet-edge points, an edge flange's edges, a fold's line and fixed point, the flange type, the positions, the relief shape and the perforation pattern) get types that call the handlers' own readers, split out of cmd/sheet.rs, and give their messages. The rule's values (thickness, K-factor, bend radius, reliefs) stay out of the contracts: the handlers refuse them, and strict refuses them as unknown keys. A test passed a nested `base` object whose `sketch` the flange never reads; it now names the sketch at the top level. Part of #2829 (#6581). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Sheet metal contracts: a further bend's angle stays as lenient as before The flange handler reads a `then` bend's `angle` that is no expression (`true`, a list) as left out and bends it 90 degrees. The rebased contract had moved that check into the shared reader, so the handler refused such a call even with the check off. The reader is back to the handler's behaviour, and `ThenSteps` is the stricter one, as the schema guide asks: warn reports such an angle and strict refuses it. Tests cover the reader's leniency, the type's refusal and the three check levels on one flange. Part of #2829 (#6581). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>