@mexty/engine-schema

The data contracts of the Mexty game engine, as zod schemas with generated JSON Schema:

• GameDefinitionSchema — a whole game: meta, settings, assets, primitives, player, scene.entities, quests, triggers, hud, completion. A game host block's props are a game definition; validateGameDefinition(value) returns { valid, errors, warnings, definition } with defaults applied and cross-references (aliases, entity ids, objective targets) checked.
• PrimitiveManifestSchema — what a primitive block declares in src/manifest.json.
• EngineAssetManifestSchema — a catalog asset (kind, url, clips, scale, collider hint).
• Vocabularies: ASSET_KINDS, PRIMITIVE_KINDS, BUILTIN_PRIMITIVES, SEMANTIC_CLIPS, CAMERA_MODES, OBJECTIVE_TYPES, EVENT_NAMES, OBJECTIVE_EVENTS; the Action and Condition unions the trigger interpreter runs.
• gameDefinitionJsonSchema() — the JSON Schema committed as a game host's src/props.schema.json, carrying the editor keywords (x-asset, x-primitive, x-entity-ref, x-alias-ref, x-animation, x-engine). Also shipped as dist/game-definition.schema.json.
• chestDemoDefinition — the smallest complete game ("walk to the chest, open it").

No React or three.js dependency: the backend validates with it, the website reads its keywords, the engine renders from it.