Move JSON schema contracts under tools/schemas

Keeps schema ownership with the tool/workspace system instead of adding root-level schema files. Establishes shared manifest schemas under tools/schemas and tool-specific payload schemas under tools/schemas/tools.

Author: DavidQ

docs/dev/BUILD_PR.md

@@ -0,0 +1,27 @@
+# BUILD_PR: Schema location correction
+
+## Codex task
+Move the schema contract plan from root-level schema files to `tools/schemas/`.
+
+## Required changes
+1. Remove any planned or newly-added root-level `*.schema.json` files.
+2. Add schema contracts under `tools/schemas/` only.
+3. Put reusable manifest schemas directly under `tools/schemas/`.
+4. Put individual tool payload schemas under `tools/schemas/tools/`.
+5. Update any docs or references to point to the new schema paths.
+
+## Do not
+- Do not write broad validation utilities as the primary deliverable.
+- Do not change sample payloads.
+- Do not unlock or mutate samples.
+- Do not create schema files at repository root.
+- Do not modify start_of_day folders.
+
+## Validation command
+Search for misplaced schemas:
+
+```powershell
+Get-ChildItem -Path . -Filter *.schema.json -Recurse | Select-Object FullName
+```
+
+Expected result: all schema files are under `tools\schemas\`.

docs/dev/PLAN_PR.md

@@ -0,0 +1,40 @@
+# PLAN_PR: Move JSON schemas under tools ownership
+
+## Purpose
+Move schema contracts out of the repository root and into the tools area so schema ownership matches the systems that load, edit, validate, and export tool/workspace/sample data.
+
+## Scope
+- Do not change runtime behavior directly.
+- Do not edit locked samples.
+- Do not modify start_of_day folders.
+- Establish schema placement rules for Codex to implement in the next pass.
+
+## Schema placement rule
+Use this structure:
+
+```text
+tools/
+  schemas/
+    workspace.manifest.schema.json
+    tool.manifest.schema.json
+    palette.schema.json
+    sample.tool-payload.schema.json
+    tools/
+      vector-map-editor.schema.json
+      vector-asset-studio.schema.json
+      sprite-editor.schema.json
+```
+
+## Rationale
+Schemas belong near tool contracts, not at repository root. The root should stay clean and should not accumulate validation artifacts.
+
+Shared schemas live at `tools/schemas/`.
+Tool-specific schemas live at `tools/schemas/tools/<tool>.schema.json`.
+
+## Acceptance criteria
+- No new schema files are added at repository root.
+- All JSON schema files are under `tools/schemas/`.
+- Workspace manifest validation uses `tools/schemas/workspace.manifest.schema.json`.
+- Tool manifest validation uses `tools/schemas/tool.manifest.schema.json`.
+- Tool-specific payload validation uses `tools/schemas/tools/<tool>.schema.json`.
+- Samples reference the same tool schema contracts used by tool manifests.

docs/dev/codex_commands.md

@@ -1,73 +1,8 @@
-# BUILD_PR: Codex Execution Notes
+# Codex Commands
 
-## Model
-
-GPT-5.4 or GPT-5.3-codex
-
-## Reasoning
-
-High
-
-## Codex Command
-
-```bash
-codex
-```
-
-## Task
-
-Implement the PLAN_PR in `docs/dev/plan_pr_tool_workspace_schema_manifest_boundaries.md`.
-
-## Constraints
-
-- Smallest valid change.
-- One PR purpose only.
-- Docs-first schema/manifest boundary cleanup.
-- Do not modify `start_of_day`.
-- Do not delete preserved legacy folders.
-- Do not write broad custom validation code where `*.schema` files can define the contract.
-- Preserve existing sample behavior.
-- Samples must use named palettes only and remain locked.
-- Workspaces must use duplicated palettes and enforce used-palette replacement restrictions.
-- Workspace assets must live in `workspace.manifest`; only rendered/exportable artifacts such as PNG files may be saved separately.
-
-## Suggested Implementation Order
-
-1. Inventory only the specific files referencing:
-   - `buildDefaultPayload`
-   - 3D camera path editor payload setup
-   - 3D JSON payload normalizer
-   - viewer asset save/export paths
-   - workspace/sample manifest loading
-   - palette mutation rules
-2. Add schema files near the owning tool or manifest contract.
-3. Wire sample tool payloads to validate/load through the same tool schema.
-4. Wire workspace manifest validation through `workspace.manifest` schema.
-5. Centralize button/action enablement by loaded context:
-   - tool context
-   - workspace context
-6. Add/update minimal tests or fixtures proving:
-   - sample palette lock
-   - workspace palette duplication
-   - used swatch replacement protection
-   - workspace-owned assets persisted in manifest
-   - PNG export still works
-7. Update roadmap/status markers only if the repo has an active roadmap file for this phase.
-
-## Test Commands
-
-Use the repo’s existing test commands. If none exist, run the smallest available smoke checks:
+Model: GPT-5.4-mini
+Reasoning: medium
 
 ```bash
-npm test
-npm run build
+codex exec "Apply BUILD_PR docs/dev/BUILD_PR.md. Keep the change docs-first and schema-location only. Do not add root-level schema files. Place all schema contracts under tools/schemas, with tool-specific schemas under tools/schemas/tools. Do not modify locked samples or start_of_day folders."
 ```
-
-If the repo does not use npm for this area, document the actual commands run in the PR notes.
-
-## Required Output From Codex
-
-- List changed files.
-- List tests run.
-- Note any compatibility shims left in place.
-- Note any old references that were intentionally preserved.

docs/dev/commit_comment.txt

@@ -1,6 +1,3 @@
-Schema-backed tool/workspace manifest boundary cleanup
+Move JSON schema contracts under tools/schemas
 
-- Adds explicit schema contracts for tool/sample/workspace payloads
-- Locks sample palette behavior to named palettes
-- Keeps workspace-owned assets inside workspace.manifest
-- Gates valid UI actions by loaded context
+Keeps schema ownership with the tool/workspace system instead of adding root-level schema files. Establishes shared manifest schemas under tools/schemas and tool-specific payload schemas under tools/schemas/tools.

tests/tools/ToolWorkspaceSchemaManifestBoundaries.test.mjs

@@ -3,21 +3,21 @@ import { readFileSync } from "node:fs";
 import {
   createDefaultCameraPathPayload,
   validateCameraPathPayload
-} from "../../tools/3D Camera Path Editor/cameraPathPayload.schema.js";
+} from "../../tools/schemas/tools/cameraPathPayload.schema.js";
 import {
   createDefaultMapPayload,
   validateMapPayload
-} from "../../tools/3D JSON Payload Normalizer/mapPayload.schema.js";
+} from "../../tools/schemas/tools/mapPayload.schema.js";
 import {
   createDefaultAssetPayload,
   validateAssetPayload
-} from "../../tools/3D Asset Viewer/assetPayload.schema.js";
+} from "../../tools/schemas/tools/assetPayload.schema.js";
 import {
   validateWorkspaceManifestSchema,
   WORKSPACE_MANIFEST_SCHEMA,
   WORKSPACE_MANIFEST_VERSION,
   WORKSPACE_DOCUMENT_KIND
-} from "../../tools/shared/workspaceManifest.schema.js";
+} from "../../tools/schemas/workspaceManifest.schema.js";
 
 export async function run() {
   const cameraValidation = validateCameraPathPayload(createDefaultCameraPathPayload(), {

tools/3D Asset Viewer/main.js

@@ -4,7 +4,7 @@ import {
   ASSET_VIEWER_REPORT_SCHEMA,
   createDefaultAssetPayload,
   validateAssetPayload
-} from "./assetPayload.schema.js";
+} from "../schemas/tools/assetPayload.schema.js";
 
 const refs = {
   inspectButton: document.getElementById("inspect3dAssetButton"),

tools/3D Camera Path Editor/main.js

@@ -4,7 +4,7 @@ import {
   createDefaultCameraPathPayload,
   normalizeCameraPathPayload,
   validateCameraPathPayload
-} from "./cameraPathPayload.schema.js";
+} from "../schemas/tools/cameraPathPayload.schema.js";
 
 const refs = {
   addButton: document.getElementById("addCameraPointButton"),

tools/3D JSON Payload Normalizer/main.js

@@ -4,7 +4,7 @@ import {
   createDefaultMapPayload,
   normalizeMapPayload,
   validateMapPayload
-} from "./mapPayload.schema.js";
+} from "../schemas/tools/mapPayload.schema.js";
 
 const refs = {
   normalizeButton: document.getElementById("normalize3dMapButton"),

tools/schemas/README.md

@@ -0,0 +1,17 @@
+# Tool and Workspace Schemas
+
+All JSON schema contracts for tools, samples, palettes, and workspace manifests belong here.
+
+Root-level schema files should not be added.
+
+## Layout
+
+```text
+tools/schemas/
+  workspace.manifest.schema.json
+  tool.manifest.schema.json
+  palette.schema.json
+  sample.tool-payload.schema.json
+  tools/
+    <tool>.schema.json
+```

tools/schemas/tool.manifest.schema.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "tools/schemas/tool.manifest.schema.json",
+  "title": "Tool Manifest",
+  "type": "object",
+  "required": ["tool", "schema", "data"],
+  "additionalProperties": true,
+  "properties": {
+    "tool": { "type": "string" },
+    "schema": { "type": "string" },
+    "data": { "type": "object" }
+  }
+}