layero 0.8.15 → 0.8.17

package/README.md

@@ -250,9 +250,13 @@ it means waiting for something that will not arrive.
 
 Not logged in? `deploy` starts the device-flow itself (`auth_required`).
 
-Errors carry a stable `code` (e.g. `not_logged_in`, `invalid_type`,
-`project_not_found`, `cli_deploys_disabled`) and a `next_action` hint so
-your agent can react without parsing prose.
+Errors carry a stable `code` (`auth_required`, `auth_expired`, `auth_timeout`,
+`project_unknown`, `project_not_found`, `cli_deploys_disabled`, `invalid_type`,
+`prebuilt_no_dir`, `prebuilt_no_index`, `deploy_not_started`, `deploy_failed`,
+`internal`, and a few command-specific ones) plus a `next_action` hint, so your
+agent can react without parsing prose. The failure code is assembled as
+`deploy_<status>` and a deploy only has `ready`, `building`, `failed` and
+`cancelled` — so `deploy_error` and `deploy_timed_out` do not exist.
 
 ## Ignore rules
 

package/dist/bin/layero.js

@@ -318,8 +318,8 @@ main().catch((err) => {
                 event: "error",
                 code: "internal",
                 next_action: debug
-                    ? "report at https://github.com/LayeroInfra/core/issues"
-                    : "re-run with --debug for a stack trace, or report at https://github.com/LayeroInfra/core/issues",
+                    ? "report at https://docs.layero.ru/contacts/"
+                    : "re-run with --debug for a stack trace, or report at https://docs.layero.ru/contacts/",
                 message,
             });
         }

package/dist/commands/init.js

@@ -49,11 +49,16 @@ stdout), the CLI auto-switches to JSON-lines. Key events to watch:
 
 Common error codes and remediation:
 
-- \`not_logged_in\` → run \`npx layero@latest login\`
+- \`auth_required\` → run \`npx layero@latest login\`, or set \`LAYERO_TOKEN\`
 - \`auth_expired\` / \`auth_timeout\` → user did not approve in time, re-run login
+- \`project_unknown\` → run from the project directory, or pass \`--project\`
 - \`invalid_type\` → drop \`--type\`, rely on auto-detect
 - \`cli_deploys_disabled\` → user must enable CLI deploys in project settings
-- \`deploy_failed\` / \`deploy_error\` → check the dashboard URL in the message
+- \`deploy_failed\` → check the dashboard URL in the message
+- \`internal\` → unexpected CLI error; re-run with \`--debug\`
+
+There is no \`not_logged_in\`, \`deploy_error\` or \`deploy_timed_out\` — do not
+branch on codes that are not listed here.
 
 ### Re-deploys and production
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "layero",
-  "version": "0.8.15",
+  "version": "0.8.17",
   "description": "Layero CLI — publish a local site with one command. No git, no GitHub, agent-friendly (Cursor, Claude Code).",
   "license": "MIT",
   "type": "module",