@elmundi/ship-cli 0.14.0 → 0.14.1
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/lib/commands/run.mjs +24 -8
- package/package.json +1 -1
package/lib/commands/run.mjs
CHANGED
|
@@ -421,20 +421,36 @@ JSON
|
|
|
421
421
|
|
|
422
422
|
### Outcomes
|
|
423
423
|
|
|
424
|
-
- **\`ready_next_step\`** — your role finished cleanly.
|
|
425
|
-
|
|
426
|
-
|
|
424
|
+
- **\`ready_next_step\`** — your role finished cleanly. Two shapes:
|
|
425
|
+
|
|
426
|
+
1. **You worked on a ticket.** Set \`ticket_ref\` and \`stage_next\`
|
|
427
|
+
to the next FSM stage; server moves the ticket and posts
|
|
428
|
+
\`comment\` if provided.
|
|
429
|
+
2. **There was nothing to do.** Pass \`ticket_ref: null\` and omit
|
|
430
|
+
\`stage_next\`. The server records the run in the audit log and
|
|
431
|
+
does **nothing** else — no inbox row, no tracker mutation. This
|
|
432
|
+
is the right outcome when a context-free routine (daily audit,
|
|
433
|
+
security sweep, retro) found no findings, OR when an FSM-stage
|
|
434
|
+
agent picked up no eligible ticket. **No work is not a blocker.**
|
|
435
|
+
|
|
427
436
|
- **\`needs_clarification\`** — you're waiting on a human. Set
|
|
428
437
|
\`comment\` with the question (server posts it) or omit it if you
|
|
429
438
|
already left the question via a separate read-only path. Server
|
|
430
439
|
tags the ticket \`needs:clarification\` so intake stops re-picking.
|
|
431
|
-
Status stays Todo. \`stage_next\` is ignored.
|
|
432
|
-
|
|
433
|
-
|
|
434
|
-
|
|
440
|
+
Status stays Todo. \`stage_next\` is ignored. Requires a
|
|
441
|
+
\`ticket_ref\`.
|
|
442
|
+
|
|
443
|
+
- **\`blocked\`** — **the environment is broken.** Use this only when
|
|
444
|
+
something on the runner side prevents the work from running:
|
|
445
|
+
missing secret, dead adapter, conflicting branch, tracker
|
|
446
|
+
unreachable, snyk/probe binary not installed, etc. Server drops a
|
|
447
|
+
blocker row into the inbox so an operator can fix the plumbing.
|
|
448
|
+
**Do not use \`blocked\` to mean "no findings" or "queue empty"**
|
|
449
|
+
— those are \`ready_next_step\` with \`ticket_ref: null\`.
|
|
450
|
+
|
|
435
451
|
- **\`out_of_scope\`** — the ticket is invalid or shouldn't be
|
|
436
452
|
processed. Server moves it to Done with optional \`comment\`.
|
|
437
|
-
\`stage_next\` is ignored.
|
|
453
|
+
\`stage_next\` is ignored. Requires a \`ticket_ref\`.
|
|
438
454
|
|
|
439
455
|
### Security
|
|
440
456
|
|