Upgrade Core to fe450b982907f99e542a0cfc78bc60d2b600ff7a

[jviotti]

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

[augmentcode]

🤖 Augment PR Summary

Summary: This PR updates the vendored sourcemeta/core dependency to commit fe450b9 and adapts local code to match the updated Core APIs.

Changes:

• Bumped the Core dependency revision in DEPENDENCIES.
• Updated IR compilation’s schema canonicalization callback signature to include the new boolean parameter.
• Adjusted JSON Pointer hashing to better incorporate property hashes (including 128-bit-capable hashing paths).
• Improved token equality semantics to optionally short-circuit comparisons when a “perfect” hash is available.
• Refactored SchemaFrame analysis to cache standalone state, and updated reachability to better account for dynamic anchors by fragment.
• Changed JSON Schema wrap API to use SchemaFrame/Location and added base-pointer reporting for wrapper results.
• Extended schema transformer callbacks to include a mutability/applied boolean and wired it through check/apply paths.

Technical Notes: The upgrade introduces API signature changes (callbacks + wrap) and subtle behavioral changes in hashing and reference reachability that may affect downstream consumers and tests.

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

reinterpret_cast<const std::uint64_t *>(&hash.a) risks strict-aliasing UB (and can also accidentally read into padding/adjacent fields depending on hash_type layout), which could miscompile the Hasher and break unordered container lookups.

Severity: high

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

[augmentcode]

wrap(..., WeakPointer &base) appends to base and doesn’t clear/set it on the early-return paths; if a caller reuses a non-empty base, it can retain stale segments or accumulate extra ones across calls.

Severity: medium

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