* claim: #12288
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Render camera: input and output schemas for Set, Inspect and Frame Render Camera and Apply Render Camera (#12288)
The four commands that set, read, fit and apply the render camera get
typed contracts and replies, in a new `schema/render_camera.rs`, and
leave `schema/unconverted.txt`.
- `RenderCamera` is a saved render setup's camera: its keys, and the
bounds `RenderSetup::validate` keeps (1e9 mm, 1e6 radians, a positive
distance, 0 <= fov < pi). The reader decodes it as the handler does,
through a setup holding only that camera, so each refusal keeps the
handler's message. The bounds are in the input schema only: a reply
gives back the camera in the view, which Frame Render Subject can move
beyond them, so the output schema has the camera's shape alone.
- `camera` and `name` 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; `#[schemars(required)]` doesn't do this
next to `serde(default)`.
- The handlers build their replies from the reply types through a small
`typed_reply`; the JSON is unchanged.
Tests check each camera and aspect case against both the schema and the
handler, keep today's messages in strict, and match every reply against
its schema in warn.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>