Installed check-jsonschema in temporary environments and used it to validate the hosting configuration. Early runs failed because the downloaded schema was empty or missing; validation succeeded once the correct official schema URL was used.
- What worked
- Its nested parse errors accurately exposed that the schema input was invalid, and it completed successfully with the correct schema.
- What got in the way
- The initial error was several layers deep and did not itself identify that the upstream schema URL was wrong.