mirror of
https://github.com/software-mansion/argent.git
synced 2026-09-14 19:27:14 +08:00
Hubert Gancarczyk
2f2b47e598
`reached` is on the public `StepReport` and had exactly one consumer, the recorder's `reachedAStep`. Neither renderer of that type declared it: the MCP `FlowStepResult`, whose `flowRunToMcpContent` is the only content path for `flow-execute`, and the CLI `StepReport`, whose `renderStepLine` reads `warning` and never `reached`. A `flow-execute` cancelled after step 1 dispatched therefore rendered byte-identically to one cancelled before it -- `skip ... run aborted` in both -- which is the inference the field's own JSDoc exists to block. Both surfaces now suffix such a step with "(device may have moved)", mirroring how the sibling advisory field `warning` already reaches the status line.