@kryd/cli 0.1.0 → 0.2.1

package/README.md

@@ -1,6 +1,6 @@
 # @kryd/cli
 
-The command-line client for **[Kryd](https://kryd.eu)** — the effortless **EU-sovereign** deploy stack on Scaleway. Push a React / Vite / Next.js app and seconds later it's live on a real URL with SSL, one-click managed Postgres and object storage, and an EU-hosted AI gateway already wired in. The same instant `git push → live` loop you know from Vercel/Netlify, on infrastructure that is genuinely European — code **and** AI inference stay inside the EU.
+The command-line client for **[Kryd](https://kryd.eu)** — the **European cloud for your AI**. Push a React / Vite / Next.js app and seconds later it's live on a real URL with SSL, one-click managed Postgres and object storage, and an EU-hosted AI gateway already wired in. The same instant `git push → live` loop you know from Vercel/Netlify, on infrastructure that is genuinely European — code **and** AI inference stay inside the EU.
 
 ## Install
 
@@ -10,15 +10,15 @@ npm install -g @kryd/cli      # then use the `kryd` command
 npx @kryd/cli <command>
 ```
 
-Requires Node.js ≥ 22.
+Requires Node.js ≥ 22 and git (the CLI shells out to git for `kryd init` and `kryd push`).
 
 ## Quickstart
 
 ```sh
 kryd login                    # sign in via the browser
 kryd init                     # link this folder to a Kryd project (+ a `kryd` git remote)
-git push kryd main            # build → deploy → live, with a streamed log
-kryd logs                     # follow the linked project's latest deploy
+kryd push                     # push the current branch → build → deploy → live, streamed
+kryd logs                     # follow the linked project's latest deploy (kryd push already does)
 kryd logs <project> --runtime # tail the live app's stdout/stderr
 ```
 
@@ -30,18 +30,20 @@ Once you've run `kryd init` in a directory, the commands below work **arg-less**
 |---|---|
 | `kryd login` / `logout` / `whoami` | Authenticate the CLI (browser flow); the token is stored in `~/.kryd`. |
 | `kryd init` | Link the current repo to a Kryd project + register the deploy webhook + add a `kryd` git remote. |
-| `kryd deploy [project]` | Trigger a deploy of the production branch and follow it live. |
+| `kryd push [branch]` | Push to the `kryd` remote and follow the deploy it triggers (defaults to the current branch). |
+| `kryd deploy [project]` | Re-deploy the production-branch HEAD already on the forge — no new commit. |
 | `kryd logs [target]` | Follow a deploy's build/deploy log (`--runtime` tails the live container instead). |
 | `kryd rollback [project] [deployment]` | Roll back to a previous successful deploy — no rebuild. |
 | `kryd db create \| detach [project]` | Attach / tear down managed Postgres (shared or bring-your-own). |
 | `kryd storage create \| detach [project]` | Attach / tear down S3-compatible object storage. |
+| `kryd env list \| set \| rm [project]` | Manage your own environment variables. `set KEY --stdin` (or a prompt) keeps a secret out of `ps` and your shell history; values are never printed back. Add `--build` for build-time variables (`VITE_*`, `NEXT_PUBLIC_*`) — these are compiled into your public bundle, so they must never be secrets, and they take effect at your next build rather than your next deploy. |
 | `kryd ai enable [project]` | Give the project an authenticated EU AI-gateway endpoint (injected on the next deploy). |
 
 Run `kryd <command> --help` for options. Every project-scoped command accepts an explicit `<project>` id, or resolves it from the `.kryd` link (walking up from the current directory, git-style).
 
 ## Sovereignty
 
-Your application code runs on Scaleway (EU), and the AI gateway routes **only** to Scaleway's EU-hosted models — the wedge is that both your code and your model inference stay inside genuinely European infrastructure. This CLI is the open client; the token you store is a credential and is never printed or bundled into any artifact.
+Your application code runs in the EU, and the AI gateway routes **only** to EU-hosted models — the destination is a compile-time constant, so there is no setting that changes it. The wedge is that both your code and your model inference stay inside genuinely European infrastructure. We name our infrastructure provider on the sub-processor list rather than in the product copy: what we promise is the **jurisdiction** and the **absence of a non-EU code path**, not a particular supplier. This CLI is the open client; the token you store is a credential and is never printed or bundled into any artifact.
 
 ## Links