## Created Created by LocalTicketBackend create. --- ## Plan Recorded an initial UI design draft from the panel discussion in `artifacts/workspace-panel-ui-design.md`. Key direction: - make the workspace panel a successor to `--multi`, not a permanent split with the normal single-Pod UI; - use Ticket/action state as the default unit and attach to Pod/session details only on demand; - provide an explicit composer target selector for Companion / New Intake / Selected Ticket / advanced Selected Pod; - add a Gantt-like phase/dependency timeline based on Ticket gates and umbrella/child ordering rather than date estimates. This is a design draft for review/iteration, not implementation approval for the child panel tickets yet. ---