@getxflow/cli 0.3.2 → 0.3.3

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 = '0.3.1';
+exports.CLI_VERSION = '0.3.3';
 /** 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": "0.3.2",
+  "version": "0.3.3",
   "description": "CLI for the XFlow platform: source sync, deployment and publishing of applications",
   "license": "UNLICENSED",
   "engines": {

package/skills/xflow/SKILL.md

@@ -6,8 +6,9 @@ description: Build, deploy and publish apps on the XFlow platform with the xflow
 # XFlow
 
 Hosting for web apps. The code lives in an ordinary repository on the developer
-machine and is built locally; the platform takes the finished build and serves it.
-A platform project is recognized by the `xflow.json` file in its root.
+machine, `xflow deploy` sends the sources, and the platform builds them in a clean
+sandbox and serves the result as static files. A platform project is recognized by
+the `xflow.json` file in its root.
 
 ## First rule
 
@@ -134,6 +135,12 @@ separate deploy command: `xflow deploy` ships the functions and then builds the
 in that order. List what is live with `xflow functions list`. The handler returns
 `{ statusCode, body }` where `body` is a JSON string.
 
+Keep one shape inside that string across the whole project: `{ success: true, data }`
+when it worked, `{ success: false, error: { message, code } }` when it did not. Nothing
+enforces this, but a project where every function answers its own way costs an adapter
+on every call. Branch the frontend on `error.code`, never on `error.message`: wording
+gets rewritten on any edit, a code does not.
+
 The sources are the whole truth about which functions exist. Delete the directory and the
 next deploy deletes the function from the cloud, schedules included, and that cannot be
 undone: a function created again later gets a different address. So never remove a function
@@ -291,6 +298,10 @@ answers you get:
   and takes its real size from there, not from what you declared, so an early `confirm`
   answers that the file is not there.
 
+A refusal comes back as `{ error, code }`. Branch on `code` (`invalid_name`, `file_too_large`,
+`quota_exceeded`, `not_uploaded`, `duplicate_name`, `not_found`, …) and never on the text:
+the wording is free to change, the code is not.
+
 What the app may do with files is decided inside that function, because the page in the
 browser can be edited by whoever opened it. Never write the key into the sources and never
 send it to the frontend: the build gate stops on a key found in the application code, and a