v2.38.1
run402-mcp: clearer SQL feedback + accurate 403 guidance
Patch release. @run402/sdk and run402 (CLI) are version-bumped in lockstep but have no functional changes - both fixes are in the run402-mcp server.
Fixes
run_sqlno longer reports "0 rows returned" for mutations and DDL. It now reflects the gateway's actual row semantics: a result set shows "N rows returned" + table; anINSERT/UPDATE/DELETEshows "N rows affected"; a no-match mutation or empty result shows "0 rows"; DDL (CREATE TABLE/CREATE INDEX, etc.) shows "Statement executed". Previously every mutation and all DDL printed "0 rows returned", which reads to an agent like the statement did nothing - costing redundant verification round-trips.- 403 errors no longer claim "the project lease may have expired" for blocked operations.
FORBIDDEN(blocked SQL such asCREATE ROLE/CREATE SCHEMA/CREATE EXTENSION/GRANT) andADMIN_REQUIRED(e.g.service_roleon/rest/v1/*) now get accurate, code-specific next-step guidance instead of a misleading lease-expiry detour.
Both surfaced while benchmarking the MCP server against the MCPMark benchmark.