camera

<!-- Use a short conventional title, such as "fix: reject incomplete readings". Write each paragraph on one physical line; do not hard-wrap prose. Remove these hints when completing the description. -->

## Change

<!-- Explain the problem and resulting behavior. Keep the PR focused on one result. Include a compatibility or rollout constraint only when relevant. -->

## Validation

<!-- Name the commands actually run and their results. Summarize meaningful success, invalid-input, boundary, and failure cases in a sentence or short list. Use a table only when it makes the evidence easier to compare. State unperformed checks and material uncertainty. -->

<!-- When applicable, include UI screenshots, a Changeset or why none is needed, dependency compatibility, brand consumer impact, or the required equipment safety evidence. -->