v3.34.1

Fix

SQL passed as sql was missed (#397). mcp-data-server's query tool takes sql_query and register_hex_tiles takes sql, and each accepts the other's name (mcp-data-server#321). Models use both. A query call with {"sql": …} lost its SQL in three places:

• The chat panel's SQL disclosure on the result.
• The agent's per-turn SQL record.
• The exported report, which filed the query under "Consulted". It got no code chunk, and with no runnable query the .R / .py / .qmd / .ipynb download buttons were hidden.

Seen on ca-30x30 with deepseek-v4-flash (v3.34.0).

The cause was four separate copies of the rule for which argument holds the SQL. They now share one, sqlArg() in tool-registry.js: remote tools read sql_query, sql, query, and local tools read sql only. The chat panel no longer shows geocode's place-name query as SQL. test/sql-arg.test.js covers every name against both remote tools at every site, including the export's chunks, download buttons, downloaded files and data-source citations.

Upgrading

No config changes; bump the pin to @v3.34.1.