Repository navigation
v0.300.2
A queued ship card no longer asks "weiter in ?". A kept ship whose summary carries do-ship's (Queue n/N) suffix now renders the plain merge heading without a Continue button.
Why: in a /do-run backlog run every ship is --queued and --keep, so each ship card asked to continue on its branch, and the user — who sees only this one thread and background agents — had to type "weiter" for a run that continues on its own. Rejected: a new card field for queue mode — the existing (Queue n/N) suffix already identifies the case.
Fixed
- Queued keep heading.
render_completion_cardresolves a queued kept ship to the plainship-successfulkey; a user-driven keep (no queue suffix) still asks "weiter in ?". - Docs. do-ship
completion-card-payloads.md§ Keep-mode variant: "Not for a queued ship".
Install: /plugin marketplace add Jerry0022/dotclaude