v1.2 depth expansion

Problem

The v1.0 chart library launched with a curated set of chart types and styling options, but real-world usage data will reveal gaps — chart types that users attempt but don't exist (e.g., waterfall, funnel, heatmap), encoding options that are requested but unsupported, or customization depth that is insufficient for power users. Without expanding the visual language system's depth based on observed usage patterns and retention signals, the library will plateau: users who hit its limits will stop building new dashboards or revert to other tools. Prioritizing expansion by data rather than intuition ensures engineering effort lands on the features that actually drive continued adoption.

Context

Possible Solutions

Plan

Implementation Progress

Review Feedback

• Review cleared