fix: address review feedback on color palette

Remove turborepo references from JSDoc and test.
Test now validates palette properties (no bg/white/grey/black/red
colors) instead of asserting a specific color list.

Author: GermanJablo

lib/prefix-color-selector.spec.ts

@@ -181,7 +181,7 @@ describe('#ACCEPTABLE_CONSOLE_COLORS', () => {
         expect(PrefixColorSelector.ACCEPTABLE_CONSOLE_COLORS.length).toBeGreaterThan(1);
     });
 
-    it('uses the same colors and order as turborepo', () => {
+    it('only includes colors that are visually distinct, semantically neutral, and lightweight', () => {
         expect(PrefixColorSelector.ACCEPTABLE_CONSOLE_COLORS).toEqual([
             'cyan',
             'magenta',

lib/prefix-color-selector.ts

@@ -66,10 +66,10 @@ export class PrefixColorSelector {
     /**
      * Colors used by `auto` selection and default cycling.
      *
-     * Matches turborepo's palette: cyan, magenta, green, yellow, blue.
-     * These are visually distinct on both dark and light terminal backgrounds
-     * without carrying semantic meaning (unlike red → errors) or blending
-     * into the default text color (unlike white/grey).
+     * Each color is chosen to be visually distinct on both dark and light
+     * terminal backgrounds, without carrying semantic meaning (e.g. red
+     * implies errors) or blending into default text (e.g. white/grey).
+     * Background colors are excluded to keep output lightweight.
      *
      * This list does NOT restrict manually specified colors — any valid Chalk
      * color name, hex value, or modifier can be passed via `--prefix-colors`.