fix: Align schema compatibility with JSON Schema semantics

- compare const, enum, and numeric constraints by accepted values
- handle exact mixed numeric equality and signed-zero bounds
- apply the validator's default dialect to unevaluated properties

Author: aviator5

Cargo.lock

@@ -183,6 +183,8 @@ chrono = "0.4"
 
 # JSON Schema validation
 jsonschema = { version = "0.40", default-features = false }
+# Exact comparison between differently typed numbers, as used by `jsonschema`.
+num-cmp = "0.1"
 
 # JSON Schema generation
 schemars = { version = "1.2", features = ["uuid1"] }

Cargo.toml

@@ -21,6 +21,7 @@ serde.workspace = true
 serde_json.workspace = true
 thiserror.workspace = true
 jsonschema.workspace = true
+num-cmp.workspace = true
 schemars.workspace = true
 walkdir.workspace = true
 tracing.workspace = true