Fix various misc validation issues on edge cases

DEPENDENCIES

@@ -1,5 +1,5 @@
 vendorpull https://github.com/sourcemeta/vendorpull 1dcbac42809cf87cb5b045106b863e17ad84ba02
-core https://github.com/sourcemeta/core 367f6ef45c8e8f05269d65d98dab155505f39ccb
-jsonbinpack https://github.com/sourcemeta/jsonbinpack 183f333e0e032ebf0a397b5d66ed504c44a0a59f
-blaze https://github.com/sourcemeta/blaze 9d13de453c340797d3214dc12e7d9382f7f3fb47
+core https://github.com/sourcemeta/core 6bbc7a8850da0ad72cd2b2badfc33033a4e48be1
+jsonbinpack https://github.com/sourcemeta/jsonbinpack aa6fb7ae6addfe7d7de1f7f49e8f1bbf9652f5ee
+blaze https://github.com/sourcemeta/blaze 49ff4cd2893d52970154a7eea5a729671a9f630a
 ctrf https://github.com/ctrf-io/ctrf 93ea827d951390190171d37443bff169cf47c808

test/codegen/fail_unsupported_keyword_value.sh

@@ -10,7 +10,7 @@ trap clean EXIT
 cat << 'EOF' > "$TMP/schema.json"
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "type": "foo"
+  "type": 1
 }
 EOF
 
@@ -19,10 +19,8 @@ EOF
 # Not supported
 test "$EXIT_CODE" = "3"
 
-# TODO: This error message is pretty bad. Can we do better somehow?
-
 cat << EOF > "$TMP/expected.txt"
-error: Unsupported type value
+error: Expected a string value
   at keyword type
   at file path $(realpath "$TMP")/schema.json
   at document location ""
@@ -38,7 +36,7 @@ test "$EXIT_CODE" = "3"
 
 cat << EOF > "$TMP/expected.txt"
 {
-  "error": "Unsupported type value",
+  "error": "Expected a string value",
   "keyword": "type",
   "filePath": "$(realpath "$TMP")/schema.json",
   "location": ""