mirror of
https://github.com/software-mansion/argent.git
synced 2026-09-14 19:27:14 +08:00
Hubert Gancarczyk
60c8edecbd
`execLeafStep` promoted a weak-pass note for `keyboard` and `run-sequence` steps. `flow-execute` is the third registered nested orchestrator and was not read: it keeps its sub-run's reports inside `result`, `flowExecuteOutcome` answers `undefined` on a green sub-run, and the CLI's `StepReport` has no `result` field — so a composed flow whose clear took an unverified path reported a clean green with the warning where nothing renders or counts it. `flow-add-step` records a raw `tool: flow-execute` step on four branches, so this is a spelling flows really carry. Reproduced on an API 36 emulator with the helper too old for the atomic path, against two real flows (an inner `tool: keyboard` clear, an outer `tool: flow-execute`): before OUTER step 0 pass flow-execute warning=NONE after OUTER step 0 pass flow-execute warning=keyboard clear: the atomic … Nested `warning`s are taken whole rather than filtered to `keyboard` notes: unlike a `note`, that field already means one thing — this step passed in a way that weakens it as proof — and the sub-run's own `execLeafStep` has applied the tool rule at its level, so composition to any depth needs no second rule. Repeats are dropped. The enumeration now lives in one function, since three docblocks name it: both `StepReport.warning`s and the `flow-execute` tool description said the note reaches a report three ways, and this is the fourth.