Update theme colors for command center and editor widgets

[mrleemurray]

Refine color values for command center and editor widgets in both dark and light themes, enhancing visual consistency and usability. Adjust background colors and add widget borders for improved aesthetics in the 2026 light theme.

[Copilot]

Pull request overview

This pull request refines the visual appearance of the 2026 theme by adjusting color opacity values and border styles for various UI components including the command center, editor widgets, and notifications. The changes aim to enhance visual consistency and usability across both dark and light theme variants.

Changes:

• Increased opacity for several UI elements from various percentages (30%, 40%, 50%, 70%, 75%) to a consistent 60% transparency in CSS
• Updated command center colors in light theme from transparent/semi-transparent to solid colors for better visibility
• Added widget.border color definition to the light theme
• Removed several border: none declarations to allow default borders to show through
• Changed shadow styles from --shadow-hover to --shadow-lg for parameter hints and debug hover widgets

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
extensions/theme-2026/themes/styles.css	Updated color-mix transparency values to 60% for consistency, removed unnecessary border:none rules, added new background colors for command center and breadcrumbs, changed some shadow values
extensions/theme-2026/themes/2026-light.json	Updated command center colors from transparent to solid (#FAFAFD, #F0F0F3), replaced #E8ECF2 with #F0F0F3 throughout for widget backgrounds, removed alpha channels from some borders, added widget.border color
extensions/theme-2026/themes/2026-dark.json	Updated command center colors to darker solid values (#252627 for active, #2E3031 for border), changed editor widget backgrounds from semi-transparent to solid (#202122)

[Copilot]

These two rules apply the exact same background style. The vs-dark specific rule (lines 433-435) is redundant since it applies the same property value as the generic rule (lines 430-431), which already applies to both themes. Consider removing the vs-dark specific rule to reduce duplication.

Suggested change

	.monaco-workbench.vs-dark .breadcrumbs-picker-widget {
	background: color-mix(in srgb, var(--vscode-breadcrumbPicker-background) 60%, transparent) !important;
	}

[Copilot]

These two rules apply the exact same background style. The vs-dark specific rule (lines 352-354) is redundant since it applies the same property value as the generic rule (lines 347), which already applies to both themes. Consider removing the vs-dark specific rule to reduce duplication.

Suggested change

	.monaco-workbench.vs-dark .monaco-editor .peekview-widget {
	background: color-mix(in srgb, var(--vscode-peekViewEditor-background) 60%, transparent) !important;
	}

[Copilot]

These two rules apply the exact same background style. The vs-dark specific rule (lines 259-261) is redundant since it applies the same property value as the generic rule (lines 256-257), which already applies to both themes. Consider removing the vs-dark specific rule to reduce duplication.

Suggested change

	.monaco-workbench.vs-dark .notification-toast-container {
	background: color-mix(in srgb, var(--vscode-notifications-background) 60%, transparent) !important;
	}

[Copilot]

These two rules apply the exact same background style. The vs-dark specific rule (lines 273-275) is redundant since it applies the same property value as the generic rule (lines 270-271), which already applies to both themes. Consider removing the vs-dark specific rule to reduce duplication.

Suggested change

	.monaco-workbench.vs-dark .notifications-center {
	background: color-mix(in srgb, var(--vscode-notifications-background) 60%, transparent) !important;
	}