#12168: feat: integrate Mission Control dashboard into Control UI

- Add Mission Control as new tab in Control UI navigation - Create Kanban board view with 6 task status columns: - Pending, Running, Review, Revising, Done, Failed - Implement task management features: - Create new tasks with title, description, priority, tags - Update task status by moving between columns - Delete tasks with confirmation modal - Assign agents to tasks using sessions_spawn - Track session keys and link to chat sessions - Add server-side RPC handlers for mission control: - missionControl.list - Fetch all tasks - missionControl.create - Create new task - missionControl.update - Update task status/details - missionControl.delete - Delete task - missionControl.spawnAgent - Spawn agent for task - Use existing SQLite DB at ~/.openclaw/workspace-dev/data/mission_control.db - Follow OpenClaw UI patterns (Lit components, existing CSS variables) - Add responsive Kanban board layout with drag-drop styling - Add target icon for Mission Control tab navigation <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR adds a new “Mission Control” tab under the Control UI with a Kanban-style task board and client-side controllers to list/create/update/delete tasks and spawn an agent for a task. On the server side, it registers new gateway RPC methods (`missionControl.*`) and implements a handler module that reads/writes tasks from a local SQLite database (falling back to an in-memory array). The overall integration touches navigation (new tab + icon), rendering (new view + state plumbing), and gateway method registration/authorization to route the new RPCs through the existing gateway infrastructure. <h3>Confidence Score: 2/5</h3> - This PR is not safe to merge as-is due to a definite module syntax error and some inconsistent/duplicated state wiring. - The new `import` added mid-file in `ui/src/ui/app-render.ts` will break compilation/runtime. In addition, `ui/src/ui/app.ts` introduces a duplicate set of Mission Control state fields and at least one unused import, which is likely to fail CI/lint and makes the integration error-prone. Server handler typing also has a clear response/type mismatch that should be corrected before relying on it. - ui/src/ui/app-render.ts, ui/src/ui/app.ts, src/gateway/server-methods/mission-control.ts <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->