@getxflow/cli 1.8.0 → 1.8.1

package/dist/limits.js

@@ -40,8 +40,7 @@ const QUOTA_ORDER = [
     'functions',
     'schedules',
     'people',
-    'database_mb',
-    'files_mb',
+    'space_mb',
     'function_minutes',
     'db_hours',
     'builds',
@@ -52,8 +51,7 @@ const QUOTA_LABELS = {
     functions: 'Cloud functions',
     schedules: 'Schedules',
     people: 'People',
-    database_mb: 'Database',
-    files_mb: 'Files',
+    space_mb: 'Space (databases and files together)',
     function_minutes: 'Function minutes',
     db_hours: 'Database hours',
     builds: 'Builds this month',

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.8.0';
+exports.CLI_VERSION = '1.8.1';
 /** Overridden by XFLOW_API_URL or the `api` field in xflow.json. */
 exports.DEFAULT_API_URL = 'https://app.getxflow.com';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getxflow/cli",
-  "version": "1.8.0",
+  "version": "1.8.1",
   "description": "CLI for the XFlow platform: projects with apps, functions and a database; source sync, deployment and publishing",
   "license": "UNLICENSED",
   "engines": {

package/skills/xflow/SKILL.md

@@ -28,7 +28,7 @@ instead of guessing; give the person https://docs.getxflow.com when they ask how
 
 ## Keeping these instructions current
 
-These instructions ship with xflow CLI 1.8.0, so the copy you are reading can be older than
+These instructions ship with xflow CLI 1.8.1, 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
@@ -62,8 +62,8 @@ the error points away from the cause. The sections below carry the details.
 6. An already applied migration is never re-run, and `xflow db migrate` refuses a
    name it already holds with different content. A schema change is always a new file.
 7. When `xflow db migrate` answers `db_write_locked`, or an INSERT or CREATE TABLE in a
-   function fails with `database size limit ... reached` (53100), the database is over its plan
-   size and Postgres itself refuses. Reads, updates and deletes keep working, so the fix is deleting data
+   function fails with `database size limit ... reached` (53100), the organization's space
+   (databases and files together) is full and Postgres itself refuses. Reads, updates and deletes keep working, so the fix is deleting data
    (`xflow db exec` or a migration), never a rewrite of the SQL. Write comes back within the hour. The limit
    is shared by the organization: `xflow db list` shows the size of each project database.
 8. Heavy media does not travel with the sources. Photos, video and PDFs go up with
@@ -114,10 +114,13 @@ One folder per project, apps in subfolders:
 ## Plan limits
 
 The organization runs on a plan with limits: apps, active connections, people in the
-organization, database and file storage, function minutes, builds per month and at once, how often
+organization, space shared by databases and files, function minutes, builds per month and at once, how often
 schedules may run, and which access levels an app may have. The number of functions, schedules
 and projects is not capped; at most 15 new projects a day (UTC) per organization, deleted ones count. Most are finite; a plan
 may leave one uncapped, and then `whoami` prints `no limit` instead of a ceiling.
+A paid plan comes in packages (Start S/M/L, Business M/L/XL): the package sets the space,
+database hours and function minutes, the plan sets the rest. More space is a bigger package
+chosen by a person in «Тариф» (Plan); there is no separate purchase of space.
 `xflow whoami` prints every one of them next to what is used, and the rights of your own key
 with them: destroying data (a migration or `db exec`), deleting files from storage, moving a database and
 linking a connected account each need a right. Reading it before a long task turns a refusal
@@ -615,7 +618,8 @@ key to the frontend.
 
 - A name already taken in that folder is refused before the link is issued; `overwrite: true`
   replaces the bytes and keeps the address.
-- 200 MB per file and the storage quota of the organization, checked again on `confirm`.
+- 200 MB per file and the organization's space (databases and files together), checked again
+  on `confirm`.
 - Confirm only after the PUT has finished, and send on the PUT exactly the `Content-Type` you
   named: the link is signed for it, a different or missing type gets 403.
 - Assets only: pages, scripts and executables (`html`, `js`, `exe`, …) are refused with