feat: JSON schemas + editor modelines for module YAML

[ValgulNecron]

Problem

VS Code's YAML extension (redhat.vscode-yaml) auto-guesses a schema from its store and mis-matches template.yaml against the AWS CloudFormation SAM schema, flagging valid fields:

Property apiVersion is not allowed. yaml-schema: AWS CloudFormation Serverless Application Model (SAM)(513)

Fix

Give both module YAML files an explicit $schema so the extension stops guessing — and gets real validation + autocomplete.

• .schema/gametemplate.schema.json — generated from the GameTemplate CRD's openAPIV3Schema (a module template.yaml is a GameTemplate custom resource). Regenerated from the Gameplane repo via make module-schema.
• .schema/module.schema.json — hand-maintained, mirrors docs/module-authoring.md.
• A first-line modeline in every template.yaml/module.yaml:

  # yaml-language-server: $schema=../.schema/gametemplate.schema.json

  The relative ../.schema path resolves whether this repo is opened standalone or as the Gameplane repo's modules/ submodule.

Verification

• Both schemas accept all 16 modules' files (validated locally: every module.yaml key is in the schema, all required present; every template.yaml matches the const apiVersion/kind).
• The modeline is a leading comment, so build.sh's ymv parser still extracts name/version, and validate.py's YAML load is unaffected — .schema/ has no template.yaml, so discover_modules skips it.

Companion

The generator + make module-schema target land in the Gameplane repo; the submodule pointer bump follows once this merges.

Note: curseforgeGameID (added in Gameplane #156) isn't in the generated schema yet — it's regenerated once that CRD change hits main. The schema sets no additionalProperties: false, so it does not flag the field in the meantime.

🤖 Generated with Claude Code