run402-mcp 4.43.0 → 4.44.0

package/README.md

@@ -394,7 +394,10 @@ run402 init
 # 2. Allocate the repo's vault explicitly. Separate from `run402 init` on
 #    purpose: this is the step that mints key material on this machine and
 #    prints a one-shot recovery receipt. Idempotent — an existing vault comes
-#    back deduplicated. (git push / repos snapshot would allocate it lazily too.)
+#    back deduplicated. (Skip this step and git push / repos snapshot
+#    against an unallocated project allocates the SAME way, lazily, on
+#    first use — the two paths don't stack; this one just does it now,
+#    explicitly, so the receipt lands in JSON stdout instead of stderr.)
 run402 repos create --project <id>
 
 # 3. Snapshot — capture the working tree, encrypt it, publish a signed head.
@@ -411,6 +414,8 @@ git clone run402::<org_id>/<project_id> restored
 
 Cloning needs a Run402 principal on this machine — a wallet with an allowance and a keystore holding an envelope for this vault — this is encrypted git, not a shareable link.
 
+A fresh clone may show dangling commits under a plain `git fsck` — that's the vault's retained deploy/capture history, delivered in the pack but not referenced by any local ref. Expected and harmless, not corruption; `git fsck`'s exit status stays clean.
+
 `repos snapshot` is the CAPTURE lane — the protocol deploy ref plus the HEAD target — because a dirty tree captures as a synthetic commit that sits on no branch. Your own branches and tags reach the vault through `git push origin <branch>`.
 
 **Allocating a vault does NOT gate the project's deploys.** `gitvault_policy` stays unset until you set it — a vault created by a first `git push` or `repos create` never silently changes how you deploy. A deploy against a vaulted, ungated project proceeds ungated and its result carries a typed `next_actions` entry offering `run402 repos policy required`; every later ungated deploy carries a `warnings[]` entry naming the drift, until the policy is set either way — never a block, never an interactive prompt. Once `gitvault_policy` is `required`, a deploy must present a vaulted capture at commit — `run402 deploy apply` produces one automatically on any machine holding the keystore; un-gate with `run402 repos policy grandfathered --reason "<why>"` (owner + step-up, audited, reversible with `run402 repos policy required`). Vaulting your source is never gated on a deploy, either way. `run402 doctor` reports the policy, whether this machine can satisfy it, and where the keystore lives.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "run402-mcp",
-  "version": "4.43.0",
+  "version": "4.44.0",
   "packageManager": "npm@11.19.0",
   "mcpName": "com.run402/mcp",
   "description": "MCP server for Run402 — full-stack backend infrastructure for AI agents: Postgres, auth, storage, serverless functions and atomic deploys. Paid with x402/MPP. Includes $0.03 image generation.",