v1.2 depth expansion

Problem

The v1.0 YAML contract covers a baseline set of chart types, layout options, and query patterns, but post-launch usage data reveals gaps where users hit the limits of what can be expressed — missing chart types, unsupported layout configurations, or query patterns that require workarounds. Without expanding the contract's depth based on observed demand, users either abandon Dataface for use cases it almost-but-doesn't-quite support, or resort to fragile hacks that the normalizer wasn't designed to handle.

Context

• This milestone should deepen the YAML contract, compiler/normalizer, execution adapters, and release/versioning 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 dataface/core/, schema/compiled types, docs, and core test suites, 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 the YAML contract, compiler/normalizer, execution adapters, and release/versioning 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