@lepsto/sdk-app 89.6.0 → 89.7.1

package/CHANGELOG.md

@@ -115,36 +115,8 @@ before this point lives in that package.
 The publish pipeline appends its machine-rendered block for the release being
 built below this line. It is not committed back to the repo, so in a git
 checkout this section is empty — see the note at the top.
-## 89.6.0 (minor)
-
-### deployment
-- `deployment_canvas_get`: new optional field `services.publicDomain (output)`
-- `deployment_domain_add`: new optional field `redirectStatus (output)`
-- `deployment_domain_add`: new optional field `redirectToDomainId (output)`
-- `deployment_domain_get`: new optional field `redirectStatus (output)`
-- `deployment_domain_get`: new optional field `redirectToDomainId (output)`
-- `deployment_domain_list`: new optional field `redirectStatus (output)`
-- `deployment_domain_list`: new optional field `redirectToDomainId (output)`
-- `deployment_domain_list_by_service`: new optional field `redirectStatus (output)`
-- `deployment_domain_list_by_service`: new optional field `redirectToDomainId (output)`
-- added `deployment_domain_redirect_set`
-- `deployment_domain_redirect_www`: new optional field `redirectStatus (output)`
-- `deployment_domain_redirect_www`: new optional field `redirectToDomainId (output)`
-- `deployment_domain_verify`: new optional field `redirectStatus (output)`
-- `deployment_domain_verify`: new optional field `redirectToDomainId (output)`
-- `deployment_events_list_by_environment`: new accepted value on `type`
-- `deployment_events_list_by_environment`: new accepted value on `type (output)`
-- `deployment_events_list_by_service`: new accepted value on `type`
-- `deployment_events_list_by_service`: new accepted value on `type (output)`
-- `deployment_service_create`: new optional field `publicDomain`
-- `deployment_service_create`: new optional field `publicDomain (output)`
-- `deployment_service_create`: description updated
-- `deployment_service_get`: new optional field `publicDomain (output)`
-- `deployment_service_get`: description updated
-- `deployment_service_list`: new optional field `publicDomain (output)`
-- `deployment_service_list`: description updated
-- `deployment_service_scale`: new optional field `publicDomain (output)`
-- `deployment_service_update`: new optional field `publicDomain`
-- `deployment_service_update`: new optional field `publicDomain (output)`
-- `deployment_service_update`: description updated
+## 89.7.1 (patch)
+
+### *
+- documentation update
 

package/README.md

@@ -4,35 +4,35 @@ The Lepsto SDK for App is a TypeScript SDK that provides runtime bindings and ty
 
 **Note:** The `src/gen` directory contains generated SDK code and should not be edited by hand. Generated files are produced by running `npm run generate` with an API catalog.
 
-The committed `src/gen` is a **convenience snapshot** — it lets the repo type-check, test, and build offline. It is **not** the source of truth: canonical generation happens **at publish time**, when Cloud Build regenerates `src/gen` from the live catalog before publishing. The catalog is **mid-migration**, so the committed snapshot's namespaces (currently `organization` and `playground`) will **grow as platform extensions migrate to `@lessly-platform/tools`** — a namespace only appears once its tools carry a REST binding (tools without one are excluded until migrated). Regenerate the snapshot with `npx tsx scripts/generate.ts <catalog.json> src/gen && npm run sync-exports` against the live catalog (`https://api.lessly.dev/catalog/tools`).
+The committed `src/gen` is a **convenience snapshot** — it lets the repo type-check, test, and build offline. It is **not** the source of truth: canonical generation happens **at publish time**, when Cloud Build regenerates `src/gen` from the live catalog before publishing. The catalog is **mid-migration**, so the committed snapshot's namespaces (currently `organization` and `playground`) will **grow as platform extensions migrate to `@lepsto-platform/tools`** — a namespace only appears once its tools carry a REST binding (tools without one are excluded until migrated). Regenerate the snapshot with `npx tsx scripts/generate.ts <catalog.json> src/gen && npm run sync-exports` against the live catalog (`https://api.lepsto.dev/catalog/tools`).
 
-## Package name: `@lepsto/sdk-app` (and legacy `@lessly/sdk-app`)
+## Package name: `@lepsto/sdk-app`
 
 ```sh
 npm i @lepsto/sdk-app
 ```
 
-The package is published on public npmjs as **`@lepsto/sdk-app`** and, during the transition,
-**also** as `@lessly/sdk-app` — same build, same version, identical `exports` map. The old name is
-not deprecated.
+`@lepsto/sdk-app` is the name to install. One build is published on public npmjs under two
+names — `@lepsto/sdk-app` and `@lessly/sdk-app` — at the same version, with an identical
+`exports` map. Both are supported.
 
-`package.json` keeps `name: @lessly/sdk-app` on purpose: the dev-console SDK-rebuild Cloud Build
-job derives `PKG` from it (`require('./package.json').name`) for its `npm view` probe and runs
-`npm run publish:npmjs -- --tag <channel>`. The new name is the **derived** tarball.
+`package.json` carries `name: @lessly/sdk-app`, and the dev-console SDK-rebuild Cloud Build job
+derives `PKG` from it (`require('./package.json').name`) for its `npm view` probe before running
+`npm run publish:npmjs -- --tag <channel>`. `@lepsto/sdk-app` is the **derived** tarball.
 
 | Script | Publishes | Contract |
 | --- | --- | --- |
-| `npm run publish:npmjs -- --tag <channel>` | `@lessly/sdk-app` | unchanged; token with write on `@lessly` |
+| `npm run publish:npmjs -- --tag <channel>` | `@lessly/sdk-app` | token with write on `@lessly` |
 | `npm run publish:npmjs:lepsto -- --tag <channel>` | `@lepsto/sdk-app` | same args as `publish:npmjs`; token with write on `@lepsto` |
 
 `publish:npmjs:lepsto` (`scripts/publish-alias.ts`) builds once, `npm pack`s, rewrites `name` and `description`
-(the Lepsto text; `package.json` keeps the legacy description for `@lessly/sdk-app`),
+(the Lepsto text; `package.json` carries its own description for `@lessly/sdk-app`),
 checks every `exports` target is in the tarball, and publishes with `--registry` and
 `--@lepsto:registry` pinned. Run it after `publish:npmjs` against the same checkout so both names
 carry the same version.
 
-**Bootstrap** (`.github/workflows/publish-lepsto.yml`, manual): mirrors already-published legacy
-tarballs instead of rebuilding — `npm pack @lessly/sdk-app@<v>`, rewrite `name` and `description`, drop
+**Bootstrap** (`.github/workflows/publish-lepsto.yml`, manual): mirrors already-published
+`@lessly/sdk-app` tarballs instead of rebuilding — `npm pack @lessly/sdk-app@<v>`, rewrite `name` and `description`, drop
 `publishConfig.registry`, publish as `@lepsto/sdk-app@<v>` (`tsx scripts/publish-alias.ts --mirror
 84.0.0:latest,85.0.0:next`). Versions that already exist are skipped. It uses `NPM_BOOTSTRAP_TOKEN`
 and is ready for npm Trusted Publishing (`id-token: write`, npm >= 11.5.1, token only in the publish
@@ -46,9 +46,10 @@ Create a client with `createLesslyApp`, then call operations through the Proxy n
 import { createLesslyApp } from '@lepsto/sdk-app';
 
 const sdk = createLesslyApp({
-  baseUrl: 'https://api.lessly.dev', // or a page-relative '/api' in the browser
+  baseUrl: 'https://api.lepsto.dev', // or a page-relative '/api' in the browser
   productId: 'prod_123',
-  // getCsrfToken defaults to reading the `lessly_csrf` cookie; override for SSR/tests.
+  // getCsrfToken defaults to reading the `lepsto_csrf` cookie, then `lessly_csrf`;
+  // override for SSR/tests.
 });
 
 const connectors = await sdk.organization.connectors.list({ productId: 'prod_123' });
@@ -113,7 +114,7 @@ Streaming (`<tool>Connect`) factories carry neither field: a socket is neither a
 and the catalog declares no level for a ws-only tool.
 
 Errors are surfaced as a typed `LesslyApiError` (`status`, `code`, `body`). Mutating calls
-without the `lessly_csrf` cookie fail before the network with `status: 0` and
+without the `lepsto_csrf` cookie (or `lessly_csrf`) fail before the network with `status: 0` and
 `code: 'csrf_cookie_missing'` — no retry, no hidden refresh.
 
 ### TanStack Query
@@ -156,13 +157,13 @@ npm run ci -- --channel <next|latest> --catalog-url <URL> [--baseline <path>]
 
 - `--channel` — the npm dist-tag to publish under (`next` for staging, `latest` for production).
 - `--catalog-url` — the public catalog endpoint, fetched with an anonymous GET
-  (staging `https://api.lessly.dev/catalog/tools`, production `https://api.lessly.com/catalog/tools`).
+  (staging `https://api.lepsto.dev/catalog/tools`, production `https://api.lepsto.com/catalog/tools`).
 - `--baseline` — path to the previous catalog snapshot (downloaded from GCS) used for the
   content-hash gate and the semver diff-classifier. **Omit it for the first publish.**
 
 The very first publish on the (empty) npmjs registry is floored at **`0.2.0`**, not `0.1.0`,
 so it lands strictly above the legacy GAR `0.1.x` line that existing consumers pinned (e.g.
-`^0.1.1`). This mirrors the `@lessly/ui` migration (GAR `0.1.0` → npmjs `0.2.0`). Once a version
+`^0.1.1`). Once a version
 exists on a channel's dist-tag, normal semver bumping (and the recovery patch-bump) takes over.
 The floor is keyed off the **registry**, not the flag: if the channel's dist-tag resolves to
 nothing (empty npmjs), the run takes the first-publish path even when Cloud Build passes a stored

package/docs/README.md

@@ -1,20 +1,20 @@
-# Building a Lessly App
+# Building a Lepsto App
 
-This is the entry point for building a Lessly **App** with `@lepsto/sdk-app`.
+This is the entry point for building a Lepsto **App** with `@lepsto/sdk-app`.
 Read this file first, then `rules.md`, then whichever recipe under `recipes/`
 matches the task in front of you.
 
 This path is stable: every scaffolded app's `AGENTS.md` points agents at
-`node_modules/@lepsto/sdk-app/docs/README.md` (or `node_modules/@lessly/sdk-app/docs/README.md` under the legacy name). It will not move or be renamed.
+`node_modules/@lepsto/sdk-app/docs/README.md`. It will not move or be renamed.
 
 ## What an App is
 
-A Lessly **App** is a pure-frontend Module Federation remote built on
+A Lepsto **App** is a pure-frontend Module Federation remote built on
 `@lepsto/sdk-app`. It ships no backend, no database, and no MCP endpoint — all
 platform data access goes through the SDK, and all identity/session state is
 handed to it by the shell that hosts it.
 
-Contrast this with a Lessly **extension**: an extension owns a backend
+Contrast this with a Lepsto **extension**: an extension owns a backend
 service, a database, and typically an MCP endpoint, and is built against the
 toolkit-guide contracts (`MFST-*`, `PRD-*`, `MCP-*`, etc.). An App has none
 of that surface. If your task involves a database migration, a service-to-service
@@ -32,7 +32,7 @@ does not apply.
   product switching. An App reads the active product from props or the
   `X-Product-Id` header — never from a token — and must not implement its own
   auth.
-- **Manifest is `lessly.app.yaml`, schema v1.** Exactly five top-level fields:
+- **Manifest is `lepsto.app.yaml`, schema v1.** Exactly five top-level fields:
   `app_schema_version: 1`, `id`, `title`, `version`, `nav` (`nav.icon`, plus an
   optional `nav.sections` rail menu). No backend or extension manifest field
   (`s2s`, `webhooks`, `billing`, `analytics`, `routing`, ...) is valid here.
@@ -43,12 +43,12 @@ does not apply.
 ## Quickstart
 
 ```sh
-npm create lessly-app@latest my-app
+npm create lepsto-app@latest my-app
 cd my-app
 pnpm dev
 ```
 
-The generated manifest (`lessly.app.yaml`) is the full v1 surface:
+The generated manifest (`lepsto.app.yaml`) is the full v1 surface:
 
 ```yaml
 app_schema_version: 1

package/docs/recipes/access.md

@@ -81,7 +81,7 @@ drift from the method it is meant to describe; the method cannot.
 // src/App.tsx
 import { useEffect } from 'react';
 import { createLesslyApp } from '@lepsto/sdk-app';
-import { TooltipProvider } from '@lessly/ui';
+import { TooltipProvider } from '@lepsto/ui';
 
 export default function App({ productId }: { productId: string }) {
   const app = useMemo(() => createLesslyApp({ baseUrl: '/api', productId }), [productId]);
@@ -119,7 +119,7 @@ refetched on a timer.
 ```tsx
 import { accessReason } from '@lepsto/sdk-app';
 import { useAccess, useCan } from '@lepsto/sdk-app/react';
-import { Button, Tooltip, TooltipContent, TooltipProvider, TooltipTrigger } from '@lessly/ui';
+import { Button, Tooltip, TooltipContent, TooltipProvider, TooltipTrigger } from '@lepsto/ui';
 
 function AddDomainButton({ app, onClick }: { app: App; onClick: () => void }) {
   const { state } = useAccess(app);
@@ -164,7 +164,7 @@ by keyboard and by touch even on an enabled control. That class sits in the **ba
 `buttonVariants`, not in an icon-only branch — so the wrapper pattern applies to
 *every* Button, not just the icon-only shape. The wrapping trigger carries
 `tabIndex={0}` for the same reason: a keyboard user has to be able to reach the hint.
-This mirrors what `@lessly/ui` documents above `ButtonIconOnlyProps` in `button.tsx`
+This mirrors what `@lepsto/ui` documents above `ButtonIconOnlyProps` in `button.tsx`
 (`Button --disabled-with-tooltip` shows both halves).
 
 Controls that take no `title` at all — the kit's `Switch`, for one — have no other
@@ -543,7 +543,7 @@ Prefer **one line in the card's footer**, stating the constraint before anyone
 starts editing:
 
 ```tsx
-import { Card, CardNote } from '@lessly/ui';
+import { Card, CardNote } from '@lepsto/ui';
 
 <Card title="Domain settings">
   {fields}

package/docs/recipes/federation.md

@@ -28,7 +28,7 @@ There is no `./navigation` module. FED-011 — the shell's extension-menu
 contract — is **RETIRED (2026-08)**: the shell never registers, preloads or
 calls it, there is no `subscribeNavItems` (v1 or v2) and no
 `navContractVersion` negotiation, and the menu the shell renders while your app
-is open comes from **your own** `lessly.app.yaml` — the `nav.sections` block
+is open comes from **your own** `lepsto.app.yaml` — the `nav.sections` block
 (APP-011) — not from your App code, and not from a toolkit manifest.
 
 Still mapping the expose is inert, not an error — you just ship a chunk nobody
@@ -46,7 +46,7 @@ router.
 The rows the module used to publish are now data in your App's manifest:
 
 ```yaml
-# lessly.app.yaml
+# lepsto.app.yaml
 nav:
   icon: flask-conical
   sections:
@@ -68,7 +68,7 @@ how a change reaches production are in APP-011.
 
 ## Shared singletons: `>=` floors, not carets, on 0.x packages
 
-`react`, `react-dom`, `react-router`, and `@lessly/ui` MUST be declared as
+`react`, `react-dom`, `react-router`, and `@lepsto/ui` MUST be declared as
 shared singletons, never bundled (FED-005), pinned via `@module-federation/vite`
 at exactly `1.16.12` (FED-006):
 
@@ -77,18 +77,25 @@ const SHARED = {
   react: { singleton: true, strictVersion: false, requiredVersion: '^19' },
   'react-dom': { singleton: true, strictVersion: false, requiredVersion: '^19' },
   'react-router': { singleton: true, strictVersion: false, requiredVersion: '^7.18' },
-  // 0.x singletons use a `>=` floor, NOT a caret: `^0.x` resolves to `<0.(x+1).0`,
-  // so a routine shell ui/icon bump would fail Module Federation version negotiation.
-  '@lessly/ui': { singleton: true, strictVersion: false, requiredVersion: '>=0.1.0' },
+  // The kit is shared on a `>=` floor, NOT a caret: a caret pins the share to one
+  // major (or, on a 0.x package, one minor), so a routine shell kit bump would fail
+  // Module Federation version negotiation.
+  '@lepsto/ui': { singleton: true, strictVersion: false, requiredVersion: '>=0.1.0' },
 };
 ```
 
-`@lessly/ui` is pre-1.0. A caret range on a 0.x package (`^0.1.0`) resolves to
-`<0.2.0`, so the next time the shell bumps `@lessly/ui`'s minor version, MF
-version negotiation fails and your remote won't load under the shell. Use a
-`>=` floor for every 0.x shared singleton instead — it only guarantees a
-minimum, so it survives minor bumps upstream. Any other 0.x singleton you add
-(e.g. an icon package) follows the same rule.
+Two different ranges describe two different things here, and they are meant to
+disagree:
+
+- the **share range** (`requiredVersion` above) is deliberately open — `>=0.1.0`,
+  the same shape the shell declares. It only has to guarantee a floor, so it
+  survives every upstream bump of the kit without breaking MF negotiation.
+- the **dependency range** in your `package.json` is `^9.0.0`, the major the
+  shell actually runs (see "Three things that are easy to get wrong" below).
+
+Pin the share with a caret and the next kit bump in the shell fails version
+negotiation and your remote won't load. Any other shared singleton you add
+(e.g. an icon package) uses the same `>=` floor.
 
 ## Dual build: standalone + federation, merged into one `dist/`
 
@@ -153,16 +160,16 @@ Four files, ready to copy.
    tailwindcss/theme.css at all. */
 
 /* Layer order first, so positions are fixed before Tailwind emits its own.
-   Mirrors the shell's declaration in lessly-workspace:apps/web/src/index.css. */
+   Mirrors the shell's declaration in lepsto-workspace:apps/web/src/index.css. */
 @layer theme, base, components, remote-utilities, utilities;
 
 @config '../tailwind.config.ts';
 @import 'tailwindcss/utilities.css' layer(remote-utilities);
-@import '@lessly/ui/styles-federated.css';
+@import '@lepsto/ui/styles-federated.css';
 
-/* Tailwind must scan the kit's compiled output, or the classes @lessly/ui
+/* Tailwind must scan the kit's compiled output, or the classes @lepsto/ui
    components use are never generated. */
-@source '../node_modules/@lessly/ui/dist/index.js';
+@source '../node_modules/@lepsto/ui/dist/index.js';
 
 /* ...and must NOT scan your tests: a utility class named as a test fixture is
    just a string to Tailwind, and would be compiled into the shipped sheet. */
@@ -178,12 +185,12 @@ Four files, ready to copy.
 @config '../tailwind.config.ts';
 @import 'tailwindcss';
 @import url('https://fonts.googleapis.com/css2?family=Inter');
-@import '@lessly/ui/styles.css';
+@import '@lepsto/ui/styles.css';
 @import './base.css';
 
 /* Same reason as in the federation entry: Tailwind generates utilities per
    entry, and neither entry's scan reaches node_modules on its own. */
-@source '../node_modules/@lessly/ui/dist/index.js';
+@source '../node_modules/@lepsto/ui/dist/index.js';
 ```
 
 ```css
@@ -197,10 +204,10 @@ Four files, ready to copy.
 
 ```ts
 // tailwind.config.ts — the single source of scale vocabulary, for both entries
-import { lesslyPreset } from '@lessly/ui/tailwind-preset';
+import { lepstoPreset } from '@lepsto/ui/tailwind-preset';
 
 export default {
-  presets: [lesslyPreset],
+  presets: [lepstoPreset],
   content: ['./index.html', './src/**/*.{ts,tsx}'],
 };
 ```
@@ -221,8 +228,8 @@ import './index.css';
 
 **`theme.css` is optional, and it is not a token bridge.** There is no
 `src/theme.css` in the layout above, and an app with no tokens of its own does
-not need one. The kit's tokens come from `@lessly/ui/styles-federated.css` in
-federation and `@lessly/ui/styles.css` in standalone; re-declaring them locally
+not need one. The kit's tokens come from `@lepsto/ui/styles-federated.css` in
+federation and `@lepsto/ui/styles.css` in standalone; re-declaring them locally
 is a hand-copied set that drifts from the kit silently, and an `@theme` block
 restating the kit's scales is exactly what APP-009 forbids.
 
@@ -234,16 +241,16 @@ first paint. That exact block is what shipped the production font jump; it
 belongs in `src/base.css`, standalone-only.
 
 **The sanctioned federated export, not a hand-rolled filter.**
-`@lessly/ui/styles-federated.css` is `styles.css` minus the `@font-face` blocks
+`@lepsto/ui/styles-federated.css` is `styles.css` minus the `@font-face` blocks
 and the `@layer base` — tokens, `--color-*` aliases, `.link`, the `.motion-*`
 helpers and the compiled tw-animate-css layer are all still there. A prebuild
 script that reads the kit's stylesheet out of `node_modules` and strips the
 forbidden blocks itself breaks on any restructure of a file you don't own.
-Depend on `@lessly/ui` at `^4.0.0`, the range the shell runs.
+Depend on `@lepsto/ui` at `^9.0.0`, the range the shell runs.
 
 **`layer(remote-utilities)` only after the shell declares the order.** The
 shell already ships `@layer theme, base, components, remote-utilities,
-utilities;` (`lessly-workspace:apps/web/src/index.css`). Adopt the layer
+utilities;` (`lepsto-workspace:apps/web/src/index.css`). Adopt the layer
 against a shell that hasn't, and `remote-utilities` becomes the last-declared —
 and therefore highest-priority — layer, so every one of your utilities beats
 every shell utility. Verify the shell first; adopting early is a regression,

package/docs/recipes/local-dev.md

@@ -11,29 +11,29 @@ pnpm dev
 ```
 
 This starts the app on its own, outside any shell, proxied through
-`@lessly/app-dev`'s local dev server. Platform API calls made through your
+`@lepsto/app-dev`'s local dev server. Platform API calls made through your
 `sdk` (created with `createLesslyApp`, see `recipes/sdk-usage.md`) are
 forwarded through a bearer proxy at exactly this path:
 
 ```
-/lessly-api
+/lepsto-api
 ```
 
-`@lessly/app-dev` attaches your locally stored bearer token to everything it
-proxies through `/lessly-api`, so your SDK client just talks to that path in
+`@lepsto/app-dev` attaches your locally stored bearer token to everything it
+proxies through `/lepsto-api`, so your SDK client just talks to that path in
 dev — it never sees or handles the token itself.
 
-So in dev you pass `baseUrl: '/lessly-api'` — a page-relative `baseUrl` is
+So in dev you pass `baseUrl: '/lepsto-api'` — a page-relative `baseUrl` is
 supported and resolved against the current document (browser-only); see
 `recipes/sdk-usage.md`.
 
 ### Device-code login
 
 The first time you run `pnpm dev` (or once your local session expires),
-`@lessly/app-dev` walks you through a device-code login: it prints a
+`@lepsto/app-dev` walks you through a device-code login: it prints a
 verification URL and a short code, opens your browser, and polls until you
 approve. Once approved, it stores the resulting bearer token locally and the
-`/lessly-api` proxy starts attaching it automatically. You don't write any of
+`/lepsto-api` proxy starts attaching it automatically. You don't write any of
 this — it's ambient, per APP-005: an App MUST NOT implement its own login,
 token handling, or refresh.
 
@@ -97,15 +97,15 @@ go back to the deployed remote.
 
 ## Keeping your local setup current
 
-Update the SDK and `@lessly/app-dev` with the `@latest` form, never `npm
+Update the SDK and `@lepsto/app-dev` with the `@latest` form, never `npm
 update`:
 
 ```sh
 npm i @lepsto/sdk-app@latest
-npm i @lessly/app-dev@latest
+npm i @lepsto/app-dev@latest
 ```
 
-`@lepsto/sdk-app` and `@lessly/app-dev` are pre-1.0 and pinned with caret
-ranges, so `npm update` never crosses a minor version — and since the SDK
-bumps its minor version whenever the platform ships a new tool, `npm update`
-would never actually deliver those updates (see APP-007).
+Both are pinned with caret ranges, and a caret range stops `npm update` at the
+next major — or, for a pre-1.0 package like `@lepsto/app-dev`, at the next
+minor. The SDK cuts majors routinely as the platform catalog changes, so
+`npm update` would never actually deliver those updates (see APP-007).

package/docs/recipes/sdk-usage.md

@@ -1,6 +1,6 @@
 # Recipe: calling the platform API
 
-How to reach Lessly platform data from an App. The normative rule is APP-001
+How to reach Lepsto platform data from an App. The normative rule is APP-001
 (all platform data access goes through `@lepsto/sdk-app`) and APP-006 (prefer
 the generated option factories) — this page shows the *how*.
 
@@ -13,10 +13,10 @@ Proxy namespace tree:
 import { createLesslyApp } from '@lepsto/sdk-app';
 
 const sdk = createLesslyApp({
-  baseUrl: 'https://api.lessly.dev',
+  baseUrl: 'https://api.lepsto.dev',
   productId: 'prod_123',
-  // getCsrfToken defaults to reading the `lepsto_csrf` cookie (falling back to
-  // the legacy `lessly_csrf`); override for SSR/tests.
+  // getCsrfToken defaults to reading the `lepsto_csrf` cookie, then
+  // `lessly_csrf`; override for SSR/tests.
 });
 
 const connectors = await sdk.organization.connectors.list({ productId: 'prod_123' });
@@ -31,18 +31,18 @@ await sdk.organization.product.create({ name: 'Acme' });
 
 `baseUrl` may be either form:
 
-- **Absolute** — `'https://api.lessly.dev'`. Works anywhere, including SSR and
+- **Absolute** — `'https://api.lepsto.dev'`. Works anywhere, including SSR and
   tests.
-- **Page-relative** — `'/lessly-api'`, the path `pnpm dev` proxies through
+- **Page-relative** — `'/lepsto-api'`, the path `pnpm dev` proxies through
   (see `recipes/local-dev.md`). It is resolved against the current document via
   `globalThis.location`, so it is **browser-only**: outside a browser the SDK
-  throws a named error (`@lepsto/sdk-app: relative baseUrl "/lessly-api" cannot
+  throws a named error (`@lepsto/sdk-app: relative baseUrl "/lepsto-api" cannot
   be resolved outside a browser`) instead of an opaque `Invalid URL`. Tests and
   SSR must pass an absolute base.
 
 ```ts
 const sdk = createLesslyApp({
-  baseUrl: import.meta.env.DEV ? '/lessly-api' : 'https://api.lessly.dev',
+  baseUrl: import.meta.env.DEV ? '/lepsto-api' : 'https://api.lepsto.dev',
   productId: 'prod_123',
 });
 ```
@@ -74,7 +74,7 @@ try {
 ### Missing CSRF cookie
 
 Mutating calls (`POST`, `PUT`, `PATCH`, `DELETE`) require the `lepsto_csrf`
-cookie, or the legacy `lessly_csrf` one as a fallback. If both are absent, the SDK throws before any network call:
+cookie, or `lessly_csrf` as a fallback. If both are absent, the SDK throws before any network call:
 `LesslyApiError` with `status: 0` and `code: 'csrf_cookie_missing'`. There is no
 retry and no hidden token refresh — re-establish the session, or supply
 `getCsrfToken` for SSR/tests. Read-only calls are unaffected.
@@ -130,7 +130,7 @@ generated from the live catalog; check `client.gen.ts` (or your editor's
 autocomplete) for which shape a given operation takes.
 
 The available namespaces track the live catalog and **grow as platform
-extensions migrate to `@lessly-platform/tools`** — a namespace appears here only once its
+extensions migrate to `@lepsto-platform/tools`** — a namespace appears here only once its
 tools carry a REST binding. Run `npm i @lepsto/sdk-app@latest` to pick up newly
 migrated namespaces. To see exactly what a given version exposes, check its
 subpaths in `package.json` `exports`, or the `manifest.gen.ts` namespace list.
@@ -147,7 +147,7 @@ the socket, and hands back a small handle:
 import { createLesslyApp } from '@lepsto/sdk-app';
 import { playgroundWsEchoConnect } from '@lepsto/sdk-app/playground';
 
-const sdk = createLesslyApp({ baseUrl: 'https://api.lessly.dev', productId: 'prod_123' });
+const sdk = createLesslyApp({ baseUrl: 'https://api.lepsto.dev', productId: 'prod_123' });
 
 const stream = playgroundWsEchoConnect(sdk, { room: 'lobby' });
 const off = stream.onMessage((frame) => console.log(frame));

package/docs/rules.md

@@ -1,6 +1,6 @@
 # App Rules
 
-Normative rules for building a Lessly App on `@lepsto/sdk-app`. Read this
+Normative rules for building a Lepsto App on `@lepsto/sdk-app`. Read this
 before writing code; see `README.md` for the map of the rest of the guide.
 
 Severity (RFC 2119): **MUST** blocks merge, **SHOULD** is a strong
@@ -17,7 +17,7 @@ rationale, and examples.
 
 ### APP-001 (MUST) — All platform data access goes through `@lepsto/sdk-app`
 
-Every read or write to a Lessly platform API MUST go through a
+Every read or write to a Lepsto platform API MUST go through a
 `@lepsto/sdk-app` client created with `createLesslyApp`, or through the
 generated `*QueryOptions`/`*MutationOptions` factories built on top of it. An
 App MUST NOT `fetch` a platform host directly, and MUST NOT use any other HTTP
@@ -43,9 +43,9 @@ of its logic runs in the browser, built on `@lepsto/sdk-app` and the Module
 Federation contract below. If a feature needs server-side state or a
 service-to-service call, it belongs in an extension, not an App.
 
-### APP-003 (MUST) — Manifest is `lessly.app.yaml`, schema v1
+### APP-003 (MUST) — Manifest is `lepsto.app.yaml`, schema v1
 
-The manifest file is `lessly.app.yaml`, and its top-level surface is exactly:
+The manifest file is `lepsto.app.yaml`, and its top-level surface is exactly:
 `app_schema_version: 1`, `id`, `title`, `version`, `nav`. No other top-level
 field is valid — in particular, no extension/backend manifest field (`s2s`,
 `webhooks`, `billing`, `analytics`, `routing`, `public`, ...) belongs in an App
@@ -61,7 +61,7 @@ being stripped.
 
 An App exposes `./App` as its Module Federation remote entry, implementing
 the shell's remote contract (FED-001). The Module Federation `name` MUST equal
-the manifest `id` (FED-004). React, React DOM, React Router, and `@lessly/ui`
+the manifest `id` (FED-004). React, React DOM, React Router, and `@lepsto/ui`
 MUST be declared as shared singletons, never bundled (FED-005), using
 `@module-federation/vite` pinned at exactly `1.16.12` (FED-006). The asset
 base in federation mode is the absolute path `/~/<id>/`. The build MUST
@@ -71,7 +71,7 @@ artifacts (FED-007).
 `./App` is the **only** module an App exposes. There is no `./navigation`
 contract: the shell no longer loads such a module, there is no
 `subscribeNavItems` and no `navContractVersion` negotiation, and the menu the
-shell renders comes from **your own** `lessly.app.yaml` — the `nav.sections`
+shell renders comes from **your own** `lepsto.app.yaml` — the `nav.sections`
 block (APP-011) — not from your App code, and not from a toolkit manifest.
 FED-011 is **RETIRED (2026-08)**. Still mapping the expose is inert rather than
 an error — it just ships a chunk nobody fetches — but a new App MUST NOT add
@@ -115,10 +115,12 @@ current with:
 npm i @lepsto/sdk-app@latest
 ```
 
-Use this exact `@latest` form — not `npm update`. `@lepsto/sdk-app` is
-pre-1.0 and pinned with a caret range, so `npm update` never crosses a minor
-version; since this SDK also bumps its minor version whenever the platform
-ships a new tool, `npm update` would never actually deliver those updates.
+Use this exact `@latest` form — not `npm update`. A caret range never lets
+`npm update` cross a major version, and this SDK cuts majors routinely: the
+publish pipeline classifies a removed field, a narrowed enum or a newly
+required input as a major, and the platform catalog produces those regularly.
+So `npm update` would leave you behind on the SDK no matter which version you
+are pinned at.
 
 ### APP-008 (MUST) — The federation CSS entry is slim and global-free
 
@@ -134,14 +136,14 @@ NOT contain:
   `font-size`, `line-height`, `color`, `background`, `margin`, `padding`,
   `border-*`, `box-sizing`, `-webkit-text-size-adjust` — on `html`, `body`,
   `:root` or `*`;
-- an `@import` of a web font, of `@lessly/ui/styles.css`, or of the full
+- an `@import` of a web font, of `@lepsto/ui/styles.css`, or of the full
   `tailwindcss` entry (which bundles **preflight**).
 
 The prohibition holds wherever the rule comes from, `@apply` included:
 `body { @apply bg-bg-primary … }` in the App's own base layer is exactly as
 forbidden as an imported reset. The App's base layer belongs in a separate
 `src/base.css` that only the **standalone** entry imports. The standalone entry
-is unconstrained by this rule: it keeps the fonts, `@lessly/ui/styles.css`, the
+is unconstrained by this rule: it keeps the fonts, `@lepsto/ui/styles.css`, the
 full `tailwindcss` import and the base layer, because there the App owns the
 page.
 
@@ -150,25 +152,25 @@ page.
 App's own subtree reads them. Inherited and visual properties are what is
 forbidden, because the App is composed inside the shell's already-painted page
 and a `body` or `*` rule addresses the whole live document, shell chrome
-included. This line is load-bearing: `@lessly/ui/styles-federated.css`
+included. This line is load-bearing: `@lepsto/ui/styles-federated.css`
 legitimately ships a `*, ::before, ::after, ::backdrop { --tw-*: … }` block
 (Tailwind v4's internal variable shim), and a guard written against selectors
 instead of declarations fails on the very import this rule prescribes.
 
 **Kit tokens.** An App that needs the design-system variables MUST import
-`@lessly/ui/styles-federated.css` — `styles.css` minus the `@font-face` blocks
+`@lepsto/ui/styles-federated.css` — `styles.css` minus the `@font-face` blocks
 and the `@layer base`, keeping the token variables, the `--color-*` aliases,
 `.link`, the `.motion-*` helpers and the compiled tw-animate-css layer. Depend
-on `@lessly/ui` at `^4.0.0`, the range the shell itself runs. An App MUST NOT
+on `@lepsto/ui` at `^9.0.0`, the range the shell itself runs. An App MUST NOT
 hand-copy the kit's tokens into a local `theme.css` (it silently drifts from
-the kit), and MUST NOT hand-filter `@lessly/ui/styles.css` with a prebuild
+the kit), and MUST NOT hand-filter `@lepsto/ui/styles.css` with a prebuild
 script (it breaks on any restructure of a file the App does not own).
 
 **Scanning.** Tailwind generates only the classes it finds, and it scans the
 project, not `node_modules`. The federation entry MUST therefore
 `@source` the kit's compiled output
-(`@source '../node_modules/@lessly/ui/dist/index.js';`) or the classes
-`@lessly/ui` components use are never emitted — and it SHOULD exclude test
+(`@source '../node_modules/@lepsto/ui/dist/index.js';`) or the classes
+`@lepsto/ui` components use are never emitted — and it SHOULD exclude test
 files (`@source not '../src/**/*.test.tsx';`), since a utility class named as a
 test fixture is just a string to Tailwind and would otherwise be compiled into
 the shipped stylesheet.
@@ -185,13 +187,13 @@ For the production defect this comes from — a remote's late-loading `body`
 rule re-fonting the shell's chrome — see FED-008 in the toolkit-guide.
 `recipes/federation.md` has the canonical stylesheets.
 
-### APP-009 (MUST) — One source of scale vocabulary: `lesslyPreset`
+### APP-009 (MUST) — One source of scale vocabulary: `lepstoPreset`
 
 An App takes its **scale vocabulary** — type, spacing, radii, font weight,
 line height, letter spacing — from the design-system preset the shell is built
-on: `lesslyPreset`, exported by `@lessly/ui/tailwind-preset`. Concretely:
+on: `lepstoPreset`, exported by `@lepsto/ui/tailwind-preset`. Concretely:
 
-- `tailwind.config.ts` sets `presets: [lesslyPreset]`;
+- `tailwind.config.ts` sets `presets: [lepstoPreset]`;
 - **both** CSS entries carry `@config '../tailwind.config.ts'`;
 - the App declares no scales of its own and keeps no `@theme` block bridging
   to them;
@@ -231,7 +233,7 @@ full `tailwindcss` import (APP-008), where the App owns the page and there is
 nothing to rank against.
 
 This works because the shell pre-declares the layer order in
-`lessly-workspace:apps/web/src/index.css`:
+`lepsto-workspace:apps/web/src/index.css`:
 
 ```css
 @layer theme, base, components, remote-utilities, utilities;
@@ -257,7 +259,7 @@ the App's own nodes.
 ### APP-011 (SHOULD) — Declare the rail menu in your own manifest
 
 The rail menu the shell draws while your App is open comes from your App's own
-`lessly.app.yaml`, in an optional `nav.sections` block. An App with more than
+`lepsto.app.yaml`, in an optional `nav.sections` block. An App with more than
 one page SHOULD declare it; without it the shell has nothing of yours to draw
 (see *No block* below).
 
@@ -326,7 +328,7 @@ table rather than drawing a partial disclosure.
 so adding, editing and removing sections all land without a `version` bump.
 Bumping `version` on release remains APP-007.
 
-**The scaffold's linter does not check this block.** `create-lessly-app lint`
+**The scaffold's linter does not check this block.** `create-lepsto-app lint`
 validates the top-level surface and `nav.icon` only; it neither rejects nor
 warns on `nav.sections`, and it will not catch a malformed one. The platform's
 registration validation is the authority — a menu that lints clean locally can
@@ -499,7 +501,7 @@ Pass the generated method rather than a hand-written tool id
 (`app.access.can(app.mail.domain.create)`): the accessor path is a lossy view
 of the tool id, so a literal string can silently drift from the call it gates.
 
-One gap is known and accepted: `@lessly/ui`'s `ConfirmDialog` takes an `onError`
+One gap is known and accepted: `@lepsto/ui`'s `ConfirmDialog` takes an `onError`
 that returns a string, so the kit picks the tone and a refusal raised inside the
 dialog cannot be painted neutrally yet. An App SHOULD still route that error
 through `isAccessDenied()` for the *words*, and MUST NOT reimplement the confirm

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@lepsto/sdk-app",
   "description": "The Lepsto SDK for App is a TypeScript SDK that provides runtime bindings and type-safe generated code for interacting with Lepsto Platform APIs and services. This package generates type definitions and client bindings from API catalogs, enabling developers to build applications that consume Lepsto platform services with full type safety and autocompletion.",
-  "version": "89.6.0",
+  "version": "89.7.1",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/lepsto/lepsto-sdk-app.git"