Suite chart creation and settings editing UX pass

Problem

The chart creation and settings editing experience in Cloud Suite is too rough for analysts to use independently. Common tasks — picking a chart type, configuring axes, adjusting visual settings — require falling back to raw YAML editing, which is inaccessible to non-technical users. The settings panel lacks coverage of key visual and query options needed for real dashboards. Until the chart authoring UX reaches a pilot-usable baseline, analysts cannot build production-quality dashboards without engineering assistance.

Context

• Chart creation flow supports common analyst intents with minimal friction.
• Settings editor supports key visual/query options needed for pilot dashboards.
• Analysts can complete core chart workflows without engineering intervention.
• M1 scope should focus on the smallest set of chart authoring actions analysts need weekly, not full parity with raw YAML.
• Nice-to-have advanced settings should remain out of scope unless they block the pilot workflow.

Possible Solutions

Plan

1. Identify the minimum weekly pilot chart workflows that must work without raw YAML fallback.
2. Implement the highest-impact settings/editor improvements for that narrow workflow slice first.
3. Add validation messaging and defaults for the top analyst misconfiguration cases.
4. Run acceptance sessions on the narrowed workflow and explicitly defer non-blocking advanced settings.

Implementation Progress

• graph-library chart capability baseline
• dft-core chart settings contract
• Scope clarification: this task should deliver a bounded pilot baseline, not comprehensive chart-editor coverage.

QA Exploration

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

Review Feedback

• Review cleared