@farthershore/cli 0.25.0 → 0.27.0

package/README.md

@@ -123,8 +123,8 @@ Run `farthershore <group> --help` for the full flag set of any command.
 ### `farthershore init`
 
 Scaffold a starter business repo locally from a named plan preset. Each preset
-fills in a single decorated `business/business.ts` (one `@Business` class
-with `@Meter`/`@Feature`/`@Plan` members) and creates the matching customer
+fills in a functional `business/business.ts` using `fs.requests()`,
+`fs.route()`, `fs.plan()`, and a default `fs.business()` export, then creates the matching customer
 `frontend/` project, repo-local `business/package.json`, `business/tsconfig.json`,
 and `.gitignore`.
 
@@ -147,9 +147,9 @@ farthershore init --template starter --surface frontend --surface agent
 | `prepaid` | $50 one-time signup credit, then pay-as-you-go               |
 | `metered` | Pure pay-as-you-go at $0.001/request                         |
 
-After `init`, edit the `@Business({ name, origin })` decorator — `origin` is the
-business-logic destination FartherShore calls for customer-facing actions — and
-add `@Meter`/`@Feature`/`@Plan` members to grow the business. Pass repeatable
+After `init`, add functional meter, route, group, and plan declarations to grow
+the business. Configure the platform-owned upstream origin separately.
+Pass repeatable
 `--surface <frontend|api|docs|widget|dashboard|webhook|worker|agent>` to seed a
 specific shape; omitting it keeps the default `frontend + api` starter. Run
 `npm install` in `business/`, then `farthershore build` from the repo root to
@@ -295,7 +295,7 @@ farthershore plan migrate weather-api pro --from 1 --to head --policy next_renew
 ### `farthershore frontend`
 
 Managed Frontend Hosting operations plus a local preview. `deploy`, `status`,
-`rollback`, and `env` operate the hosted build; `preview` runs the generated
+and `rollback` operate the hosted build; `preview` runs the generated
 `frontend/`'s `vite dev` with an injected `window.__FS_CONFIG__` shim so the
 portal renders locally exactly as it serves in production. Pass `--mock` to
 inject `{ mock: true }` instead of Core/Clerk config for local page inspection
@@ -305,8 +305,6 @@ with placeholder data and auth bypassed.
 farthershore frontend status weather-api --format json
 farthershore frontend deploy weather-api --format json
 farthershore frontend rollback weather-api --release-id <hash> --format json
-farthershore frontend env list weather-api --format json
-farthershore frontend env set weather-api VITE_PUBLIC_FOO bar --target BUILD --format json
 
 # Local preview (shells out to vite; needs a frontend/ project)
 farthershore frontend dev                            # hot-reloading dev server, mock mode by default
@@ -349,23 +347,26 @@ Use `consumer list` first to find a `subscriberId`. `block` suspends a user and
 revokes active API keys. `remove` is irreversible and tears down subscriber state
 across billing, edge credentials, and subscriptions.
 
-### `farthershore secret`
+### `farthershore variables`
 
-Manage private business secrets. Values are encrypted at rest; list/read
-responses return metadata only.
+Manage write-only private secrets with one exclusive delivery phase. `BUILD`
+values enter only the isolated managed build and are leak-scanned from its
+artifact. `RUNTIME` values stay out of builds and are injected only by Gateway
+for compiled, granted integrations.
 
 ```bash
-farthershore secret list weather-api --format json
-printf '%s' "$CLERK_SECRET_KEY" | farthershore secret set weather-api \
-  CLERK_SECRET_KEY --from-stdin --target RUNTIME --format json
-farthershore secret delete weather-api CLERK_SECRET_KEY --yes --format json
+farthershore variables list weather-api --format json
+printf '%s' "$SENTRY_AUTH_TOKEN" | farthershore variables set weather-api \
+  SENTRY_AUTH_TOKEN --delivery build --format json
+printf '%s' "$POSTHOG_SECRET" | farthershore variables set weather-api \
+  POSTHOG_SECRET --delivery runtime --format json
+farthershore variables revoke weather-api POSTHOG_SECRET --yes --format json
+farthershore variables rm weather-api POSTHOG_SECRET --yes --format json
 ```
 
-Use `frontend env` for public, browser-visible variables (`VITE_PUBLIC_*`,
-analytics keys). Use `secret` for server runtime and private build values.
-`BUILD` secrets are injected into managed frontend builds and require a redeploy;
-`RUNTIME` secrets are for trusted server/backend code and are never exposed to
-the browser.
+There is no builder-managed public-variable surface and values are never
+revealed after write. Rotation preserves the delivery phase; changing phase
+requires revoke, delete, and recreate.
 
 ### `farthershore backend`
 
@@ -379,6 +380,10 @@ farthershore backend create weather-api \
   --name "Production API" \
   --origin-url https://api.example.com \
   --format json
+farthershore backend bind weather-api api \
+  --env preview-42 \
+  --origin-url https://api-pr-42.example.com \
+  --format json
 farthershore backend tokens create weather-api --backend <backendId> --format json
 farthershore backend tokens rotate weather-api <tokenId> --format json
 farthershore backend tokens revoke weather-api <tokenId> --yes --format json