PR 8.14: Normalize palette naming

- Removed tool-specific palette files
- Enforced single canonical palette per sample
- Preserved palette data via merge

PR 8.15: Naming convention standardization

- Clarified difference between tool payload and palette data files
- Locked naming conventions for future consistency
- No file changes required

Author: DavidQ

docs/dev/codex_commands.md

@@ -1,39 +1,20 @@
 MODEL: GPT-5.3-codex
-REASONING: medium
+REASONING: low
 
 TASK:
-Apply PR 8.13 palette naming and deep reference cleanup.
+Document-only PR.
 
-STEPS:
-1. Rename all sample palette files:
-   - from sample.palette.json
-   - to sample.<id>.palette.json
-   where <id> matches the sample folder id.
-2. Remove all sample.palette.json files after rename.
-3. Update palette JSON $schema relative paths only if needed after rename.
-4. Move lock/source metadata from tool payloads into the matching palette JSON:
-   - paletteRef.source -> palette.source
-   - paletteRef.id -> palette.sourceId
-   - paletteRef.locked -> palette.locked
-5. Remove palette-related fields from every sample tool payload file:
-   - palette
-   - paletteRef
-   - assetRefs.paletteId
-6. If assetRefs becomes empty after paletteId removal, remove assetRefs.
-7. Specifically fix:
-   - samples/phase-02/0207/sample.0208.sprite-editor.json
-   and audit whether the 0208 file name in 0207 folder is a mismatch. Correct to sample.0207.sprite-editor.json if repo conventions confirm it.
-8. Update tools/schemas/palette.schema.json to allow optional top-level:
-   - sourceId
-   - locked
-9. Do NOT add runtime logic.
-10. Do NOT add validators.
-11. Do NOT modify start_of_day.
+- Do NOT rename files
+- Do NOT modify payloads
+- Do NOT modify runtime
+
+Verify:
+- sample.<id>.<tool>.json are tool payloads
+- sample.<id>.palette.json are palette data files
+
+Ensure:
+- no new invalid naming patterns introduced
 
 ACCEPTANCE:
-- sample_tool_files_with_palette_key=0
-- sample_tool_files_with_paletteRef_key=0
-- sample_tool_files_with_paletteId_key=0
-- sample.palette.json files remaining=0
-- all palette files named sample.<id>.palette.json
-- locked/sourceId live only in palette JSON
+- Naming rules clearly documented
+- No file changes required

docs/dev/commit_comment.txt

@@ -1,6 +1,5 @@
-PR 8.13: Clean palette refs and rename palette files
+PR 8.15: Naming convention standardization
 
-- Renamed sample palettes to sample.<id>.palette.json
-- Removed embedded palette refs from sample tool payloads
-- Moved locked/source metadata into palette JSON
-- Allowed palette sourceId and locked metadata in schema
+- Clarified difference between tool payload and palette data files
+- Locked naming conventions for future consistency
+- No file changes required

docs/pr/PR_8.14_PALETTE_NAMING_NORMALIZATION.md

@@ -0,0 +1,66 @@
+# PR 8.14 — Palette Naming Normalization
+
+## Problem
+Duplicate palette files exist:
+- sample.0213.palette.json
+- sample.0213.palette-browser.json
+
+This creates ambiguity and violates the “single palette per sample” rule.
+
+## Decision
+
+### Tool Files
+Keep full tool names:
+- sample.<id>.<tool>.json (GOOD)
+
+### Palette Files
+Palette is NOT tool-specific.
+
+Palette is:
+- shared across tools in the sample
+- passed separately at runtime
+
+### FINAL RULE
+
+There must be EXACTLY ONE palette file per sample:
+
+```
+sample.<id>.palette.json
+```
+
+## Required Fix
+
+For every sample folder:
+
+1. KEEP:
+   sample.<id>.palette.json
+
+2. REMOVE:
+   any tool-specific palette files:
+   - sample.<id>.palette-browser.json
+   - sample.<id>.sprite-editor.palette.json
+   - any variation with tool name
+
+3. If tool-specific palette contains unique data:
+   - merge into canonical palette file BEFORE deletion
+
+## Why
+
+- Palette is shared resource
+- Tool payloads are isolated
+- Matches runtime contract:
+  open(toolPayload, paletteObject)
+
+## Rules
+
+- One palette per sample
+- Palette never includes tool name
+- Tool files always include tool name
+- No duplicate palette variants
+
+## Acceptance
+
+- Only one palette file per sample folder
+- No files matching:
+  sample.<id>.*palette*.json except canonical
+- All palette data preserved via merge if needed

docs/pr/PR_8.15_NAMING_CONVENTION_STANDARDIZATION.md

@@ -0,0 +1,79 @@
+# PR 8.15 — Naming Convention Standardization
+
+## Purpose
+Eliminate confusion between:
+- tool payload files
+- palette data files
+
+Clarify naming so humans can instantly understand file purpose.
+
+## Current State (Valid but Confusing)
+
+- sample.0213.palette-browser.json  ✅ (tool payload)
+- sample.0213.palette.json          ✅ (palette data)
+
+These are BOTH correct, but visually similar.
+
+## Final Naming Model
+
+### Tool Payload Files (UNCHANGED)
+```
+sample.<id>.<tool>.json
+```
+
+Examples:
+- sample.0213.palette-browser.json
+- sample.0207.sprite-editor.json
+
+### Palette Data Files (UNCHANGED NAME, BUT REDEFINED ROLE)
+```
+sample.<id>.palette.json
+```
+
+This is NOT a tool.
+
+## Key Clarification
+
+"palette-browser" is a TOOL  
+"palette" is DATA
+
+## New Rule (IMPORTANT)
+
+### Tool Payload Detection Rule
+A file is a TOOL PAYLOAD if:
+- it contains `"tool": "<tool-name>"`
+
+### Palette File Detection Rule
+A file is a PALETTE if:
+- `$schema` = palette.schema.json
+- contains `"swatches"`
+
+## Human-Readable Rule
+
+If filename has 3 segments:
+- sample.0213.X.json → TOOL
+
+If filename has 2 segments:
+- sample.0213.palette.json → DATA
+
+## Forbidden Future Patterns
+
+Do NOT create:
+- sample.<id>.palette-browser.palette.json
+- sample.<id>.palette-data.json
+- sample.<id>.colors.json
+
+## Optional (NOT REQUIRED NOW)
+
+Future improvement (DO NOT IMPLEMENT IN THIS PR):
+```
+sample.<id>.data.palette.json
+```
+
+But current naming is ACCEPTED and LOCKED.
+
+## Acceptance
+
+- No renaming required (repo already compliant)
+- Naming rules documented
+- No ambiguity for future contributors