Support bundled schemas with custom meta-schemas

[jviotti]

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

[augmentcode]

🤖 Augment PR Summary

Summary: This PR improves support for self-contained/bundled schemas that use custom meta-schemas by allowing embedded meta-schemas to be discovered and preferred during dialect/base-dialect/vocabulary resolution.

Changes:

• Bumps the vendored blaze dependency to a newer revision.
• Adds metaschema_try_embedded to locate a schema’s meta-schema inside the document (via $defs/definitions) and validates the embedded meta-schema chain against an official base dialect.
• Updates metaschema(), base_dialect(), and vocabularies() to prefer embedded meta-schemas over resolver-provided ones when present.
• Extends SchemaFrame to probe/cache embedded meta-schemas during analysis and reuse them for vocabulary resolution.
• Changes SchemaKeywordIterator to take explicit vocabularies (removing resolver/default-dialect dependency) and updates the compiler accordingly.
• Adjusts bundling dependency traversal to report but not recurse into official schemas.
• Adds new CLI regression tests (pass_bundled_metaschema) across fmt/validate/bundle/inspect/compile/codegen/lint/metaschema/test, and removes the install docs warning that required manual dependency ordering.

Technical Notes: Embedded meta-schema precedence aims to make bundled documents self-descriptive, avoiding reliance on external resolver availability for custom dialects.

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

[augmentcode]

Review completed. 2 suggestions posted.

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

[augmentcode]

The docstring for metaschema_try_embedded says it “is null if no valid embedded meta-schema could be found”, but the implementation can throw (e.g., on cycles or missing/invalid $schema while walking the embedded chain). Consider clarifying the API contract here (return-null vs throw-on-invalid) so callers don’t treat it as a non-throwing probe.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

This comment says probed_metaschemas_ only tracks meta-schemas “that the resolver could not resolve”, but SchemaFrame::analyse now checks metaschema_try_embedded before delegating to the resolver (so it can cache embedded meta-schemas even if the resolver would have resolved them). Consider tightening the wording to match the precedence behavior.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}