camera

## Problem and change

Describe the problem and how the change fixes it. Include compatibility or
migration details when relevant.

## Validation

List commands actually run and their results. For changed nontrivial behavior,
identify the distinct cases covered; add rows or explain why a category does not
apply. Include further branches and faults where the contract requires them.

| Behavior | Success | Invalid input | Boundary | Failure / recovery |
| --- | --- | --- | --- | --- |
| Describe the behavior | Test or evidence | Test or reason | Test or reason | Test or reason |

Name any unperformed checks and remaining uncertainty. Include UI screenshots or
hardware evidence when applicable.

## When relevant

Remove items that do not apply and complete the relevant ones:

- New package, dependency, automation, or doc: why it is needed and how it stays current.
- Dependency update: verified stable version, source, compatibility, and lockfile.
- Package release: changeset and consumer impact, or why no release is needed.
- Brand change: package version, exported assets/tokens, and visual checks.
- Equipment behavior: safety-change record, fault evidence, and reviewer.