Improve error handling on --resolve meta-schema errors

[jviotti]

See: #672
Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[augmentcode]

🤖 Augment PR Summary

Summary: This PR improves user-facing error reporting when importing schemas via --resolve, ensuring meta-schema resolution/validation errors are surfaced with the correct file context.

Changes:

• Wraps additional schema-processing exceptions during --resolve import (SchemaKeywordError, SchemaReferenceError, SchemaResolutionError, and generic SchemaError) as FileError<...> so the CLI can print the originating file path.
• Preserves identifier/value/keyword/location details when available, aligning output with the existing structured error printer.
• Adds new Unix CLI tests covering common --resolve failure modes: unknown metaschema dialect, invalid $id URI, invalid $recursiveRef, and missing core vocabulary in a custom meta-schema.
• Registers the new tests in test/CMakeLists.txt.

Technical Notes: The new test cases validate both human-readable stderr formatting and --json output for the same failures, reducing regressions in error-shaping behavior (see issue #672).

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestions posted.

Comment augment review to trigger a new review at any time.

[cubic-dev-ai]

1 issue found across 6 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/resolver.h">

<violation number="1" location="src/resolver.h:215">
P2: The `catch (const sourcemeta::core::SchemaResolutionError &error)` block will also catch any derived exception types (e.g., `SchemaRelativeMetaschemaResolutionError`) due to C++ exception handling order, causing type slicing when rethrowing as `FileError<SchemaResolutionError>`. This means downstream handlers will see the base type instead of the derived type, potentially showing a misleading "forgot to import using `--resolve/-r`" hint for errors that aren't actually about missing imports. Consider adding a catch block for derived resolution error types *before* this one to preserve the specific error semantics.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}