Description

ExtensionContextValidation could resolve model metadata via runtime-type fallback (ModelInspector.ForType), which breaks with custom model inspectors and mixed/custom type scenarios. This change makes the high-level Validator consistently seed and use ValidationSettings.ModelInspector so downstream validation gets the intended inspector.

• Inspector propagation in Validator

  • Initialize settings.ModelInspector when absent:

    _settings.ModelInspector ??= ModelInfo.ModelInspector;

  • Use _settings.ModelInspector for all high-level ToPocoNode(...) conversions:
    • Validate(Resource ...)
    • Validate(ElementNode ...)
    • external reference resolution conversion path

• Behavioral guardrail

  • Added regression coverage to assert the validator initializes ValidationSettings.ModelInspector when callers provide settings without one.

Related issues

Testing

• Added: ValidatorInitializesModelInspectorOnSettings in ValidatorHighLevelApiTests.