@madewithremy/admin 0.1.26 → 0.1.27

package/dist/prod.js

@@ -2236,7 +2236,7 @@ function liftFromLive(ctx, params = {}) {
 // src/commands/data.ts
 var dataSpecs = {
   "data lift-from-dev": {
-    usage: "Usage: remy-admin data lift-from-dev <appId> --confirm [--release-id <id>]\nRefusing to run without the exact appId and --confirm: this destructively replaces the live release's databases with a snapshot of dev. Wipes any rows live had \u2014 including signed-up users. Intended for first-publish / pre-launch data sync only.\n--release-id names which of your dev workspaces to lift from, and is required only when you have more than one open (a box and a laptop CLI). The ambiguity error lists the ids.",
+    usage: "Usage: remy-admin data lift-from-dev <appId> --confirm [--release-id <id>]\nRefusing to run without the exact appId and --confirm: this destructively replaces the live release's databases with a snapshot of dev. Wipes any rows live had \u2014 including signed-up users. Intended for first-publish / pre-launch data sync only.\n--release-id names the dev release to lift from; without it, your dev workspace in this app.",
     positionals: [{ name: "appId", required: true }],
     flags: { confirm: { type: "boolean" }, "release-id": { type: "string" } },
     requireAnyOf: {
@@ -2245,7 +2245,7 @@ var dataSpecs = {
     }
   },
   "data lift-from-live": {
-    usage: "Usage: remy-admin data lift-from-live [--truncate] --confirm [--release-id <id>]\nRefusing to run without --confirm: this destructively replaces the dev release's databases with a snapshot of live (wiping local dev data). Live/prod data is never touched. With --truncate it instead empties the dev databases (keeps schema, no data pulled from live).\n--release-id names which of your dev workspaces to overwrite, and is required only when you have more than one open.",
+    usage: "Usage: remy-admin data lift-from-live [--truncate] --confirm [--release-id <id>]\nRefusing to run without --confirm: this destructively replaces the dev release's databases with a snapshot of live (wiping local dev data). Live/prod data is never touched. With --truncate it instead empties the dev databases (keeps schema, no data pulled from live).\n--release-id names the dev release to overwrite; without it, your dev workspace in this app.",
     flags: {
       truncate: { type: "boolean" },
       confirm: { type: "boolean" },
@@ -6481,7 +6481,7 @@ var eventsSpecs = {
     }
   },
   "events publish": {
-    usage: "Usage: remy-admin events publish <channel> <json> [--scope live]\nPublishes exactly as the app's own events.publish would \u2014 same validation, delivery, and metering.",
+    usage: "Usage: remy-admin events publish <channel> <json> [--scope live]\nPublishes exactly as the app's own events.publish would \u2014 same validation, delivery, and metering. Goes to your own dev session unless --scope says otherwise; --scope live reaches real users.",
     positionals: [
       { name: "channel", required: true },
       { name: "json", required: true }
@@ -6568,18 +6568,21 @@ Notes:
   run from a script.
 
   publish lets a frontend subscriber be verified before the backend trigger
-  exists. The response's 'delivered' counts live subscriber connections per
-  published channel \u2014 0 means nobody is listening right now, which is normal,
-  not an error.
+  exists. It goes to YOUR dev session by default (the preview you're building
+  in); pass --scope live to reach real users' browsers. The response's
+  'scope' says where it went, and 'delivered' counts live subscriber
+  connections per published channel \u2014 0 means nobody is listening right now,
+  which is normal, not an error.
 
   channels list is the mismatch-finder: a channel with subscribers but no
   recent publish (or the reverse) usually means the frontend and backend spell
   the channel differently. Window is 24h; channels are exact strings \u2014 there
   are no wildcards anywhere in app events.
 
-  Scopes: events never cross execution environments. --scope defaults to
-  'live'; use 'dev:<devSessionId>' to inspect a tunnel session's world or
-  'preview:<releaseId>' for a branch preview.`;
+  Scopes: events never cross execution environments. tail and channels list
+  default to 'live', publish to your own dev session; use
+  'dev:<devSessionId>' for a dev session's world (a publish prints its own)
+  or 'preview:<releaseId>' for a branch preview.`;
 
 // src/ops/jewels.ts
 var JEWEL_RUN_TIMEOUT_MS = 6e5;
@@ -8181,11 +8184,13 @@ Today the one kind is dedicated retrieval: the app's own vector-store capacity
 for data sources, isolated from the shared pool. Sizes and prices come from the
 platform catalog (\`infra list\` prints them); nothing is priced client-side.
 
-A resource bills by the hour from activation, at the retained-storage rate while
-hibernated, and not at all once destroyed. Provisioning (and growing) needs a
-month's worth of credits available in the workspace, checked before the request
-is accepted; nothing is charged until activation. The provision output prints
-the price it committed to. Every action below is audited.
+A resource bills by the clock hour at the active rate for every hour it is
+active in, including the hour a resume lands in, and costs nothing while
+hibernated or once destroyed. Provisioning, growing and resuming need a month's
+worth of credits available in the workspace, checked before the request is
+accepted (insufficient_credits); nothing is charged until activation. The
+provision output prints the price it committed to. Every action below is
+audited.
 
 Subcommands:
   list        Resources on this app, plus the offerings you can provision
@@ -8193,7 +8198,7 @@ Subcommands:
   logs        The platform's log for a resource (--follow to keep reading)
   provision   Lease a new resource (needs a month's credits; prints the price)
   hibernate   Park it: data kept, searches paused, compute charge stops
-  resume      Bring a hibernated resource back
+  resume      Bring a hibernated resource back (needs a month's credits)
   resize      Change its size, data intact (passes through hibernated)
   destroy     Delete it (refused while data sources are placed on it)
   rename      Change the display name

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@madewithremy/admin",
-  "version": "0.1.26",
+  "version": "0.1.27",
   "description": "Admin SDK + CLI for managing production Remy apps",
   "type": "module",
   "main": "./dist/index.js",
@@ -22,7 +22,6 @@
     "build": "tsup",
     "dev": "tsup --watch",
     "typecheck": "npm run tsc -- --noEmit",
-    "lint:fix": "prettier --write ./src",
     "prepublishOnly": "npm run build",
     "tsc": "node node_modules/@typescript/native/bin/tsc",
     "//tsc": "The native TypeScript 7 compiler by explicit path. It (typescript@7 under the @typescript/native alias) and the JS compiler API behind the `typescript` alias — which tsup's dts step needs — both declare a `tsc` bin, so node_modules/.bin/tsc is whichever npm linked last."
@@ -56,7 +55,6 @@
   "devDependencies": {
     "@types/node": "^25.3.2",
     "@typescript/native": "npm:typescript@^7.0.2",
-    "prettier": "^3.8.1",
     "tsup": "^8",
     "tsx": "^4",
     "typescript": "npm:@typescript/typescript6@^6.0.2"