v0.26.2

• Define how to tell a finite command from an event stream: a command producing more than one caller-needed output over time is an event stream, so it defaults to --output-to stdout and rejects an explicit split rather than stranding its data on the diagnostic stream
• Name the two shapes that qualify — a payload delivered in chunks whose batches carry the data, and an operation that reports an address the caller must act on before it can report its outcome — neither of which fits finite mode's limit of at most one terminal event
• State the invariant the policy protects: data the caller captures is never routed to the diagnostic stream, so a progress event carrying a payload the caller must read is an event stream that has not declared itself