Acceptance Criteria
- A JSON Schema is generated from the universal token contract and published at a stable path/URL
- A JSON preset declaring
"$schema": "…" validates against it, with editor autocomplete - The preset-pack scaffold seeds
$schema in its example preset (WORK-448/WORK-456) - The schema is regenerated/checked in CI so it tracks the token contract (no drift)
Approach
Derive the schema from the typed token contract in packages/types (codegen from the TS types, or a hand-maintained schema with a CI drift check). Keep it the single source editors and the validator (WORK-459) reference.
Dependencies
- WORK-456 — the pack format
References
- SPEC-111 §6; SPEC-048 (universal token contract)