@palbase/backend 22.0.0 → 22.0.1

package/docs/README.md

@@ -194,13 +194,18 @@ generated client surface) changes; the verb/path do not affect it.
 - `palbase push` — deploy the current backend to the selected Environment. For a
   GitHub-backed project it runs `git push`; the pushed source Git branch deploys
   to the Environment configured for that branch.
-- `palbase secret set NAME=value` / `palbase secret list` — Environment-scoped
-  secrets (encrypted at rest), read in code via `process.env.NAME`.
-- `palbase secret pull` / `palbase secret push` — sync the selected Environment's
-  variables with a local `.env.local` (gitignored). `pull` writes decrypted
-  values for local dev (merging local-only keys); `push` uploads changed keys
-  (new keys default to SECRET and need `--secret`/`--plain` classification,
-  existing secrets are left untouched unless `--force-secrets`).
+- `palbase secret set NAME=value` (or `set NAME --stdin`, which keeps it out of
+  your shell history) / `palbase secret list` / `palbase secret remove NAME` —
+  Environment-scoped secrets, read in code via `process.env.NAME`. Everything in
+  the vault is sealed: there is no `--secret`/`--plain` classification, and the
+  listing answers names and last-changed times, never values.
+- `palbase run -- <command>` — run something on YOUR machine with the project's
+  secrets in its environment. There is no `.env` file: nothing writes one and
+  nothing reads one, so the values live in one child process and are gone when it
+  exits.
+- `config/secrets.ts` — `defineSecrets({ secrets: [secret("NAME")] })` declares
+  WHICH secrets the backend needs (never a value). `push` refuses the deploy when
+  a required one is missing from the target Environment, naming it.
 - `tsconfig.json` needs `"experimentalDecorators": true` (the scaffold sets it).
 
 ## Mental model

package/docs/llms-full.txt

@@ -202,13 +202,18 @@ generated client surface) changes; the verb/path do not affect it.
 - `palbase push` — deploy the current backend to the selected Environment. For a
   GitHub-backed project it runs `git push`; the pushed source Git branch deploys
   to the Environment configured for that branch.
-- `palbase secret set NAME=value` / `palbase secret list` — Environment-scoped
-  secrets (encrypted at rest), read in code via `process.env.NAME`.
-- `palbase secret pull` / `palbase secret push` — sync the selected Environment's
-  variables with a local `.env.local` (gitignored). `pull` writes decrypted
-  values for local dev (merging local-only keys); `push` uploads changed keys
-  (new keys default to SECRET and need `--secret`/`--plain` classification,
-  existing secrets are left untouched unless `--force-secrets`).
+- `palbase secret set NAME=value` (or `set NAME --stdin`, which keeps it out of
+  your shell history) / `palbase secret list` / `palbase secret remove NAME` —
+  Environment-scoped secrets, read in code via `process.env.NAME`. Everything in
+  the vault is sealed: there is no `--secret`/`--plain` classification, and the
+  listing answers names and last-changed times, never values.
+- `palbase run -- <command>` — run something on YOUR machine with the project's
+  secrets in its environment. There is no `.env` file: nothing writes one and
+  nothing reads one, so the values live in one child process and are gone when it
+  exits.
+- `config/secrets.ts` — `defineSecrets({ secrets: [secret("NAME")] })` declares
+  WHICH secrets the backend needs (never a value). `push` refuses the deploy when
+  a required one is missing from the target Environment, naming it.
 - `tsconfig.json` needs `"experimentalDecorators": true` (the scaffold sets it).
 
 ## Mental model

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@palbase/backend",
-  "version": "22.0.0",
-  "description": "Palbase Backend SDK — class controllers (@Controller/@Get/@Post + @Body/@QueryParams/@Param), error classes, schema DSL",
+  "version": "22.0.1",
+  "description": "Palbase Backend SDK \u2014 class controllers (@Controller/@Get/@Post + @Body/@QueryParams/@Param), error classes, schema DSL",
   "license": "MIT",
   "repository": {
     "type": "git",