@elmundi/ship-cli 0.14.1 → 0.14.2
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 +11 -3
- package/package.json +1 -1
package/lib/commands/run.mjs
CHANGED
|
@@ -412,7 +412,8 @@ curl -fsS -X POST '${apiBase}/v1/workspaces/${workspaceId}/agent-runs/finish' \\
|
|
|
412
412
|
${ticketLine}
|
|
413
413
|
${fsmLine}
|
|
414
414
|
"stage_next": "<next FSM stage, e.g. ba_requirements>",
|
|
415
|
-
"
|
|
415
|
+
"description": "<Full rewritten ticket body in Markdown — Problem / Goal / Acceptance criteria / Scope / Non-goals / Risks / etc. — when your role's job is to shape the ticket itself (intake, BA, planner). Omit (null) when your role is not supposed to rewrite the body.>",
|
|
416
|
+
"comment": "<One-paragraph audit narration of what you changed and why, ending with [Ship SDLC:${ctx?.role || "{{ROLE}}"}]. Do NOT paste the new description here — that's what the description field is for.>",
|
|
416
417
|
"summary": null,
|
|
417
418
|
"payload": {}
|
|
418
419
|
}
|
|
@@ -424,8 +425,15 @@ JSON
|
|
|
424
425
|
- **\`ready_next_step\`** — your role finished cleanly. Two shapes:
|
|
425
426
|
|
|
426
427
|
1. **You worked on a ticket.** Set \`ticket_ref\` and \`stage_next\`
|
|
427
|
-
to the next FSM stage; server moves the ticket
|
|
428
|
-
|
|
428
|
+
to the next FSM stage; server moves the ticket. If your role's
|
|
429
|
+
job is to shape the ticket (intake / BA / planner), set
|
|
430
|
+
\`description\` to the **full rewritten body** — the server
|
|
431
|
+
replaces the tracker description (Linear keeps the prior body
|
|
432
|
+
in the activity feed, so nothing is lost). Use \`comment\` for
|
|
433
|
+
a short audit narration of what changed and why; **do not put
|
|
434
|
+
the new spec text in a comment**, otherwise the ticket
|
|
435
|
+
description rots while comments accumulate. Pure-narration
|
|
436
|
+
roles (security-officer, retro) skip \`description\` entirely.
|
|
429
437
|
2. **There was nothing to do.** Pass \`ticket_ref: null\` and omit
|
|
430
438
|
\`stage_next\`. The server records the run in the audit log and
|
|
431
439
|
does **nothing** else — no inbox row, no tracker mutation. This
|