Upgrade Core and Blaze to the latest versions

[jviotti]

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

[cubic-dev-ai]

No issues found across 16 files

[augmentcode]

🤖 Augment PR Summary

Summary: Updates the vendored core and blaze dependencies and adapts jsonschema CLI integration to the latest compiler/frame APIs.

Changes:

• Bumps sourcemeta/core and sourcemeta/blaze revisions in DEPENDENCIES.
• Updates jsonschema validate and jsonschema metaschema to call Blaze compilation with an explicit entrypoint (frame.root()).
• Blaze compiler adds an explicit compilation entrypoint concept, validates that the entrypoint exists, and introduces CompilerInvalidEntryPoint.
• Compilation planning/reachability checks in Blaze are now evaluated relative to the chosen entrypoint.
• Core SchemaFrame refactors reachability computation to be base-relative and caches results per base location.
• AlterSchema’s OrphanDefinitions rule is updated to pass a base location into reachability checks.
• Unevaluated keyword dependency discovery in Blaze is reorganized and vocabulary gating is clarified for 2019-09 vs 2020-12.
• Vendored Blaze drops Node.js packaging metadata (e.g. package.json) and related clang-format inputs.

Technical Notes: The main functional change is that “reachability” (and thus compilation planning / transforms that rely on it) is now evaluated from a specific base/entrypoint instead of being implicitly global.

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

populate_reachability mutates pointer_to_location_ directly, which can leave it only partially populated if this is the first API that touches the frame. Since populate_pointer_to_location() stops once pointer_to_location_ is non-empty, later traverse(const WeakPointer&)/uri(const WeakPointer&) calls may incorrectly return std::nullopt depending on call order.

Severity: high

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

[augmentcode]

This rule now bails out when frame.root() is empty (because frame.traverse(frame.root()) returns nullopt), which can happen for schemas without an explicit identifier/default id (or when analysing non-root paths). If orphan cleanup is expected to work in those scenarios, using frame.root() as the reachability base may skip intended transforms.

Severity: medium

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