Fix upgrade not correctly handling $vocabulary in 2019-09 to 2020-12

[jviotti]

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

[cubic-dev-ai]

No issues found across 4 files

_{Re-trigger cubic}

[augmentcode]

🤖 Augment PR Summary

Summary: This PR updates the Blaze vendored dependency and fixes JSON Schema upgrade logic from draft 2019-09 to 2020-12 to correctly handle $vocabulary.

Changes:

• Adds a $vocabulary rewrite step during 2019-09 → 2020-12 upgrade, mapping known vocabulary URIs and inlining the 2020-12 unevaluated vocabulary when applicable.
• Extends the “pending pattern” detection to trigger upgrades when $vocabulary needs rewriting.
• Makes parse_vocabularies return nullopt on non-object / non-boolean $vocabulary entries instead of asserting.
• Updates Blaze’s JavaScript README to document the lack of Format Assertion vocabulary support.

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

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

In vendor/blaze/src/foundation/foundation.cc:515, returning std::nullopt for a malformed $vocabulary (wrong type / non-boolean members) makes it indistinguishable from “no $vocabulary present”; callers like vocabularies(...) use .value_or(Vocabularies{}) and may silently fall back to a core-only vocabulary set.

Severity: medium

Other Locations

• vendor/blaze/src/foundation/foundation.cc:521

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