chore: bump version to 1.38.0 + guard publish skill against non-main branches

Catches main up to the v1.38.0 release that was published to npm from a feature branch. Also adds a hard-stop in the /publish skill if HEAD is not `main` or if main is behind origin, so the same mistake can't happen again.

The v1.38.0 tag will be moved to this commit so it's reachable from main.

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

Author: MajorTal

.claude/commands/publish.md

@@ -2,9 +2,10 @@ Publish all three packages in this monorepo. Run each step in order, stopping on
 
 ## Pre-publish checks
 
-1. Make sure the working tree is clean (`git status`). If there are uncommitted changes, stop and tell the user.
-2. Run the full test suite: `npm test`. If any test fails, stop and tell the user.
-3. Run the build: `npm run build`. If it fails, stop and tell the user.
+1. **Verify you are on `main` and in sync with `origin/main`.** Run `git rev-parse --abbrev-ref HEAD` — if the output is not `main`, **STOP IMMEDIATELY**. Do not run tests, do not run the build, do not bump the version. Tell the user: "You're on branch `<branch>`, not `main`. Releases must be cut from `main` so the tag matches the published commit and the private-repo docs deploy picks it up. Merge the branch first, then re-run `/publish`." Do not offer to switch branches or merge for them — just stop. Then run `git fetch origin main && git rev-list --count HEAD..origin/main` — if non-zero, stop and tell the user `main` is behind `origin/main` and needs a pull.
+2. Make sure the working tree is clean (`git status`). If there are uncommitted changes, stop and tell the user.
+3. Run the full test suite: `npm test`. If any test fails, stop and tell the user.
+4. Run the build: `npm run build`. If it fails, stop and tell the user.
 
 ## Version bump
 

cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "run402",
-  "version": "1.37.0",
+  "version": "1.38.0",
   "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": "1.37.0",
+  "version": "1.38.0",
   "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",