[Satirito]

What changed

Zed editor and other multi-theme templates define dual appearances (Matugen Dark and Matugen Light) referencing {{colors.role.dark.hex}} and {{colors.role.light.hex}}. Previously, parseMatugenPalette discarded the dark and light buckets and matugenCarrier duplicated the active palette across all three keys (default, dark, light). Consequently, both themes received identical colors, causing broken or inverted styling when wallpapers were light or using smart mode.

This PR:

• Updates parseMatugenPalette to extract active, dark, and light palettes directly from matugen JSON buckets while preserving modeKey priority fallback for the active palette.
• Populates matugenCarrier with separate submaps for default, dark, and light, while maintaining backward compatibility by flattening default entries directly on the role for templates using {{colors.role.hex}}.
• Adds safe ARGB conversion handling when color roles are empty.
• Updates template rendering signatures and caller pipelines accordingly.

Area

ryoku

How it was tested

• Ran go test -v -run "TestMatugen" ./... in ryoku/shell/ipc: all tests pass cleanly (TestMatugenIsolatedDrive, TestMatugenApply, TestMatugenApplyInvokesBinary, TestMatugenApplyNeutralizesAchromaticWallpaper).
• Verified binary compiles without warnings (go build).
• Inspected generated Zed theme and matugen carrier output to confirm distinct background and accent values across dark and light themes.

Checklist

• One logical change, with a clear [area] scope: summary commit subject.
• Matching CHANGELOG.md updated in the area I touched.
• The git hooks pass locally; I did not use --no-verify.
• Lua parses (luac -p), shell scripts pass bash -n, and QML passes qmllint where applicable.
• No duplicated config, no dead code, no commented-out code, no em-dash.
• Docs updated if behavior or layout changed.