@vxil/cli 0.4.0 → 0.4.1

package/README.md

@@ -1,6 +1,6 @@
-# vxil
+# @vxil/cli
 
-The [Vxil](https://vxil.com) CLI — config-as-code for backend building blocks you enable in one line.
+The [Vxil](https://vxil.com) CLI — config-as-code for backend building blocks you enable in one line. The package is `@vxil/cli` and it installs the `vxil` command — the bare `vxil` name on npm is blocked, so always install the scoped package.
 
 ```bash
 npx @vxil/cli quickstart          # create a tenant + scaffold vxil.config.ts
@@ -9,24 +9,46 @@ npx @vxil/cli gen                 # generate a typed client + MCP manifest for Y
 npx @vxil/cli functions dev fn    # run a tenant function locally against the remote edge
 npx @vxil/cli listen --forward-to localhost:3000/webhook   # forward inbound webhook events to your local server
 npx @vxil/cli mcp install --client cursor   # wire your backend's MCP server into your editor's agent
-npx @vxil/cli doctor              # sanity-check keys, URLs, reachability
+npx @vxil/cli doctor              # keys, URLs, reachability + secrets referenced-vs-stored + per-function hashes
+npx @vxil/cli diff --against staging   # CI drift gate vs a named slot: exit 0 no drift · 1 drift · 2 error
 ```
 
-Config-as-code lives in `vxil.config.ts`, typed via the bundled `vxil/config` subpath:
+Config-as-code lives in `vxil.config.ts`, typed by `@vxil/config` (also bundled as the `@vxil/cli/config` subpath):
 
 ```ts
 import { defineConfig } from '@vxil/config';
 
 export default defineConfig({
+  // (a) per-feature config — the same typed manifests the server validates
   features: {
-    auth: { enabled: true, methods: ['email_otp'] },
-    cms: { enabled: true, collections: { tasks: { fields: { title: 'text', done: 'boolean' } } } },
-    notifications: { enabled: true, provider: 'resend' },
+    auth: { enabled: true },
+    cms: { enabled: true, draftPublish: true },
+    notifications: { enabled: true, provider: 'resend', fromEmail: 'noreply@example.app' },
+  },
+  // (b) CMS schema-as-code — collections + fields, reconciled by `vxil push`
+  cms: {
+    collections: {
+      tasks: {
+        fields: {
+          title: { type: 'string', required: true, indexSlot: 's1' },
+          done: { type: 'bool' },
+        },
+      },
+    },
   },
 });
 ```
 
-Verbs: `init quickstart push pull diff gen secrets env seed export import functions listen mcp cms dev doctor versions rollback link apply migrate try`.
+Verbs: `init templates quickstart try login link plan push pull diff gen doctor architect versions rollback secrets env seed export import functions listen mcp cms dev payments migrate config users send deliveries api`.
+
+**Every verb names its target.** `--dev` selects the dev slot, `--target <name>` a named slot bound by `vxil link <slug> --as <name>` (which merges into the existing binding rather than replacing it). The selector is **fail-closed** — an unbound slot exits 1 telling you the fix, and never falls through to another tenant — and every write verb prints a target banner (slug + env, never a key) before it acts.
+
+- `vxil plan --explain` — the config plan with every leaf tagged *declared* or *default*.
+- `vxil diff [--against <target>] [--ignore <k,…>]` — the CI drift gate; secrets compared by name only.
+- `vxil doctor` — preflight: secrets referenced-vs-stored (advisory, names only) plus a served / published / local hash verdict per function.
+- `vxil secrets list --all-projects` — the names-and-metadata matrix across every bound project (values never come back).
+- `vxil migrate payments --from-provider stripe|paddle|paypal|revenuecat (--customers <f.csv> | --all) [--dry-run]` — backfill subscriptions through the server sync leg; resumable.
+- `vxil payments simulate --scenario <s> --user <id> [--tier <t>]` — mock/dev projects only: drive a refund pair, cross-platform unlock, renewal, expiry, past-due grace or transfer and check the oracle.
 
 `vxil listen --forward-to <url>` polls your tenant's inbound webhook events and re-POSTs each new one to your local server under the exact delivery contract production uses — same body shape, same signed `X-Vxil-Jobs-Signature` header (your real signing secret) — so the handler you test locally is the handler you ship. `--replay-last <n>` re-forwards recent events; `--raw` posts the stored provider payload alone.
 

package/dist/vxil.js

@@ -32,7 +32,7 @@ function lowerTriggerBindings(trigger) {
   return [{ kind: "http", ...str("path") ? { path: str("path") } : {} }];
 }
 var CONFIG_FILENAMES = ["vxil.config.ts", "vxil.config.mjs", "vxil.config.js"];
-var VXIL_CONFIG_PKG_VERSION = "0.2.0";
+var VXIL_CONFIG_PKG_VERSION = "0.3.0";
 function ensureScaffoldPackageJson(cwd) {
   const file = resolve(cwd, "package.json");
   const spec = `^${VXIL_CONFIG_PKG_VERSION}`;

package/package.json

@@ -1,16 +1,15 @@
 {
   "name": "@vxil/cli",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "private": false,
-  "description": "The vxil CLI (`npx vxil`) — config-as-code (`vxil/config`), typed-client generation, functions deploy, for the whole vxil backend.",
+  "description": "The vxil CLI — init, quickstart, push, gen, secrets, migrate, doctor, diff, functions, payments; installs the `vxil` command (npm i -g @vxil/cli).",
   "license": "MIT",
   "homepage": "https://vxil.com",
   "keywords": [
     "backend",
     "baas",
     "cli",
-    "config-as-code",
-    "cloudflare-workers"
+    "config-as-code"
   ],
   "type": "module",
   "bin": {