Discuss authored chart width, height, and aspect ratio controls

Problem

Evaluate whether Dataface should expose chart-level width, height, and possibly aspect ratio in authored YAML for Vega-Lite-backed charts. Capture the current mismatch between layout-item sizing and chart-spec sizing, assess whether a clean schema pass-through exists, and decide if this should ship as a documented chart surface rather than a one-off workaround.

Context

• There is a mismatch between layout sizing and Vega-Lite chart sizing that authors cannot express cleanly today.
• Exposing sizing controls carelessly could break responsive behavior or duplicate layout responsibilities.
• The decision should align with the chart render boundary and documented author-facing schema.

Possible Solutions

• A - Keep sizing implicit and tell authors to rely only on layout containers: simple, but may under-serve valid use cases.
• B - Pass width, height, and aspect ratio straight through everywhere with minimal guardrails: flexible, but likely confusing and brittle.
• C - Recommended: define a narrow authored sizing surface with clear semantics, documented constraints, and explicit separation from layout-item sizing.

Plan

1. Document the current sizing path from authored YAML through layout and Vega-Lite output.
2. Evaluate the common author use cases that truly require explicit chart sizing controls.
3. Propose the smallest schema surface and precedence rules that avoid layout conflicts.
4. Decide whether to implement now, defer, or document as an intentional non-goal.

Implementation Progress

QA Exploration

• [ ] QA exploration completed (or N/A for non-UI tasks)

Review Feedback

• [ ] Review cleared