Rename the Color singleton to avoid the Qt 6.12 clash

docs/shell.md

@@ -9,7 +9,7 @@ plugin, so summoning a panel is an IPC call into a process that is already up.
 ```
 shell/
   shell.qml            entry point
-  Commons/             Style, Color, Border, Util
+  Commons/             Style, Colors, Border, Util
   Ui/                  shared components
   services/            plugin registry, bar widget registry, app library
   plugins/

docs/themes.md

@@ -22,7 +22,7 @@ Named keys are preferred: `background`, `foreground`, `accent`, `muted`,
 `color0`..`color15` form also works and is resolved through the same cascade:
 `color0` is the background, `color4` is blue, `color5` is magenta.
 
-That cascade lives in `blob-theme-color`, and `Commons/Color.qml` mirrors it so
+That cascade lives in `blob-theme-color`, and `Commons/Colors.qml` mirrors it so
 the shell and the CLI never disagree about what a slot means.
 
 ## Templates

docs/widgets.md

@@ -29,9 +29,9 @@ repeating literals.
 
 The CSS was written against pywal's `@color0`, `@color4` and `@color5` aliases.
 `blob-theme-color` resolves `color4` to blue and `color5` to magenta, so
-`Commons/Color.qml` now exposes `blue` and `magenta` with that same cascade,
+`Commons/Colors.qml` now exposes `blue` and `magenta` with that same cascade,
 falling back to `accent` for themes that define neither. `color0` is
-`background`, which Color already had.
+`background`, which Colors already had.
 
 ## Quick settings tabs