Upgrade Core to 6db6600fed02d8b7e1de54e7df340bb1a16ab551

[jviotti]

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

[augmentcode]

🤖 Augment PR Summary

Summary: Bumps vendored sourcemeta/core to 6db6600� and adapts schema transformation rules to a new reframing contract.

Key changes: Updates DEPENDENCIES core SHA; adds reframe_after_transform type trait to mapper and alterschema rules.

Transformer behavior: SchemaTransformer now stores (rule, mutates, reframe) metadata and conditionally re-analyzes the schema frame after each transform.

Looping logic: The main apply loop only restarts when references were rewritten or when a rule requests reframing.

Compatibility: Enforces presence of mutates and reframe_after_transform via static_assert when registering rules.

Intent: Allows rules that don’t require full reframing to avoid extra frame analysis work.

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

This doc example now mentions reframe_after_transform, but the transform override shown later in the snippet doesn’t match the actual virtual signature (transform(JSON&, const Result&)). Consider updating the example so it compiles for readers.

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

[augmentcode]

When reframe_after_transform is false, apply() still uses frame.traverse()/frame.vocabularies() after rule->transform() without rebuilding the frame. Please double-check that all rules opting out can’t invalidate SchemaFrame’s cached state (e.g., by changing subschema structure, resource boundaries, or dialect/vocabulary info), otherwise this can lead to stale frame reads.

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