Improve styles autofill from labels

Objective

• Extend styles and materials assistance so equipment photos can drive structured autofill when legible labels are present (for example manufacturer, model, serial number, manufacture date encoded in serials, capacity stickers).
• This is intentionally narrower than the full styles-and-materials workflow in ATT-1675.

Background

• May 15 feature sync (Chris): After ATT-1675 establishes the manual plus AI-assisted shell, a subset of value can come from reading labels in photos rather than only free-form comments.
• Examples called out: manufacturer date and serial number patterns—inspectors already photograph nameplates; the product should reuse that asset instead of retyping.
• Decision needed: minimum OCR / vision quality bar, PII handling for serials, and human confirm before writing authoritative report fields.

Scope

Report Writer product (primary)

• Decision needed: which styles and materials slots accept label-derived suggestions and which remain manual-only for liability reasons.

Vision / ML pipeline

• Label detection versus full-frame OCR—Decision needed latency budget on device vs server.

Backend

• Persistence and provenance (which photo, which bounding box or crop, confidence)—coordinates with ATT-1672 when schemas live in Attik backend.

Codebase audit note

• attik-frontend, attik-backend, and attik-mobile under this audit did not expose Report Writer authoring modules by name; implementation likely lives in the Report Writer app repo or branch—link it here when known.
• attik-frontend/src/app/client/reports/components/StylesAndMaterialsCard.tsx only reflects published observation rendering for clients, not authoring.

References

• ATT-1675 (parent workflow: manual entry plus broader AI assist from comments and photos).
• ATT-1672 (server-side schema and API ownership for Report Writer data).