merge: SQL contracts review findings resolved (Driver.Sql.Contracts-001 scalar keyValue, -002 fleet-wide numeric-enum rejection)

docs/drivers/Sql.md

@@ -80,8 +80,13 @@ the nested form.
 }
 ```
 
-`whereValue` may be authored as a JSON string, number or boolean (it is bound as a parameter either
-way). `keyValue` on the `KeyValue` model must be a **string**.
+Both value-bearing fields — `whereValue` here and `keyValue` on the `KeyValue` model — may be
+authored as a JSON string, number or boolean, and are captured as text. They are **bound as
+parameters** either way, and matched back as text (the key cell is stringified), so a key column
+that holds an INTEGER station id can be authored either `"7"` or `7`. A JSON object, array or `null`
+is not a value and is refused. (They were read asymmetrically until 2026-08-10, so a numerically
+authored `keyValue` refused the tag while the identically-bound `whereValue` was served — and the
+deploy gate reported the key as *missing* when it was right there in the blob.)
 
 ### `Query` — deferred to P3