@@ -2,31 +2,14 @@ MODEL: GPT-5.3-codex
22REASONING: medium
33
44TASK:
5- Implement PR 8.3 as a docs-guided, schema-compliant palette generation cleanup.
6-
7- REPO REALITY:
8- - There are no samples/** /config.json files.
9- - There are no samples/** /* .palette.json files in the current layout.
10- - Do not assume either exists.
11- - Generate palette documents from colors actually used by each sample.
12-
13- STEPS:
14- 1 . Read docs/pr/PR_8.3_SAMPLE_COLOR_PALETTE_GENERATION.md.
15- 2 . Read docs/pr/sample_palette_generation_rules.md.
16- 3 . Use workspace.manifest as the source of truth for sample/tool ownership.
17- 4 . Scan sample folders for explicit color values in existing sample JSON and local sample asset metadata.
18- 5 . Generate schema-compliant palette documents from discovered colors.
19- 6 . Add $schema references to generated palette documents.
20- 7 . Validate generated palette documents against tools/schemas/palette.schema.json.
21- 8 . Remove or update any stale docs that refer to nonexistent samples/** /config.json or samples/** /* .palette.json.
22- 9 . Do not add validation utility modules.
23- 10 . Do not modify runtime behavior.
24- 11 . Do not modify start_of_day.
25-
26- ACCEPTANCE:
27- - Generated palettes reflect actual colors used by samples.
28- - No invented colors.
29- - No stale config.json / palette.json assumptions.
30- - No validation utilities added.
31- - No runtime files modified.
32- - No start_of_day files modified.
5+ - Update palette.schema.json:
6+ - entries → swatches
7+ - enforce single-character symbol
8+ - enforce hex format
9+ - Migrate existing/generated palettes:
10+ - entries → swatches
11+ - s001 → single char symbols
12+ - Ensure uniqueness of symbol per palette
13+ - Preserve ordering
14+ - Do NOT add validators
15+ - Do NOT modify runtime
0 commit comments