validate_registry

Overview ¶

Command validate_registry checks every providers/*.json against the runtime schema before the publish workflow uploads to GitHub Pages.

Without this step a malformed config (e.g. forgotten field after a schema change, accidental file rename, a non-HTTPS endpoint that slipped past code review) would ship to clients and get silently rejected six hours later when refreshFromRemote runs. Failing the CI job here keeps the bad file off the registry.

Usage:

go run ./cmd/validate_registry providers/

Exits non-zero on the first invalid file, with a diagnostic naming the offending file and the schema rule it violated.