Upgrade Sourcemeta dependencies

[jviotti]

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

[cubic-dev-ai]

No issues found across 9 files

[augmentcode]

🤖 Augment PR Summary

Summary: Updates vendored Sourcemeta dependency pins (core/blaze/jsonschema) to newer revisions and incorporates corresponding upstream vendor code changes.

Changes:

• Bumped core, blaze, and jsonschema versions/revisions (including jsonschema 14.13.3 → 14.13.4) in dependency manifests.
• Vendored core: refactored JSON Schema bundling to determine behavior from base_dialect(), added definitions_keyword(), and added logic to elevate embedded resources from remote schemas into the bundle container.
• Vendored core alterschema: UnknownKeywordsPrefix now tracks renames and rebases references after keyword prefixing.
• Vendored jsonschema: adjusted JSON input enumeration to sort results deterministically per entry/config and improved resolver error wrapping for additional schema exception types.
• Fixed resolver duplicate-identifier detection to compare against the actual embedded subschema being registered.

Technical Notes: Bundling behavior for older drafts now hinges on the resolved base dialect and a computed embedded-schema container keyword, with standalone schemas short-circuiting before bundling.

_{🤖 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]

bundled.contains(identifier_string) doesn’t necessarily mean an equivalent resource is already embedded under root_container (e.g., bundled also tracks “seen/mapped” identifiers and can map an identifier to a different effective id). In that case this branch will still erase the embedded $defs/definitions entry without any conflict check, which could silently drop a non-identical embedded resource.

Severity: medium

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

[augmentcode]

This changes ordering from a single global sort of result to per-argument segment sorts; if downstream relies on globally sorted traversal (independent of the user’s argument order), this could be a behavioral change. Worth confirming the new grouping-by-argument ordering is intentional for CLI determinism/UX.

Severity: low

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