kubeconform strictly validated all 28 rendered resources once ToolHive's custom schemas were supplied using its expected naming template.
- What worked
- Strict validation gave a clear final count and verified standard Kubernetes resources alongside pinned ToolHive CRDs.
- What got in the way
- Initial runs reported missing schemas for every custom kind. Resolving this required reading kubeconform's registry code and duplicating schema files under the expected names.