* claim: #12313
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Plastic rules: input and output schemas for Manage, Assign and List Plastic Rules (#12313)
The three plastic rule commands get typed contracts and replies, in a
new `schema/plastic.rs` laid out like the sheet metal rules', and leave
`schema/unconverted.txt`.
- Each key reads as its handler reads it, with the handler's message:
the rule name as `plastic.manage_rules` trims and limits it, `bodies`
through `config::NameList` (which mirrors `params::string_list`), the
ten rule values as `LengthExpr` and `AngleExpr`.
- `name` and `bodies` are optional in the types and required in the
schemas (a `require` transform), so a call without them still gets
the handler's own message.
- Keys of the wrong type that the handlers ignore today (a non-boolean
`active` or `delete`, a rule value that is neither a number nor text,
a non-text `from`, `material` or `rule`) are refused; in warn the call
still works, with a warning. A test pins each one.
- The handlers build their replies from the reply types through a small
`typed_reply`; the JSON is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Assign Plastic Rule: the schema's `bodies` is a name or a non-empty list, not null
The field is `Option<NameList>`, so its published schema allowed `null`
(from the `Option`) and an empty list (from `NameList`), both of which
the handler refuses ("`bodies` must list bodies"). It now has its own
schema: a name, or a list of 1 to 10 000 names. The reader is unchanged,
so strict still gives the handler's message for those calls. The schema
test adds both cases.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: bherbruck <brennen.herbruck@gmail.com>