Enable internal analyst IDE flow

Problem

The core analyst loop — open a YAML dashboard file, edit it, see validation diagnostics, and preview the rendered output — does not yet work end-to-end in VS Code/Cursor with the stability required for pilot usage. Preview rendering can desync from the saved file, validation diagnostics appear late or not at all after edits, and there is no clear "happy path" that an analyst can follow from an empty file to a working dashboard. Without a stable, documented IDE flow, the pilot cannot start because analysts will hit blocking issues in their first session.

Context

• This task should act as the end-to-end pilot acceptance contract for the IDE workflow, not duplicate all implementation work in the profiler and usability-hardening tasks.
• Detailed UX fixes belong in task-m1-ide-extension-usability-hardening.md.
• Profiler-specific readiness belongs in task-m1-ide-profiler-surface-pilot-ready.md.
• The deliverable here is a documented, validated happy path that proves the full analyst loop works.

Possible Solutions

Plan

1. Define the exact analyst happy path for IDE-based pilot usage from opening a repo to previewing a working dashboard.
2. Use the profiler-surface and usability-hardening tasks to close underlying product gaps.
3. Validate the full path in VS Code/Cursor on real pilot repos.
4. Publish a short runbook/checklist for pilot analysts and record remaining known limitations.

Implementation Progress

• Scope clarified: this task is the integration/acceptance wrapper for the IDE pilot flow rather than another broad implementation bucket.

Review Feedback

• Review cleared