v1.2 depth expansion

Problem

The v1.0 extension covers the core edit-validate-preview loop but lacks depth in areas that usage data and retention analysis will reveal as high-value: advanced chart interactions (drill-down, filtering), multi-file dashboard composition, cross-referencing between YAML definitions and dbt model lineage, or richer Copilot-assisted authoring flows. Without expanding depth in the directions that actual usage patterns demand, the extension remains a "good enough" tool that users tolerate rather than one that drives retention and advocacy. Prioritization must be data-driven — based on observed usage, drop-off points, and feature requests — not speculative.

Context

• This milestone should deepen analyst authoring in VS Code/Cursor with preview, diagnostics, and assist based on what users actually needed after the initial launch, not just what sounded interesting during planning.
• Expansion work is most valuable when it builds on stable foundations and clearly improves real workflows instead of reopening unresolved launch-quality debt.
• Expected touchpoints include apps/ide/vscode-extension/, preview/inspector runtime code, and extension docs/tests, usage feedback, and any launch metrics or review artifacts that indicate where extra depth would matter most.

Possible Solutions

• A - Add the next roadmap ideas opportunistically: keeps momentum, but it risks building depth in areas users do not care about.
• B - Recommended: expand the highest-value workflows using observed usage and retention signals: keep scope tied to concrete evidence and stable foundations.
• C - Avoid depth work until a larger redesign is planned: safer, but it leaves real user demand unanswered for too long.

Plan

1. Review post-launch usage, support, and feedback to identify where deeper investment in analyst authoring in VS Code/Cursor with preview, diagnostics, and assist would most improve real workflows.
2. Define a focused expansion scope with explicit non-goals so new depth does not sprawl into adjacent or unproven ideas.
3. Implement or queue the selected enhancements along with the docs, QA, and migration notes needed to make them safe to adopt.
4. Measure whether the added depth changed user outcomes enough to justify further expansion in the same area.

Implementation Progress

Review Feedback

• [ ] Review cleared