v0.2.6

Release 0.2.6

Refuse a decimal on the ingest path that silently corrupts it

ingestMany binds DECIMAL through @tdengine/websocket's stmt2, which stores
unrelated memory instead of the value: '61.99' into DECIMAL(20,10) read back as
-4268664320557975669762473403.2597208778, and a different number on every run.
Measured against a live server, then reproduced through the connector's own API
with no eon code in the path — so there is nothing here to fix, and 3.5.0 is
the newest release there is.

A wrong price that inserts without complaint is the worst outcome available.
That path now refuses, naming the column and pointing at ingestSql, which was
measured to round-trip the digits exactly. ingestSchemaless already refused a
decimal on its own. A super-table without a decimal is untouched.

The live suite pins all three.

---

Changes since v0.2.5.