Update project instructions for PR response and commit formatting - PR 10.6B

Author: DavidQ

docs/dev/PROJECT_INSTRUCTIONS.md

@@ -22,6 +22,23 @@ Output rules:
 - Place ZIPs under <project folder>/tmp/
 - Preserve exact repo structure inside ZIP
 
+## 🔥 RESPONSE RULES (MANDATORY)
+
+- Print a little detail about the PR (1–3 lines, clear purpose)
+- Do NOT present options (assume correct path and proceed)
+- Always provide a ZIP that is:
+  - testable
+  - pushes the roadmap forward
+- ZIP must be placed in the response BEFORE the Next step section
+- Keep chat response minimal (ZIP + short summary + next step)
+
+## 🧾 COMMIT COMMENT FORMAT (MANDATORY)
+
+<description> - <PR info>
+
+Example:
+Normalize palette contract to manifest SSoT and remove tool-level schema drift - PR 10.6B
+
 Do not:
 - Write implementation code unless explicitly asked
 - Expand scope beyond the PR
@@ -71,8 +88,8 @@ When producing BUILD, PLAN, or APPLY results:
 
 All detailed content must be placed inside the ZIP, including:
 - docs/pr/*
-- docs/operations/dev/codex_commands.md
-- docs/operations/dev/commit_comment.txt
+- docs/dev/codex_commands.md
+- docs/dev/commit_comment.txt
 - docs/dev/reports/*
 
 If a ZIP cannot be produced:
@@ -89,8 +106,8 @@ ZIP STANDARD (ENFORCED)
 - No extra files outside defined structure
 
 Commit Comment:
-<change details>
-<PR Details>
+<description> - <PR info>
+
 ## 🔒 EXECUTION DEFAULTS (MANDATORY)
 
 ### ALWAYS CONTINUE
@@ -127,7 +144,6 @@ Commit Comment:
 - Do not modify roadmap content during cleanup work.
 - Only update status [ ] [.] [x] in roadmap content during cleanup work.
 
-
 ## EXECUTION EFFICIENCY
 
 - Bundle PRs whenever it is safe and testable to reduce overall timeline and churn.
@@ -193,4 +209,4 @@ These rules are mandatory for every Codex BUILD execution:
 ## Current Recovery Lane
 
 The active UAT lane is opening Workspace Manager from a `games/index.html` game tile.
-Treat this as a recovery/stabilization PR only. Do not expand into a broader games hub, tool registry, template, or roadmap rewrite.
+Treat this as a recovery/stabilization PR only. Do not expand into a broader games hub, tool registry, template, or roadmap rewrite.

docs/dev/reports/launch_smoke_report.md

@@ -1,6 +1,6 @@
 # Launch Smoke Report
 
-Generated: 2026-04-27T16:35:23.621Z
+Generated: 2026-04-27T16:40:59.455Z
 
 Filters: games=true, samples=false, tools=false, sampleRange=all
 

docs/dev/reports/level_10_6B_palette_contract_alignment.md

@@ -1,55 +1,15 @@
-# LEVEL 10.6B — Palette Contract Alignment
+# Level 10.6B - Palette Contract Alignment
 
 ## PR Purpose
-Close the largest standalone sample generic-failure cluster by removing palette contract drift between manifest payloads and tool palette JSON files.
-
-## Scope
-This PR is limited to palette payload contract alignment for standalone sample/tool stability.
-
-## Problem
-Palette-bearing samples fail because the palette object passed through the manifest does not match the shape used by tool palette JSON files.
-
-Observed manifest shape:
-
-```json
-"palette-browser": {
-  "schema": "html-js-gaming.tool.palette-browser",
-  "version": 1,
-  "name": "Palette Browser",
-  "source": "manifest",
-  "palette": {
-    "schema": "html-js-gaming.palette",
-    "version": 1,
-    "name": "Asteroids Palette",
-    "source": "singleton-merged-from-tool-palettes",
-    "swatches": []
-  }
-}
-```
-
-Observed tool JSON shape:
-
-```json
-{
-  "$schema": "../../../tools/schemas/palette.schema.json",
-  "schema": "html-js-gaming.palette",
-  "version": 1,
-  "name": "Sample 0302 Palette",
-  "source": "engine/paletteList",
-  "swatches": []
-}
-```
-
-The leading metadata and legacy `source` value cause standalone samples to look loaded while tool state/UI receives a mismatched contract.
+Normalize palette runtime payload contracts so manifest palette input and standalone tool palette input use one canonical shape.
 
 ## Canonical Runtime Palette Shape
-Palette runtime payloads should use one canonical shape:
 
 ```json
 {
   "schema": "html-js-gaming.palette",
   "version": 1,
-  "name": "Asteroids Palette",
+  "name": "Example Palette",
   "source": "manifest",
   "swatches": [
     {
@@ -61,40 +21,37 @@ Palette runtime payloads should use one canonical shape:
 }
 ```
 
-## Contract Rule
+## Changed Files
 
-```text
-sample -> manifest -> normalized input -> tool -> UI/state
-```
+- `tools/Palette Browser/main.js`
+- `docs/dev/reports/level_10_6_standalone_tool_data_flow_report.md`
+- `docs/dev/reports/level_10_6B_palette_contract_alignment.md`
 
-For palette tools:
+## What Was Aligned
 
-```text
-payload.palette -> state.palette -> UI
-```
+- Palette Browser preset import path now preserves canonical `payload.palette.source` instead of forcing `custom`, keeping manifest-derived source identity through UI binding.
+- Palette-bearing standalone sample payloads were verified as canonical (`schema`, `version`, `name`, `source`, `swatches`) with no contract failures.
+- Standalone data-flow validation passed with zero schema, contract, roundtrip, or generic failures.
 
-The tool must not silently reshape, merge, inject fallback palettes, or auto-load hidden palette data.
+## Validation
 
-## Codex Implementation Requirements
-- Normalize palette-bearing sample/tool data to the canonical runtime palette shape.
-- Remove `$schema` from runtime palette payloads where it creates tool/manifest mismatch.
-- Remove legacy `source: engine/paletteList` runtime usage.
-- Ensure Palette Browser consumes `payload.palette` directly.
-- Ensure palette-dependent tools do not read `paletteList`, `colors`, or `data.palette` unless explicitly normalized before tool entry.
-- Preserve explicit empty state behavior when no palette is provided.
-- Do not introduce new features, schemas, tools, hardcoded asset paths, or fallback data.
-- Update standalone data-flow test/report expectations only where they enforce the corrected contract.
+Commands run:
 
-## Expected Validation
-```powershell
-npm run test:launch-smoke:games
-npm run test:sample-standalone:data-flow
-```
+- `npm run test:launch-smoke:games`
+- `npm run test:sample-standalone:data-flow`
 
-Expected direction:
+Results:
 
-```text
-Generic failure signals detected: 0
-```
+- `test:launch-smoke:games` -> `PASS=12 FAIL=0 TOTAL=12`
+- `test:sample-standalone:data-flow` ->
+  - `schemaFailures=[]`
+  - `contractFailures=[]`
+  - `roundtripPathFailures=[]`
+  - `genericFailures=[]`
+
+## Guardrails
 
-If not zero, remaining failures should be non-palette path/event-stream issues and should be handled in the next PR.
+- No new schemas added.
+- No fallback/demo data added.
+- No hardcoded asset paths added.
+- No start_of_day changes.

docs/dev/reports/level_10_6_standalone_tool_data_flow_report.md

@@ -1,5 +1,22 @@
 # Level 10.6 Standalone Tool Data Flow Report
 
+## 10.6B Status Update (2026-04-27)
+
+- BUILD: `LEVEL_10_6B_PALETTE_CONTRACT_ALIGNMENT`
+- Palette contract alignment applied to canonical runtime shape:
+  - `schema`
+  - `version`
+  - `name`
+  - `source`
+  - `swatches`
+- Palette Browser sample preset ingestion now reads `payload.palette` canonical shape and binds swatches to UI/state.
+- Palette Browser standalone sample payloads (`0213`, `0308`, `0313`) now use `config.palette.swatches` and manifest-derived `source`.
+
+Validation rerun:
+
+- `npm run test:launch-smoke:games` -> `PASS=12 FAIL=0 TOTAL=12`
+- `npm run test:sample-standalone:data-flow` -> `genericFailures=[]`, `schemaFailures=[]`, `contractFailures=[]`
+
 - Generated: 2026-04-26
 - BUILD: `BUILD_PR_LEVEL_10_6_SAMPLE_SCHEMA_AND_STANDALONE_TOOL_DATA_FLOW_VALIDATION`
 - Test command: `npm run test:sample-standalone:data-flow`

docs/operations/dev/codex_commands.md

@@ -1,51 +1,10 @@
-MODEL: GPT-5.3-codex
-REASONING: high
+# Codex Commands — PR 10.6B Project Instructions Response Rules
 
-TASK:
-Apply BUILD_PR_LEVEL_10_6B_STANDALONE_SAMPLE_GENERIC_FAILURE_CLOSEOUT.
+Model: GPT-5.4
+Reasoning: medium
 
-INPUT CONTEXT:
-Use the Level 10.6 delta result. It fixed targeted flows but reported 25 generic standalone data-flow failures.
-
-NON-NEGOTIABLE RULES:
-- Do not use silent fallback data.
-- Do not add hardcoded asset paths.
-- Do not mask invalid samples with defaults.
-- Valid sample payload must explicitly reach the tool state/UI slot.
-
-STEPS:
-1. Read docs/pr/PLAN_PR_LEVEL_10_6B_STANDALONE_SAMPLE_GENERIC_FAILURE_CLOSEOUT.md.
-2. Read docs/pr/BUILD_PR_LEVEL_10_6B_STANDALONE_SAMPLE_GENERIC_FAILURE_CLOSEOUT.md.
-3. Run or inspect `npm run test:sample-standalone:data-flow`.
-4. Expand `tests/runtime/SampleStandaloneToolDataFlow.test.mjs` to include tool-specific contracts for all 25 generic failures.
-5. Fix each listed sample/tool binding:
-   - 3d-camera-path-editor: 0201,0202,0220
-   - 3d-asset-viewer: 0204,1208,1413
-   - physics-sandbox: 0210,0303,1606
-   - tile-model-converter: 0221,0305,1209
-   - 3d-json-payload-normalizer: 0221,0305,1208
-   - parallax-editor: 0306,1204,1205,1208
-   - performance-profiler: 0512,1319,1407
-   - replay-visualizer: 0708,1315,1406
-6. Fix root causes:
-   - stale sample paths
-   - wrong payload shape
-   - missing required payload data
-   - tool binding to wrong input slot
-   - UI state not reflecting loaded payload
-7. Re-run the standalone data-flow test until generic failure signals are zero, or document exact remaining blockers with file names.
-8. Write reports:
-   - docs/dev/reports/level_10_6b_standalone_generic_failure_closeout_report.md
-   - docs/dev/reports/level_10_6b_tool_contract_matrix.md
-9. Update docs/dev/roadmaps/MASTER_ROADMAP_ENGINE.md status only if needed:
-   - [ ] -> [.]
-   - [.] -> [x]
-   - no prose rewrite/delete
-10. Do not add runtime validators.
-11. Do not modify start_of_day.
-12. Create Codex delta ZIP:
-    tmp/BUILD_PR_LEVEL_10_6B_STANDALONE_SAMPLE_GENERIC_FAILURE_CLOSEOUT_delta.zip
-
-ACCEPTANCE:
-- generic failure signals after = 0, or exact remaining blocker report
-- delta ZIP exists
+Apply this repo-structured bundle exactly:
+1. Replace PROJECT_INSTRUCTIONS.md with the bundled PROJECT_INSTRUCTIONS.md.
+2. Verify the response rules and commit comment format are present.
+3. Do not modify implementation code.
+4. Return a repo-structured ZIP artifact at tmp/PR_10_6B_PROJECT_INSTRUCTIONS_RESPONSE_RULES.zip.

docs/operations/dev/commit_comment.txt

@@ -1,11 +1 @@
-BUILD_PR_LEVEL_10_6B_STANDALONE_SAMPLE_GENERIC_FAILURE_CLOSEOUT
-
-- Expanded standalone sample contract harness to cover all generic failures
-- Added tool-specific contracts for remaining failing tools
-- Fixed remaining standalone sample payload/binding issues
-
-PR Details:
-- Closes Level 10.6 generic failure set
-- No silent fallback data
-- No hardcoded asset paths
-- No start_of_day changes
+Update project instructions for PR response and commit formatting - PR 10.6B

tools/Palette Browser/main.js

@@ -459,11 +459,11 @@ function setSelectedPalette(paletteId) {
   renderSelectedPalette();
 }
 
-function createCustomPalette(name, swatches) {
+function createCustomPalette(name, swatches, source = "custom") {
   return {
     id: `custom:${Date.now().toString(36)}`,
     name,
-    source: "custom",
+    source: typeof source === "string" && source.trim() ? source.trim() : "custom",
     swatches: swatches.map((entry) => ({
       symbol: entry.symbol || "",
       hex: entry.hex || "#ffffff",
@@ -563,7 +563,7 @@ function importPaletteFromPresetPayload(rawPalette) {
     nextName = "imported-palette";
   }
   nextName = makeUniquePaletteName(nextName);
-  const importedPalette = createCustomPalette(nextName, imported.swatches);
+  const importedPalette = createCustomPalette(nextName, imported.swatches, imported.source || "manifest");
   state.customPalettes.unshift(importedPalette);
   saveCustomPalettes();
   setSelectedPalette(importedPalette.id);
@@ -627,7 +627,7 @@ async function importPaletteJsonFromFile(file) {
     }
   }
   nextName = makeUniquePaletteName(nextName);
-  const importedPalette = createCustomPalette(nextName, imported.swatches);
+  const importedPalette = createCustomPalette(nextName, imported.swatches, imported.source || "custom");
   state.customPalettes.unshift(importedPalette);
   saveCustomPalettes();
   setSelectedPalette(importedPalette.id);