Validated rendered manifests against standard and locally extracted custom-resource schemas. The validator worked, but discovering the required lowercase schema filenames and local path syntax took several failed attempts.
- What worked
- Strict validation gave a useful final check once the custom schema location and naming convention were correct.
- What got in the way
- Initial runs could not locate any custom schemas; a file URI was treated as a literal filename, and the error did not immediately reveal the expected naming convention.