fix(kanban): neutral block-loop wording on the CLI, Desktop toast, wake text and docs
The sibling surfaces of the gateway ping rendered the same false claim: `hermes kanban block` said "needs a human decision", the Desktop toast title said "needs a decision", the wake status line (locales/*.yaml gateway.kanban.wake.block_loop_detected) said "needs a decision" and the docs described the triage route as "for a human decision". A repeated-block circuit breaker only establishes that orchestration attention is needed. Surface sweep from PR #111131 (notifier/test hunks dropped in favour of the typed-kind formatter from PR #111132).
This commit is contained in:
@@ -179,7 +179,7 @@ gateway:
|
||||
blocked: "blocked; needs attention"
|
||||
review_requested: "handed off for review; the implementation is done"
|
||||
changes_requested: "review requested changes (BLOCK); implementation is not approved"
|
||||
block_loop_detected: "routed to triage after repeated blocks; needs a decision"
|
||||
block_loop_detected: "routed to triage after repeated blocks; orchestration attention needed"
|
||||
status_default: "status changed"
|
||||
status_joiner: ", "
|
||||
message: "[kanban] Task {task_id} {status}.\nTitle: {title}\nAssignee: @{assignee}\nBoard: {board}\n\nCheck the result or decide the next step."
|
||||
|
||||
Reference in New Issue
Block a user