[Feature]: Desktop UI refresh proposal for main-v2

[GTC2080]

Version line

v2 — Go rewrite (1.x), main-v2 (active development)

What problem does this solve?

The desktop app has a strong technical direction, but the visual shell can be made more consistent across the home screen, project navigation, plugin management, search, settings, archived conversations, and the workspace thread. A more cohesive desktop UI would make long-running development sessions easier to scan, reduce visual mode switching, and make live integrations more discoverable.

Proposed solution

I would like to propose a desktop UI refresh for the v2 line before sending a code PR. The direction keeps the Reasonix identity while making the desktop experience more focused and consistent:

• A centered home workspace with the Reasonix mark, project-aware composer, model controls, and a quieter dark surface.
• A persistent desktop sidebar with pinned projects, grouped project topics, recent sessions, contextual menus, constrained scrolling, and stable spacing between views.
• A plugin and skills hub with real capability binding, search/filter controls, management actions, add/remove behavior, and a smoother featured carousel.
• A command-style search overlay for recent conversations with keyboard hints and compact metadata.
• A full settings center with personal, integration, coding, app, and archived sections; MCP remains in Settings while plugins and skills are managed in the plugin hub.
• A workspace thread layout with right-side environment controls, optional side rail, bottom terminal surface, and lighter transition/motion treatment.
• Unified dark/light/auto theming, HarmonyOS Sans typography, and performance-oriented animations.

Screenshots from the current prototype

Home	Workspace thread

Plugin hub	Search overlay

Settings center

Notes for the follow-up PR

• I plan to split the implementation into reviewable pieces instead of one large UI rewrite.
• The PR should include before/after screenshots, validation commands, and performance notes.
• The prototype currently uses browser preview data for some transcript examples; the final desktop PR should keep preview data separate from real desktop bindings.
• I will preserve existing user-visible commands, settings meaning, keyboard shortcuts, and integration behavior.