chore: revert premature version bump (publish workflow bumps on release)

The previous commit bumped versions to 2.16.0 directly. The OIDC publish
workflow does its own bump based on the root package.json version, so a
manual pre-bump would cause `bump=minor` to produce 2.17.0 instead of
the intended 2.16.0. Revert so the workflow produces the right version.

CHANGELOG already names 2.16.0 as the target — no doc change needed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: MajorTal

cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "run402",
-  "version": "2.16.0",
+  "version": "2.15.3",
   "description": "CLI for Run402 — provision Postgres databases, deploy static sites, generate images, and manage wallets via x402 and MPP micropayments.",
   "type": "module",
   "bin": {

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "run402-mcp",
-  "version": "2.16.0",
+  "version": "2.15.3",
   "description": "MCP server for Run402 — AI-native Postgres databases with REST API, auth, storage, and row-level security. Pay with x402 USDC micropayments.",
   "type": "module",
   "main": "dist/index.js",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@run402/sdk",
-  "version": "2.16.0",
+  "version": "2.15.3",
   "description": "Typed TypeScript client for the Run402 API. Kernel shared by the run402-mcp server, the run402 CLI, and user-deployed run402 functions.",
   "type": "module",
   "main": "dist/index.js",