You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/product/error-conventions.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,6 +195,7 @@ These codes are the minimum stable set for the MVP:
195
195
-`RUN_FAILED`
196
196
-`DEPLOY_FAILED`
197
197
-`VERSION_UNAVAILABLE`
198
+
-`COMMAND_CANCELED`
198
199
199
200
Recommended meanings:
200
201
@@ -235,6 +236,7 @@ Recommended meanings:
235
236
-`RUN_FAILED`: local framework run command could not be started or exited unsuccessfully
236
237
-`DEPLOY_FAILED`: deployment or post-build health failed
237
238
-`VERSION_UNAVAILABLE`: CLI could not read its own bundled package metadata to report a version (defensive; not expected in normal installs)
239
+
-`COMMAND_CANCELED`: command execution was canceled by a runtime cancellation signal such as `SIGINT` or `SIGTERM`
238
240
239
241
## Exit Codes
240
242
@@ -243,9 +245,12 @@ The MVP should use these process exit codes:
243
245
-`0`: success
244
246
-`1`: runtime or command failure
245
247
-`2`: usage or configuration error
248
+
-`130`: command cancellation
246
249
247
250
Stable structured error codes, not exit code granularity, are the main branching surface for agents and CI.
248
251
252
+
Cancellation intentionally uses `130` instead of the generic runtime failure code because it has established shell semantics for interrupted commands and is useful to operators and process supervisors. Agents and CI should still branch on `COMMAND_CANCELED` rather than the numeric exit code.
0 commit comments