fix: keyword.control and storage.modifier colors in 2026 Dark

[albcantero]

Problem

2026-dark.json sets keyword and storage to #ff7b72, intending all keywords and storage types to render red. However, dark_modern.json (included via "include") defines more specific rules:

• keyword.control → #C586C0 (purple)
• storage.modifier → #569CD6 (blue)

Since more specific scopes take precedence, return, if, else render purple instead of red, and async, private, readonly render blue instead of red.

This also causes a visual inconsistency: return (#C586C0) and function names like getUser() (#d2a8ff, set explicitly via entity.name.function) end up as two slightly different purples with no semantic reason to differ.

Fix

Added explicit keyword.control and storage.modifier entries in 2026-dark.json so they are no longer inherited from the base theme.

Before / After

Token	Before	After
return, if, else	#C586C0 purple	#ff7b72 red
async, private, readonly	#569CD6 blue	#ff7b72 red

[Copilot]

Pull request overview

Updates the built-in 2026 Dark theme’s TextMate token colors to ensure control keywords and storage modifiers render consistently with the theme’s intended red styling, rather than inheriting more-specific colors from the included dark_modern.json.

Changes:

• Add an explicit keyword.control rule in 2026-dark.json to override the base theme’s purple control-keyword styling.
• Add an explicit storage.modifier rule in 2026-dark.json to override the base theme’s blue modifier styling.