v1.2 depth expansion

Problem

After v1.0 stabilization, the profiler covers a baseline set of semantic types and statistical measures, but usage data will reveal which profile features analysts actually rely on and where they drop off. Some columns that users frequently inspect may lack useful profiling depth (e.g., JSON columns with no structure extraction, array columns with no element-level statistics), while other profile sections that were expensive to build may see little engagement. Without prioritizing depth expansion based on observed usage patterns and retention signals, engineering effort will be allocated by intuition rather than evidence, and the profiler will add features users don't need while leaving gaps in features they do.

Context

• This milestone should deepen warehouse profiling, semantic inference, and analyst-facing inspect/context artifacts 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/inspect/, schema-context consumers, inspect docs, and core 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 warehouse profiling, semantic inference, and analyst-facing inspect/context artifacts 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