Implement Phase 13 - Data and Feedback Widget Component Migration

.spec/planning/live_ui/README.md

@@ -35,8 +35,11 @@ The plan aligns to:
 10. [Phase 10 - Documentation, Validation, and Release Readiness for Style Realization](./phase-10-documentation-validation-and-release-readiness-for-style-realization.md): finish the rollout with migration guidance, validation gates, hardening, and release-readiness coverage for browser-realized canonical styling.
 11. [Phase 11 - Widget LiveComponent Contract and Runtime Backbone Realignment](./phase-11-widget-livecomponent-contract-and-runtime-backbone-realignment.md): establish the shared widget LiveComponent contract, stable widget identity and routing model, and the runtime backbone needed to make widgets real mountable component boundaries.
 12. [Phase 12 - Foundational, Input, Navigation, and Form Widget Component Migration](./phase-12-foundational-input-navigation-and-form-widget-component-migration.md): migrate the foundational widget families, forms, and navigation surfaces onto the new widget-component architecture while keeping the direct-use API ergonomic.
-13. [Phase 13 - Advanced Widget Component Migration and Canonical Renderer Convergence](./phase-13-advanced-widget-component-migration-and-canonical-renderer-convergence.md): migrate advanced data, feedback, overlay, operational, and display widgets and make canonical rendering target the same widget component boundaries.
-14. [Phase 14 - Tooling, Demo, Validation, and Release Readiness for Widget Components](./phase-14-tooling-demo-validation-and-release-readiness-for-widget-components.md): finish the widget-component transition with demo/example upgrades, tooling visibility, validation gates, documentation, and cleanup of legacy helper-only paths.
+13. [Phase 13 - Data and Feedback Widget Component Migration](./phase-13-data-and-feedback-widget-component-migration.md): migrate structured data, document, and feedback surfaces onto the shared widget-component architecture.
+14. [Phase 14 - Overlay, Operational, and Display Widget Component Migration](./phase-14-overlay-operational-and-display-widget-component-migration.md): migrate overlay, operational, and display widgets onto the widget-component model.
+15. [Phase 15 - Canonical Renderer Convergence](./phase-15-canonical-renderer-convergence.md): finish the convergence work so canonical `UnifiedIUR` rendering targets the same widget component boundaries used by direct native screens.
+16. [Phase 16 - Advanced Widget Integration Tests](./phase-16-advanced-widget-integration-tests.md): validate the complete widget-component architecture end to end across all widget families.
+17. [Phase 17 - Tooling, Demo, Validation, and Release Readiness for Widget Components](./phase-17-tooling-demo-validation-and-release-readiness-for-widget-components.md): finish the widget-component transition with demo/example upgrades, tooling visibility, validation gates, documentation, and cleanup of legacy helper-only paths.
 
 ## Shared Conventions
 - Numbering:

.spec/planning/live_ui/phase-13-data-and-feedback-widget-component-migration.md

@@ -0,0 +1,57 @@
+# Phase 13 - Data and Feedback Widget Component Migration
+
+Back to index: [README](./README.md)
+
+## Relevant Shared APIs / Interfaces
+- `LiveUi.Widgets.List`
+- `LiveUi.Widgets.Table`
+- `LiveUi.Widgets.TreeView`
+- `LiveUi.Widgets.MarkdownViewer`
+- `LiveUi.Widgets.LogViewer`
+- `LiveUi.Widgets.Status`
+- `LiveUi.Widgets.Progress`
+- `LiveUi.Widgets.Gauge`
+- `LiveUi.Widgets.InlineFeedback`
+- `LiveUi.Widgets.Sparkline`
+- `LiveUi.Widgets.BarChart`
+- `LiveUi.Widgets.LineChart`
+- `LiveUi.Component`
+- `LiveUi.Widget.Identity`
+
+## Relevant Assumptions / Defaults
+- Phases 11 and 12 have established the shared widget-component contract and migrated foundational, input, navigation, and form widget families.
+- Data and feedback widgets must converge on the same widget-component architecture.
+- Some advanced surfaces may remain visually minimal at first, but they still need to respect the widget-component contract and event/lifecycle boundaries.
+
+[ ] 13 Phase 13 - Data and Feedback Widget Component Migration
+  Migrate structured data, document, and feedback surfaces onto the shared widget-component architecture.
+
+  [ ] 13.1 Section - Data and Document Widget Component Migration
+    Migrate collection and document surfaces so they stop relying on passive markup-only implementations.
+
+    [ ] 13.1.1 Task - Convert data and document widgets to explicit component boundaries
+      Migrate collection and document widgets to widget component implementations with explicit lifecycle and event semantics.
+
+      [ ] 13.1.1.1 Subtask - Convert `list`, `table`, `tree_view`, `markdown_viewer`, and `log_viewer` to widget component implementations.
+      [ ] 13.1.1.2 Subtask - Ensure collection-item identity, selection semantics, and canonical item attributes remain stable through mounted widget component boundaries.
+      [ ] 13.1.1.3 Subtask - Add tests that prove data and document widgets preserve continuity across server updates and canonical rerenders.
+
+  [ ] 13.2 Section - Feedback and Chart Widget Component Migration
+    Migrate feedback and chart surfaces so they share the same widget-component runtime contract.
+
+    [ ] 13.2.1 Task - Convert feedback and chart widgets to explicit component boundaries
+      Migrate feedback and chart surfaces to widget component implementations.
+
+      [ ] 13.2.1.1 Subtask - Convert `status`, `progress`, `gauge`, `inline_feedback`, `sparkline`, `bar_chart`, and `line_chart` to widget component implementations.
+      [ ] 13.2.1.2 Subtask - Ensure state variants, style realization, and canonical renderer behavior continue to work after the migration.
+      [ ] 13.2.1.3 Subtask - Add tests that prove feedback and chart widgets remain deterministic across direct-native and canonical paths.
+
+  [ ] 13.3 Section - Phase 13 Integration Tests
+    Validate the data and feedback widget migrations end to end.
+
+    [ ] 13.3.1 Task - Data and feedback widget integration scenarios
+      Verify data and feedback widgets now behave as real widget components across representative direct-native and canonical flows.
+
+      [ ] 13.3.1.1 Subtask - Verify data, document, feedback, and chart widgets preserve identity and bounded local state through mounted component boundaries.
+      [ ] 13.3.1.2 Subtask - Verify collection widget event routing remains correct for selection, pagination, and item interactions.
+      [ ] 13.3.1.3 Subtask - Verify visually minimal widgets still respect the widget-component contract even before richer rendering improvements land.

.spec/planning/live_ui/phase-14-overlay-operational-and-display-widget-component-migration.md

@@ -0,0 +1,68 @@
+# Phase 14 - Overlay, Operational, and Display Widget Component Migration
+
+Back to index: [README](./README.md)
+
+## Relevant Shared APIs / Interfaces
+- `LiveUi.Widgets.OverlaySurface`
+- `LiveUi.Widgets.Dialog`
+- `LiveUi.Widgets.AlertDialog`
+- `LiveUi.Widgets.ContextMenu`
+- `LiveUi.Widgets.Toast`
+- `LiveUi.Widgets.StreamWidget`
+- `LiveUi.Widgets.ProcessMonitor`
+- `LiveUi.Widgets.SupervisionTreeViewer`
+- `LiveUi.Widgets.ClusterDashboard`
+- `LiveUi.Widgets.Viewport`
+- `LiveUi.Widgets.ScrollBar`
+- `LiveUi.Widgets.SplitPane`
+- `LiveUi.Widgets.Canvas`
+- `LiveUi.Component`
+- `LiveUi.Widget.Identity`
+
+## Relevant Assumptions / Defaults
+- Phases 11, 12, and 13 have established the widget-component contract across foundational, input, navigation, form, data, and feedback widget families.
+- Overlay and operational widgets are more stateful and benefit significantly from explicit widget-local lifecycle boundaries.
+- Display system widgets need explicit event boundaries for viewport, scroll, split, and canvas interactions.
+
+[ ] 14 Phase 14 - Overlay, Operational, and Display Widget Component Migration
+  Migrate the more stateful widget families that most benefit from explicit widget-local lifecycle boundaries.
+
+  [ ] 14.1 Section - Overlay Widget Component Migration
+    Migrate dialogs, overlays, and transient overlay surfaces so their bounded local lifecycle becomes explicit and testable.
+
+    [ ] 14.1.1 Task - Convert overlay widget surfaces to explicit component boundaries
+      Migrate overlay widgets to widget component implementations.
+
+      [ ] 14.1.1.1 Subtask - Convert `overlay_surface`, `dialog`, `alert_dialog`, `context_menu`, and `toast` to widget component implementations.
+      [ ] 14.1.1.2 Subtask - Define how open, close, focus, anchor, placement, and dismissal behavior use bounded widget-local state without violating server authority.
+      [ ] 14.1.1.3 Subtask - Add tests that prove overlay lifecycle behavior remains aligned across direct-native and canonical usage.
+
+  [ ] 14.2 Section - Operational Widget Component Migration
+    Migrate stream, monitoring, and dashboard widgets onto the widget-component model.
+
+    [ ] 14.2.1 Task - Convert operational widgets to explicit component boundaries
+      Migrate operational widgets to widget component implementations.
+
+      [ ] 14.2.1.1 Subtask - Convert `stream_widget`, `process_monitor`, `supervision_tree_viewer`, and `cluster_dashboard` to widget component implementations.
+      [ ] 14.2.1.2 Subtask - Ensure streaming, monitoring, and dashboard state management works through bounded widget-local state.
+      [ ] 14.2.1.3 Subtask - Add tests that prove operational widgets preserve real-time updates and bounded local state.
+
+  [ ] 14.3 Section - Display System Widget Component Migration
+    Migrate viewport, scroll, split, and canvas widgets onto the widget-component model.
+
+    [ ] 14.3.1 Task - Convert display system widgets to explicit component boundaries
+      Migrate display system widgets to widget component implementations.
+
+      [ ] 14.3.1.1 Subtask - Convert `viewport`, `scroll_bar`, `split_pane`, and `canvas` to widget component implementations where they need lifecycle or event boundaries.
+      [ ] 14.3.1.2 Subtask - Ensure viewport, scroll, split, and canvas interactions use proper event routing through widget boundaries.
+      [ ] 14.3.1.3 Subtask - Add tests that prove display system widgets preserve interaction semantics through component boundaries.
+
+  [ ] 14.4 Section - Phase 14 Integration Tests
+    Validate the overlay, operational, and display widget migrations end to end.
+
+    [ ] 14.4.1 Task - Overlay and operational widget integration scenarios
+      Verify overlay and operational widgets now behave as real widget components.
+
+      [ ] 14.4.1.1 Subtask - Verify overlay widgets preserve lifecycle, focus, and dismissal behavior through mounted component boundaries.
+      [ ] 14.4.1.2 Subtask - Verify operational widgets preserve real-time updates and bounded local state.
+      [ ] 14.4.1.3 Subtask - Verify display system widgets preserve interaction semantics through component boundaries.