Problem
useGlassWorkspace reduced GlassShell complexity, but it still owns many concerns: Canvas bullet syncing, pending selection, preview tabs, Scratch run state, and diff pane orchestration.
Expected Behavior
Split workspace orchestration by domain and keep top-level shell code focused on routing/layout composition.
Acceptance Criteria
- Canvas, Pending, Scratch, and diff pane state have clearer domain boundaries.
- Top-level shell code is easier to read and reason about.
- Existing workspace behavior remains covered by tests.
Problem
useGlassWorkspacereducedGlassShellcomplexity, but it still owns many concerns: Canvas bullet syncing, pending selection, preview tabs, Scratch run state, and diff pane orchestration.Expected Behavior
Split workspace orchestration by domain and keep top-level shell code focused on routing/layout composition.
Acceptance Criteria