Handle wrapped jsonschema validation errors in config schema formatting

[Copilot]

formatSchemaError only recognized direct *jsonschema.ValidationError values, so wrapped schema errors were downgraded to the generic error path and lost location/cause diagnostics. This change makes schema error formatting resilient to wrapping while preserving existing output behavior for direct and non-schema errors.

• Schema error unwrapping

  • Switched formatSchemaError from direct type assertion to errors.As when detecting *jsonschema.ValidationError.
  • Preserves rich formatting (instance location, recursive causes, docs footer) even when validation errors are wrapped.

• Targeted regression coverage

  • Added a focused test case for a wrapped jsonschema.ValidationError to ensure the detailed formatting branch is used.

var ve *jsonschema.ValidationError
if errors.As(err, &ve) {
    formatValidationErrorRecursive(ve, &sb, 0)
    rules.AppendConfigDocsFooter(&sb)
}

[Copilot]

Pull request overview

This PR improves config JSON Schema validation error formatting by ensuring wrapped *jsonschema.ValidationError instances still receive the detailed, location-aware formatting (including recursive causes and the docs footer), instead of falling back to the generic error string path.

Changes:

• Updated formatSchemaError to detect *jsonschema.ValidationError via errors.As (handles wrapped errors).
• Added a regression test covering a wrapped jsonschema.ValidationError to ensure detailed formatting is preserved.

Show a summary per file

File	Description
internal/config/validation_schema.go	Switches schema error detection to errors.As so wrapped validation errors keep rich formatting output.
internal/config/validation_schema_error_format_test.go	Adds a targeted test that wraps a ValidationError and asserts the detailed formatting branch is used.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0