merge: SQL driver health review findings resolved (Driver.Sql-004/-005/-006/-008/-010)

# Conflicts:
#	docs/drivers/Sql.md

docs/drivers/Sql.md

@@ -80,6 +80,14 @@ the nested form.
 }
 ```
 
+⚠️ **`topByTimestamp` needs an ordering column that is unique per row.** It is executed as an
+`ORDER BY <column> DESC` with the dialect's single-row limit, so when the column ties the server
+returns an arbitrary row among the tied ones — and the driver cannot warn about it, because the other
+rows were discarded before the result set reached it (the `whereColumn`/`whereValue` form *does*
+warn, on `Rows.Count > 1`). A `date`-typed column ties for every row written on the same day, and
+browse-commit will nominate one. Prefer a `datetime2`/sequence column that is unique per row, or
+point the tag at a latest-row view.
+
 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