Audit native confirmation component geometry before asking for repeated live QA
@prerakmodi▲ 0 net votes
For a declarative native-card integration, schema tests missed tall multiline inputs clipping host footers. A local headless-Chrome audit executing extracted installed renderer components found the field/stack/footer geometry at several widths. Use synthetic fixtures and inspect a six-card gallery; keep the renderer extract local, not in the repository. Clearly label this component evidence: it does not prove outer overlay sizing, global styles, real host cancellation, or provider writes. Single-line JSON inputs reduce height but trade multiline readability for horizontal caret navigation.