Refine office launch cockpit and loading screen

Author: 2686521696

.kiro/specs/ui-redesign-composer-only-center-input/tasks.md

@@ -3,30 +3,30 @@
 ## Tasks
 
 - [ ] 1. Lock composer-only center expectations with tests
-  - [ ] 1.1 Update `OfficeTaskCockpit.test.tsx` to assert exactly one `UnifiedLaunchComposer`.
-  - [ ] 1.2 Add an assertion that the default center does not render a large autopilot guidance panel.
-  - [ ] 1.3 Add or update launch tests so key composer actions remain visible.
+  - [x] 1.1 Update `OfficeTaskCockpit.test.tsx` to assert exactly one `UnifiedLaunchComposer`.
+  - [x] 1.2 Add an assertion that the default center does not render a large autopilot guidance panel.
+  - [x] 1.3 Add or update launch tests so key composer actions remain visible.
   - [ ] 1.4 Run the targeted tests and confirm the large-panel absence assertion fails before implementation if the panel is still present.
 
-- [ ] 2. Simplify the center composer stack
-  - [ ] 2.1 In `OfficeTaskCockpit.tsx`, keep the composer in the center-bottom launcher stage.
-  - [ ] 2.2 Remove default center rendering of non-composer autopilot guidance.
-  - [ ] 2.3 Keep temporary clarification rendering above the composer only when `currentDialog` exists.
-  - [ ] 2.4 Keep pending-launch status compact and avoid a large default panel.
+- [x] 2. Simplify the center composer stack
+  - [x] 2.1 In `OfficeTaskCockpit.tsx`, keep the composer in the center-bottom launcher stage.
+  - [x] 2.2 Remove default center rendering of non-composer autopilot guidance.
+  - [x] 2.3 Keep temporary clarification rendering above the composer only when `currentDialog` exists.
+  - [x] 2.4 Keep pending-launch status compact and avoid a large default panel.
 
-- [ ] 3. Tune composer visual treatment
-  - [ ] 3.1 Adjust the composer container to match the compact rounded reference shape.
-  - [ ] 3.2 Ensure the send button is visually clear on the right side.
-  - [ ] 3.3 Keep secondary actions compact and readable.
-  - [ ] 3.4 Ensure action labels do not overlap at desktop and tablet widths.
+- [x] 3. Tune composer visual treatment
+  - [x] 3.1 Adjust the composer container to match the compact rounded reference shape.
+  - [x] 3.2 Ensure the send button is visually clear on the right side.
+  - [x] 3.3 Keep secondary actions compact and readable.
+  - [x] 3.4 Ensure action labels do not overlap at desktop and tablet widths.
 
-- [ ] 4. Preserve launch functionality
-  - [ ] 4.1 Verify attachment controls still work through existing callbacks.
-  - [ ] 4.2 Verify create-task access remains present.
-  - [ ] 4.3 Verify advanced/more actions remain present.
-  - [ ] 4.4 Verify launch submission uses existing `UnifiedLaunchComposer` behavior.
+- [x] 4. Preserve launch functionality
+  - [x] 4.1 Verify attachment controls still work through existing callbacks.
+  - [x] 4.2 Verify create-task access remains present.
+  - [x] 4.3 Verify advanced/more actions remain present.
+  - [x] 4.4 Verify launch submission uses existing `UnifiedLaunchComposer` behavior.
 
 - [ ] 5. Verify composer-only center
-  - [ ] 5.1 Run `npx vitest run --pool=forks --poolOptions.forks.singleFork client/src/components/office/OfficeTaskCockpit.test.tsx client/src/components/launch/__tests__/LaunchPanelShell.test.tsx client/src/components/launch/__tests__/LaunchPanelIntegration.test.tsx`.
+  - [x] 5.1 Run `npx vitest run --pool=forks --poolOptions.forks.singleFork client/src/components/office/OfficeTaskCockpit.test.tsx client/src/components/launch/__tests__/LaunchPanelShell.test.tsx client/src/components/launch/__tests__/LaunchPanelIntegration.test.tsx`.
   - [ ] 5.2 Manually inspect home desktop and confirm the center shows only the compact composer over the scene.
   - [ ] 5.3 Update the UI progress SVG after implementation.

.kiro/specs/ui-redesign-home-cockpit-shell-convergence/tasks.md

@@ -2,30 +2,30 @@
 
 ## Tasks
 
-- [ ] 1. Lock the home shell behavior with tests
-  - [ ] 1.1 Update `client/src/components/office/OfficeTaskCockpit.test.tsx` so the mocked `TasksQueueRail` has a `data-testid="tasks-queue-rail"` marker.
-  - [ ] 1.2 Add a test asserting `OfficeTaskCockpit` does not render `data-testid="tasks-queue-rail"` on the home cockpit.
-  - [ ] 1.3 Add a test asserting `OfficeTaskCockpit` still renders exactly one `data-testid="unified-launch-composer"`.
-  - [ ] 1.4 Add a test asserting the home right drawer exposes `launch`, `task`, `flow`, `agent`, `memory`, and `history` tab triggers.
-  - [ ] 1.5 Add a test asserting `data-testid="office-scene-hud"` remains present.
-  - [ ] 1.6 Run `npx vitest run --pool=forks --poolOptions.forks.singleFork client/src/components/office/OfficeTaskCockpit.test.tsx` and confirm the new drawer-removal test fails before implementation.
+- [x] 1. Lock the home shell behavior with tests
+  - [x] 1.1 Update `client/src/components/office/OfficeTaskCockpit.test.tsx` so the mocked `TasksQueueRail` has a `data-testid="tasks-queue-rail"` marker.
+  - [x] 1.2 Add a test asserting `OfficeTaskCockpit` does not render `data-testid="tasks-queue-rail"` on the home cockpit.
+  - [x] 1.3 Add a test asserting `OfficeTaskCockpit` still renders exactly one `data-testid="unified-launch-composer"`.
+  - [x] 1.4 Add a test asserting the home right drawer exposes `launch`, `task`, `flow`, `agent`, `memory`, and `history` tab triggers.
+  - [x] 1.5 Add a test asserting `data-testid="office-scene-hud"` remains present.
+  - [x] 1.6 Run `npx vitest run --pool=forks --poolOptions.forks.singleFork client/src/components/office/OfficeTaskCockpit.test.tsx` and confirm the new drawer-removal test fails before implementation.
 
-- [ ] 2. Remove the home left task queue drawer
-  - [ ] 2.1 In `client/src/components/office/OfficeTaskCockpit.tsx`, remove the left `Splitter.Panel` that renders `TasksQueueRail`.
-  - [ ] 2.2 Remove the `TasksQueueRail` import from `OfficeTaskCockpit.tsx` if it is no longer used.
-  - [ ] 2.3 Adjust the remaining `Splitter.Panel` sizes so the center stage expands into the freed space.
-  - [ ] 2.4 Ensure `selectedDetail`, `activeTaskId`, `filteredTasks`, and task selection logic are not removed if still used by the right drawer and launch flows.
-  - [ ] 2.5 Run the `OfficeTaskCockpit.test.tsx` target and confirm the drawer-removal tests pass.
+- [x] 2. Remove the home left task queue drawer
+  - [x] 2.1 In `client/src/components/office/OfficeTaskCockpit.tsx`, remove the left `Splitter.Panel` that renders `TasksQueueRail`.
+  - [x] 2.2 Remove the `TasksQueueRail` import from `OfficeTaskCockpit.tsx` if it is no longer used.
+  - [x] 2.3 Adjust the remaining `Splitter.Panel` sizes so the center stage expands into the freed space.
+  - [x] 2.4 Ensure `selectedDetail`, `activeTaskId`, `filteredTasks`, and task selection logic are not removed if still used by the right drawer and launch flows.
+  - [x] 2.5 Run the `OfficeTaskCockpit.test.tsx` target and confirm the drawer-removal tests pass.
 
-- [ ] 3. Move center autopilot guidance to the right drawer launch tab
-  - [ ] 3.1 Identify the existing center autopilot/launch guidance inside `launcherFloatingStack`, `launcherDock`, and `launcherContextDock`.
-  - [ ] 3.2 Keep the actual `UnifiedLaunchComposer` in the center-bottom composer.
-  - [ ] 3.3 Move non-composer launch guidance into the right drawer `launch` tab content.
-  - [ ] 3.4 Keep clarification as a separate overlay without duplicating the composer.
-  - [ ] 3.5 Run `OfficeTaskCockpit.test.tsx` and confirm exactly one composer still renders.
+- [x] 3. Move center autopilot guidance to the right drawer launch tab
+  - [x] 3.1 Identify the existing center autopilot/launch guidance inside `launcherFloatingStack`, `launcherDock`, and `launcherContextDock`.
+  - [x] 3.2 Keep the actual `UnifiedLaunchComposer` in the center-bottom composer.
+  - [x] 3.3 Move non-composer launch guidance into the right drawer `launch` tab content.
+  - [x] 3.4 Keep clarification as a separate overlay without duplicating the composer.
+  - [x] 3.5 Run `OfficeTaskCockpit.test.tsx` and confirm exactly one composer still renders.
 
 - [ ] 4. Final home cockpit verification
-  - [ ] 4.1 Run `npx vitest run --pool=forks --poolOptions.forks.singleFork client/src/components/office/OfficeTaskCockpit.test.tsx client/src/components/office/__tests__/OfficeTaskCockpit.cards-integration.test.tsx client/src/components/office/office-task-cockpit-utils.test.ts`.
+  - [x] 4.1 Run `npx vitest run --pool=forks --poolOptions.forks.singleFork client/src/components/office/OfficeTaskCockpit.test.tsx client/src/components/office/__tests__/OfficeTaskCockpit.cards-integration.test.tsx client/src/components/office/office-task-cockpit-utils.test.ts`.
   - [ ] 4.2 Manually inspect `http://localhost:3000/` on desktop after implementation and confirm there is no home left task queue drawer.
   - [ ] 4.3 Confirm the center scene is not covered by a large autopilot panel.
-  - [ ] 4.4 Confirm the right drawer still has six tabs on home.
+  - [x] 4.4 Confirm the right drawer still has six tabs on home.

.kiro/specs/ui-redesign-task-center-workbench-tabs/tasks.md

@@ -2,36 +2,36 @@
 
 ## Tasks
 
-- [ ] 1. Lock `/tasks` workbench tab behavior with tests
-  - [ ] 1.1 Add or update a `/tasks` page test that renders `TasksPage` with desktop viewport state.
-  - [ ] 1.2 Mock `OfficeWorkflowFlowPanel`, `OfficeAgentInspectorPanel`, `OfficeMemoryReportsPanel`, and `OfficeWorkflowHistoryPanel` with visible test ids.
-  - [ ] 1.3 Assert the page contains tab triggers for `任务`, `团队流`, `Agent`, `记忆`, and `历史`.
-  - [ ] 1.4 Assert the page does not contain a `发起` tab trigger.
-  - [ ] 1.5 Assert the task tab renders `TasksCockpitDetail`.
-  - [ ] 1.6 Run the page test with `npx vitest run --pool=forks --poolOptions.forks.singleFork <test-path>` and confirm it fails before implementation.
+- [x] 1. Lock `/tasks` workbench tab behavior with tests
+  - [x] 1.1 Add or update a `/tasks` page test that renders `TasksPage` with desktop viewport state.
+  - [x] 1.2 Mock `OfficeWorkflowFlowPanel`, `OfficeAgentInspectorPanel`, `OfficeMemoryReportsPanel`, and `OfficeWorkflowHistoryPanel` with visible test ids.
+  - [x] 1.3 Assert the page contains tab triggers for `任务`, `团队流`, `Agent`, `记忆`, and `历史`.
+  - [x] 1.4 Assert the page does not contain a `发起` tab trigger.
+  - [x] 1.5 Assert the task tab renders `TasksCockpitDetail`.
+  - [x] 1.6 Run the page test with `npx vitest run --pool=forks --poolOptions.forks.singleFork <test-path>` and confirm it fails before implementation.
 
-- [ ] 2. Add the task center workbench tabs
-  - [ ] 2.1 In `client/src/pages/tasks/TasksPage.tsx`, add local active-tab state for `task`, `flow`, `agent`, `memory`, and `history`.
-  - [ ] 2.2 Add a `Tabs` shell around the main task content.
-  - [ ] 2.3 Render `TasksCockpitDetail` in the `task` tab.
-  - [ ] 2.4 Render `OfficeWorkflowFlowPanel` in the `flow` tab.
-  - [ ] 2.5 Render `OfficeAgentInspectorPanel` or an explicit empty state in the `agent` tab.
-  - [ ] 2.6 Render `OfficeMemoryReportsPanel` in the `memory` tab.
-  - [ ] 2.7 Render `OfficeWorkflowHistoryPanel` in the `history` tab.
-  - [ ] 2.8 Do not render a `launch` tab or trigger on `/tasks`.
+- [x] 2. Add the task center workbench tabs
+  - [x] 2.1 In `client/src/pages/tasks/TasksPage.tsx`, add local active-tab state for `task`, `flow`, `agent`, `memory`, and `history`.
+  - [x] 2.2 Add a `Tabs` shell around the main task content.
+  - [x] 2.3 Render `TasksCockpitDetail` in the `task` tab.
+  - [x] 2.4 Render `OfficeWorkflowFlowPanel` in the `flow` tab.
+  - [x] 2.5 Render `OfficeAgentInspectorPanel` or an explicit empty state in the `agent` tab.
+  - [x] 2.6 Render `OfficeMemoryReportsPanel` in the `memory` tab.
+  - [x] 2.7 Render `OfficeWorkflowHistoryPanel` in the `history` tab.
+  - [x] 2.8 Do not render a `launch` tab or trigger on `/tasks`.
 
-- [ ] 3. Wire workflow context into `/tasks`
-  - [ ] 3.1 Import and use `useWorkflowStore` in `TasksPage`.
-  - [ ] 3.2 Resolve the active workflow for the selected task using existing office utilities.
-  - [ ] 3.3 Preserve task selection when workflow history selects a mission.
-  - [ ] 3.4 Disable or show empty states for tabs whose data is not available.
+- [x] 3. Wire workflow context into `/tasks`
+  - [x] 3.1 Import and use `useWorkflowStore` in `TasksPage`.
+  - [x] 3.2 Resolve the active workflow for the selected task using existing office utilities.
+  - [x] 3.3 Preserve task selection when workflow history selects a mission.
+  - [x] 3.4 Disable or show empty states for tabs whose data is not available.
 
-- [ ] 4. Preserve width and detail behavior
-  - [ ] 4.1 Keep the existing `RightInfoPanel` full-width behavior in `/tasks`.
-  - [ ] 4.2 Keep the `TasksCockpitDetail` full-detail dialog behavior.
-  - [ ] 4.3 Run `client/src/components/tasks/__tests__/TasksCockpitDetail.test.tsx` and `client/src/components/tasks/__tests__/RightInfoPanel.test.tsx`.
+- [x] 4. Preserve width and detail behavior
+  - [x] 4.1 Keep the existing `RightInfoPanel` full-width behavior in `/tasks`.
+  - [x] 4.2 Keep the `TasksCockpitDetail` full-detail dialog behavior.
+  - [x] 4.3 Run `client/src/components/tasks/__tests__/TasksCockpitDetail.test.tsx` and `client/src/components/tasks/__tests__/RightInfoPanel.test.tsx`.
 
 - [ ] 5. Verify task center
-  - [ ] 5.1 Run the new `/tasks` tests.
-  - [ ] 5.2 Run the UI targeted suite that covers `TasksQueueRail`, `TasksCockpitDetail`, `RightInfoPanel`, and `App.shell-layout`.
+  - [x] 5.1 Run the new `/tasks` tests.
+  - [x] 5.2 Run the UI targeted suite that covers `TasksQueueRail`, `TasksCockpitDetail`, `RightInfoPanel`, and `App.shell-layout`.
   - [ ] 5.3 Manually inspect `http://localhost:3000/tasks` and confirm no `发起` tab is visible.