Upgrade Core to 421f999a9c14c33233db481f8caa2e062147873e

[jviotti]

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

[augmentcode]

🤖 Augment PR Summary

Summary: This PR upgrades the vendored sourcemeta/core dependency and updates JSON Schema transformation rules to match the new Core API expectations.

Changes:

• Bumped core in DEPENDENCIES to 421f999…
• Added using mutates = std::true_type/false_type; to schema transform rule classes (jsonbinpack mappers and core alterschema rules)
• Extended SchemaTransformer to track whether each rule mutates (vector<pair<rule,bool>>)
• Refactored shared framing + rule-checking into helpers (analyse_frame, check_rules)
• Updated SchemaTransformer::apply to run mutating rules in the main loop and run non-mutating rules as a final check
• Adjusted rule removal logic to account for the new rule storage structure

Technical Notes: SchemaTransformer::add now requires a T::mutates type alias and uses it to decide whether a rule participates in mutation vs. final lint-style checks.

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

SchemaTransformer::apply no longer catches SchemaAbortError, but SchemaTransformRule::transform still throws by default; this means a misclassified/partial rule (or a rule that intentionally aborts) will now throw out of apply instead of reporting via callback/result.first. Is this exception-propagation change intended for callers of apply?

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

[augmentcode]

The comment says that if transform isn’t overridden the rule is “considered to not mutate the schema”, but the default SchemaTransformRule::transform implementation still throws SchemaAbortError. This seems like a contract/docs mismatch that could confuse implementers of new rules.

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