layero 0.8.16 → 0.8.17
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -250,9 +250,13 @@ it means waiting for something that will not arrive.
|
|
|
250
250
|
|
|
251
251
|
Not logged in? `deploy` starts the device-flow itself (`auth_required`).
|
|
252
252
|
|
|
253
|
-
Errors carry a stable `code` (
|
|
254
|
-
`project_not_found`, `cli_deploys_disabled
|
|
255
|
-
|
|
253
|
+
Errors carry a stable `code` (`auth_required`, `auth_expired`, `auth_timeout`,
|
|
254
|
+
`project_unknown`, `project_not_found`, `cli_deploys_disabled`, `invalid_type`,
|
|
255
|
+
`prebuilt_no_dir`, `prebuilt_no_index`, `deploy_not_started`, `deploy_failed`,
|
|
256
|
+
`internal`, and a few command-specific ones) plus a `next_action` hint, so your
|
|
257
|
+
agent can react without parsing prose. The failure code is assembled as
|
|
258
|
+
`deploy_<status>` and a deploy only has `ready`, `building`, `failed` and
|
|
259
|
+
`cancelled` — so `deploy_error` and `deploy_timed_out` do not exist.
|
|
256
260
|
|
|
257
261
|
## Ignore rules
|
|
258
262
|
|