Skip to content

PLAN_PR.md

Latest commit

 

History

History
40 lines (33 loc) · 1.43 KB

PLAN_PR.md

File metadata and controls

40 lines (33 loc) · 1.43 KB

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:

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.