@getxflow/cli 1.0.0 → 1.0.2

package/dist/bin.js

@@ -223,11 +223,15 @@ async function run(args) {
                 await (0, pages_1.pagesRollback)(rest);
                 return;
             }
+            if (second === 'rm' || second === 'remove') {
+                await (0, pages_1.pagesRemove)(rest);
+                return;
+            }
             if (second === undefined || second === 'list') {
                 await (0, pages_1.pagesList)(rest);
                 return;
             }
-            throw new errors_1.CliError(`Unknown command: pages ${second}`, 'Available: list, create, deploy, status and rollback');
+            throw new errors_1.CliError(`Unknown command: pages ${second}`, 'Available: list, create, deploy, status, rollback and rm');
         case 'status':
             await (0, sources_1.status)();
             return;

package/dist/commands/pages.js

@@ -5,6 +5,7 @@ exports.pagesCreate = pagesCreate;
 exports.pagesDeploy = pagesDeploy;
 exports.pagesStatus = pagesStatus;
 exports.pagesRollback = pagesRollback;
+exports.pagesRemove = pagesRemove;
 const node_fs_1 = require("node:fs");
 const node_path_1 = require("node:path");
 const api_1 = require("../api");
@@ -231,3 +232,27 @@ async function pagesRollback(args) {
         (0, ui_1.warn)(`The page is switched off: version ${revision} is current and goes live when it is switched on`);
     (0, ui_1.out)(page.url);
 }
+async function pagesRemove(args) {
+    const ref = args.words[1];
+    if (!ref) {
+        throw new errors_1.CliError('A page is required', 'The name from its address, or its id. The pages: xflow pages');
+    }
+    // The page is read first: deleting is confirmed by the name in the address, and the
+    // page can be named here by its id.
+    const client = pagesClient();
+    const { page } = await (0, api_1.apiJson)(client, pagePath(ref));
+    const query = (0, args_1.flagBool)(args, 'yes') ? `?confirm=${encodeURIComponent(page.slug)}` : '';
+    try {
+        await (0, api_1.apiJson)(client, `${pagePath(page.id)}${query}`, { method: 'DELETE' });
+    }
+    catch (e) {
+        // The platform names what goes and refuses until the answer is seen. Said in the
+        // words of this command, not of the API.
+        if (e instanceof api_1.ApiError && e.code === 'confirm_required') {
+            throw new errors_1.CliError(e.message, `To delete it anyway: xflow pages rm ${page.slug} --yes`);
+        }
+        throw e;
+    }
+    (0, ui_1.ok)(`The page is deleted: ${page.url} shows nothing now`);
+    (0, ui_1.note)((0, ui_1.dim)(`  Its versions are gone for good, the name ${page.slug} stays reserved for the organization`));
+}

package/dist/flags.js

@@ -95,6 +95,8 @@ exports.KNOWN = {
     'pages deploy': ['message'],
     'pages status': ['json'],
     'pages rollback': [],
+    'pages rm': ['yes'],
+    'pages remove': ['yes'],
     status: [],
     dev: [],
     pull: ['into', 'force', 'revision'],

package/dist/help.js

@@ -108,6 +108,7 @@ ${(0, ui_1.bold)('Pages')}
                                   upload the site: live at once, there is no publish step
   xflow pages status <page>       the page and its versions
   xflow pages rollback <page> <N> put an earlier version back on the address
+  xflow pages rm <page> --yes     delete the page for good: the address empties
 
 ${(0, ui_1.bold)('Reference')}
   xflow logs [--limit N]          browser errors of the published apps
@@ -282,6 +283,8 @@ the platform builds, with versions, access levels and a database through functio
       -m <text>                        what changed, one short line: it names the version
   xflow pages status <page>            the page and its versions
   xflow pages rollback <page> <N>      put version N back on the address
+  xflow pages rm <page>                delete the page
+      --yes                            without it the command names what goes and stops
 
 ${(0, ui_1.bold)('<path>')} is a folder with index.html at the top, its .zip, or one .html file.
 ${(0, ui_1.bold)('<page>')} is the name from the address or the id. ${(0, ui_1.bold)('--json')} on list and status
@@ -304,9 +307,14 @@ add the page name there and run ${(0, ui_1.bold)('xflow deploy functions')}. The
 Such a function is open to the whole internet. Search engines are asked not to index pages,
 so do not promise SEO.
 
+${(0, ui_1.bold)('Deleting is final.')} The address goes empty and every version of the page is gone: there
+is no undo and no copy on the platform side. The name stays reserved for the organization, so
+the same ${(0, ui_1.bold)('--slug')} is free for the next page of yours and taken for everyone else. A
+throwaway page put up to try something is worth deleting the same way it was made.
+
 A page takes the key of the whole organization, the one ${(0, ui_1.bold)('xflow login')} issues: a key
-scoped to projects is refused. Switching a page off and deleting it are for a person, in the
-platform interface.`,
+scoped to projects is refused. A page is deleted by whoever made it, or by the owner of the
+organization. Switching a page off for a while is for a person, in the platform interface.`,
     update: `${(0, ui_1.bold)('xflow update')}: bring the CLI up to date
 
 Installs the published version and, if anything changed, rewrites the platform

package/dist/limits.js

@@ -13,7 +13,7 @@ const DENIAL_LABELS = {
     limit_functions: 'cloud functions',
     limit_builds: 'builds this month',
     limit_builds_concurrent: 'builds running at once',
-    limit_seats: 'seats in the organization',
+    limit_seats: 'people in the organization',
     limit_schedule_interval: 'schedule frequency',
     db_write_locked: 'database volume, writes are off',
     plan_no_schedules: 'schedules',
@@ -38,8 +38,7 @@ const QUOTA_ORDER = [
     'connections',
     'pages',
     'functions',
-    'developers',
-    'members',
+    'people',
     'database_mb',
     'files_mb',
     'function_minutes',
@@ -50,8 +49,7 @@ const QUOTA_LABELS = {
     connections: 'Active connections',
     pages: 'Public pages',
     functions: 'Cloud functions',
-    developers: 'Developers',
-    members: 'Staff',
+    people: 'People',
     database_mb: 'Database',
     files_mb: 'Files',
     function_minutes: 'Function minutes',

package/dist/template.js

@@ -2,30 +2,30 @@
 /** Files the CLI lays into a new project root: the app itself comes from the platform template. */
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.projectScaffold = projectScaffold;
-const GITIGNORE = `node_modules/
-dist/
-.xflow/
-.env
-.env.*
+const GITIGNORE = `node_modules/
+dist/
+.xflow/
+.env
+.env.*
 `;
-const README = `# %NAME%
-
-A project on XFlow: one database, cloud functions and the apps that use them.
-
-\`\`\`
-xflow.json          projectId, and which apps and pages may call each function
-package.json        dependencies of the functions
-functions/<name>/   cloud functions, shared by every app
-migrations/         the database of the project
-apps/<folder>/      an app: its own code, versions and address
-\`\`\`
-
-\`\`\`bash
-xflow deploy functions -m "..."      # ship the functions and their callers
-xflow deploy apps/<folder> -m "..."  # build one app
-xflow publish                        # inside an app folder: show the newest build
-xflow status                         # what is on the server
-\`\`\`
+const README = `# %NAME%
+
+A project on XFlow: one database, cloud functions and the apps that use them.
+
+\`\`\`
+xflow.json          projectId, and which apps and pages may call each function
+package.json        dependencies of the functions
+functions/<name>/   cloud functions, shared by every app
+migrations/         the database of the project
+apps/<folder>/      an app: its own code, versions and address
+\`\`\`
+
+\`\`\`bash
+xflow deploy functions -m "..."      # ship the functions and their callers
+xflow deploy apps/<folder> -m "..."  # build one app
+xflow publish                        # inside an app folder: show the newest build
+xflow status                         # what is on the server
+\`\`\`
 `;
 function projectScaffold(projectName) {
     return [

package/dist/version.js

@@ -2,6 +2,6 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.DEFAULT_API_URL = exports.CLI_VERSION = void 0;
 /** Keep in sync with cli/package.json. */
-exports.CLI_VERSION = '1.0.0';
+exports.CLI_VERSION = '1.0.2';
 /** Overridden by XFLOW_API_URL or the `api` field in xflow.json. */
 exports.DEFAULT_API_URL = 'https://app.getxflow.com';

package/package.json

@@ -1,24 +1,24 @@
-{
-  "name": "@getxflow/cli",
-  "version": "1.0.0",
-  "description": "CLI for the XFlow platform: projects with apps, functions and a database; source sync, deployment and publishing",
-  "license": "UNLICENSED",
-  "engines": {
-    "node": ">=20"
-  },
-  "bin": {
-    "xflow": "dist/bin.js"
-  },
-  "files": [
-    "dist",
-    "skills"
-  ],
-  "scripts": {
-    "clean": "node -e \"require('node:fs').rmSync('dist',{recursive:true,force:true})\"",
-    "build": "npm run clean && tsc -p tsconfig.json",
-    "prepublishOnly": "npm run build"
-  },
-  "publishConfig": {
-    "access": "public"
-  }
-}
+{
+  "name": "@getxflow/cli",
+  "version": "1.0.2",
+  "description": "CLI for the XFlow platform: projects with apps, functions and a database; source sync, deployment and publishing",
+  "license": "UNLICENSED",
+  "engines": {
+    "node": ">=20"
+  },
+  "bin": {
+    "xflow": "dist/bin.js"
+  },
+  "files": [
+    "dist",
+    "skills"
+  ],
+  "scripts": {
+    "clean": "node -e \"require('node:fs').rmSync('dist',{recursive:true,force:true})\"",
+    "build": "npm run clean && tsc -p tsconfig.json",
+    "prepublishOnly": "npm run build"
+  },
+  "publishConfig": {
+    "access": "public"
+  }
+}

package/skills/xflow/SKILL.md

@@ -23,7 +23,7 @@ contains the fix.
 
 ## Keeping these instructions current
 
-These instructions ship with xflow CLI 1.0.0, so the copy you are reading can be older than
+These instructions ship with xflow CLI 1.0.2, so the copy you are reading can be older than
 the CLI answering your commands.
 
 When the CLI says this file does not match it, run `xflow skills --refresh` and then **read
@@ -108,7 +108,7 @@ One folder per project, apps in subfolders:
 ## Plan limits
 
 The organization runs on a plan with limits: apps, functions, pages, active connections,
-seats, database and file storage, function minutes, builds per month and at once, schedules
+people in the organization, database and file storage, function minutes, builds per month and at once, schedules
 and how often they may run, and which access levels an app may have. Most are finite; a plan
 may leave one uncapped, and then `whoami` prints `no limit` instead of a ceiling.
 `xflow whoami` prints every one of them next to what is used, and the rights of your own key
@@ -198,7 +198,7 @@ An app:
 - The platform files stay byte for byte as they arrived: `src/lib/platform-auth.ts`,
   `src/contexts/platform-auth-context.tsx`, `src/hooks/use-platform-auth.ts`,
   `src/utils/error-logger.ts`, `src/lib/xflow.ts`. The code keeps calling `initPlatformAuth()`
-  and `initErrorLogger()`, importing `index.css`, mounting `ThemeProvider`, and the Tailwind
+  and `initErrorLogger()` and importing `index.css`, and the Tailwind
   `content` globs keep covering `src/**`. A rejection names the revision to take the original
   from: `xflow pull --revision N --into ./original`, then copy the file back.
 
@@ -214,10 +214,15 @@ Fix the first two before you tell the person the app is done.
 ## The template is a starter kit
 
 - `src/components/ui` and `src/components/blocks` are a starting set: change them, restyle them
-  or delete what you do not use. Your own colors and inline styles are allowed.
-- While any template component is left, the theme token names in `src/index.css` (`:root` and
-  `.dark`) and their mapping in the Tailwind config stay: those components paint with them.
-  Values change freely.
+  or delete what you do not use. Any colors, your own color scheme, inline styles, a single
+  theme without dark mode: all allowed.
+- The template looks like the xflow interface: warm grays, hairline controls (`ctl-solid`,
+  `ctl-raised`, `ctl-inset`, `ctl-select`), segments (`seg-track`, `seg-on`) and surfaces
+  (`surface-raised`, `surface-pop`, `surface-modal`) in `src/index.css`.
+- While any template component is left, the theme token names in `:root` of `src/index.css`
+  and their `hsl(var(--name))` mapping in the Tailwind config stay: those components paint with
+  them. Values change freely; they are HSL components (`216 95% 40%`), not `#hex`. Your own
+  colors go under new names.
 - Images and other assets: import them from `src/` (`import logo from './assets/logo.png'`)
   so the build puts them next to the code. An absolute path into `public/` (`/logo.png`) goes
   through the access check of the app and fails inside the xflow frame in Safari.
@@ -228,14 +233,19 @@ A person sets this in the web interface; you cannot, and you should not ask for
 
 | Level | Who gets in |
 |---|---|
-| Project members | people signed in to xflow who have access to the project |
+| Project members | people who have access to the project: the team through xflow, staff with a login |
 | By list | the members named for this app |
 | Anyone with the link | anybody, no sign-in at all |
 
 - The plan decides which levels exist: on Free an app opens only inside xflow, Start adds the
-  direct address and "By list", Business adds "Anyone with the link".
+  direct address, "By list" and "Anyone with the link".
 - At the two closed levels the platform signs people in, and a function receives the person in
-  `event.xflow.user` (`id`, `role` in the organization).
+  `event.xflow.user` (`id`, `role` in the organization, `name`, `login`).
+- Staff (a doctor, a picker) never sign in to xflow: an admin gives them a login and a password,
+  they enter at the address of the app, `login` is set for them and null for the team. Keep
+  roles inside the app (doctor, receptionist) in your own table keyed by `user.id`.
+- A "Sign out" button: `const r = await fetch('/_xflow/logout', { method: 'POST' })`, then
+  `location.href = (await r.json()).next`. It ends every sign-in of the person.
 - At "Anyone with the link" the platform signs nobody in: `event.xflow.user` is null for
   visitors. Accounts, sign-in and who sees which rows are the code of your app, see below.
 - `usePlatformAuth()` in the frontend knows the person only inside the xflow frame, and even
@@ -383,7 +393,8 @@ exports.handler = async (event) => {
   //         project), 'external' (an outside service with a key), 'schedule',
   //         'platform' (a person through xflow functions invoke or the web interface)
   // slug:   the address name of the calling app (<id>--<org>) or page, null otherwise
-  // user:   { id, role } of a signed-in member, null for anonymous visitors, pages, keys
+  // user:   { id, role, name, login } of a signed-in person (login only for staff),
+  //         null for anonymous visitors, pages, keys
   // ip:     the visitor's address, null for a schedule
 }
 ```
@@ -399,7 +410,9 @@ exports.minRole = 'developer'   // 'member' | 'developer' | 'owner'
 
 The platform refuses anything below that role before your code runs; it applies to people
 (apps, pages, `functions invoke`), not to keys and schedules. `member` is the people who only
-use the apps (staff of a clinic, managers), `developer` and `owner` build them. Without the line
+use the apps (staff of a clinic, managers), `developer` and `owner` build them. In the web
+interface these roles are called «Просмотр» (`member`), «Редактор» (`developer`) and «Админ»
+(`owner`). Without the line
 every member of the project can call the function. Losing access
 closes the function within a minute.
 
@@ -512,9 +525,11 @@ and zsh, cmd.exe wants double ones; a query with quotes of its own goes in a `.s
 the project, `xflow db query ../q.sql`.
 
 The platform keeps no database history and no backups, so anything that destroys data
-(`DROP TABLE`, `DROP COLUMN`, `TRUNCATE`, `DELETE FROM` without a condition) needs both the
-`--allow-destructive` flag and the right to destroy data on the key, which is off by default and
-only its owner turns on. When the refusal is about the right, the flag changes nothing: say what
+(`DROP TABLE`, `DROP COLUMN`, `TRUNCATE`, `DELETE`) needs both the `--allow-destructive` flag and
+the right to destroy data on the key, which is off by default and only its owner turns on. It is
+judged by the result, not the text: a migration that dropped or emptied a table, dropped a column
+or deleted rows is rolled back, however the SQL was written. `BEGIN`/`COMMIT` in a migration are
+refused: each one already runs in its own transaction. When the refusal is about the right, the flag changes nothing: say what
 needs deleting and why, and let the person decide. With both in place the affected tables are
 dumped first (up to 50 000 rows each) and kept for 7 days; getting a dump back is a request to
 the person, no command does it. Check with `--dry-run`.
@@ -607,6 +622,10 @@ the address opens it, without signing in.
 - **Both are public the moment the command finishes**: no draft, no publish step.
 - `xflow pages status <page>` lists the versions, `xflow pages rollback <page> <N>` puts one back
   in seconds; the files of the last 5 are kept.
+- `xflow pages rm <page> --yes` deletes the page: the address goes empty and every version is
+  gone for good, without `--yes` the command names what goes and stops. The name stays reserved
+  for the organization. A page put up to try something out is yours to take down when you are
+  done: do not leave it standing.
 - Names are 3-40 characters. At most 100 pages per organization, 20 new and 200 uploads a day,
   10 seconds between uploads of one page: batch changes into one upload.
 - Static files only, what the build writes (`dist`), never a folder with `package.json`. At most
@@ -618,7 +637,8 @@ the address opens it, without signing in.
 - Search engines are asked not to index pages or apps: do not promise SEO.
 - The tab icon is the platform's on every page: do not spend a request on a favicon of your own.
 - The MCP `pages` tool uploads one self-contained HTML document up to 150 KB.
-- Switching a page off and deleting it are for a person, in the platform interface.
+- A page is deleted by whoever made it, or by the owner of the organization. Switching a page
+  off for a while is for a person, in the platform interface.
 
 ## Organizations and keys
 
@@ -631,6 +651,10 @@ lists the commands that take them). A "not found" on a project you know exists u
 key belongs to another organization: check `xflow org`; signing in to a missing organization is
 `xflow login`, and that needs a person with a browser.
 
+A key has its owner's level in each project. With view-only access reading works (`projects
+get`, logs, `db query`, `pull`), and every change fails with `Your access to this project is
+view-only`. That is not a bug to work around: tell the person, edit access is theirs to ask for.
+
 ## Direct access without the terminal
 
 The platform also exposes an MCP server, connected with `xflow mcp install`. When its tools are
@@ -653,6 +677,9 @@ people are set by a person in the web interface.
 
 - Take a block from `src/components/blocks` or a primitive from `src/components/ui` before
   writing your own layout; replace or delete them when the design needs something else.
+- Dropdowns, checkboxes, radios and dates through `Select`, `Checkbox`, `RadioGroup`,
+  `DatePicker` from `src/components/ui`: a bare `<select>` opens the system list in Safari
+  and Firefox, out of the app's style.
 - Every screen starts with a clear header; header, filters and content in one column.
 - Draw all four states: loading, error, empty, data. An empty screen says what appears here and
   offers an action.