Format config schema error locations as JSON Pointers

[Copilot]

The config validator was emitting jsonschema.ValidationError.InstanceLocation values without the leading /, so user-facing paths were not RFC 6901 JSON Pointers. It also fell back to generic guidance for some schema composition/conditional failures instead of surfacing actionable context.

• JSON Pointer formatting

  • Format non-root InstanceLocation values as RFC 6901-style pointers.
  • Preserve <root> for top-level failures.

• Richer schema error guidance

  • Add specific guidance for allOf failures.
  • Add keyword-path fallback dispatch so unhandled concrete error kinds can still map to known guidance for conditional keywords like if, then, and else.

• Focused regression coverage

  • Update existing config error-formatting tests to assert pointer-style locations.
  • Add coverage for allOf messaging and keyword-path fallback behavior.

location := "<root>"
if len(ve.InstanceLocation) > 0 {
	location = "/" + strings.Join(ve.InstanceLocation, "/")
}

• Fixes [go-fan] Go Module Review: santhosh-tekuri/jsonschema/v6 #9686

[Copilot]

Pull request overview

Formats config validation locations as JSON Pointers and adds schema-specific guidance.

Changes:

• Adds leading slashes to validation locations.
• Adds allOf and conditional guidance.
• Expands regression tests.

Show a summary per file

File	Description
internal/config/validation_schema.go	Updates location formatting and error guidance.
internal/config/validation_schema_error_format_test.go	Tests pointer formatting and keyword guidance.

Review details

Tip

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

• Files reviewed: 2/2 changed files
• Comments generated: 2
• Review effort level: Medium