Use x-format-assertion for the configuration schema

[jviotti]

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

[cubic-dev-ai]

No issues found across 9 files

_{Re-trigger cubic}

[augmentcode]

🤖 Augment PR Summary

Summary: This PR makes configuration-schema format constraints (URI/email/etc.) assertive by introducing and using an x-format-assertion switch.

Changes:

• Bumped Blaze to a revision that can force format assertions per-schema.
• Updated @sourcemeta/jsonschema to a newer version used by the build/test tooling.
• Replaced prior “TODO: Use Format Assertion…” $comment entries with x-format-assertion: true in the configuration-related schemas.
• Extended the configuration schema test suite with negative cases for non-absolute URIs, invalid URI-references, and invalid emails.
• Documented a limitation in the Blaze JavaScript port regarding Format Assertion vocabulary support.

Technical Notes: Blaze’s format compilation logic now treats x-format-assertion: true as enabling assertion behavior even when the global format_assertion tweak is not set, which allows enforcing format under the default 2020-12 “format-annotation” vocabulary.

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

[augmentcode]

Review completed. No suggestions at this time.

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