yes, but a flow must eventually terminate

call t synchronously on deref and that's a perfectly valid flow

It's intended to be continuous, do I really have to terminate?

what does (m/cp 42) do

it does exactly that : notify, then terminate on deref

if you don't terminate, consumers will assume the process is still holding resources and wait forever

IIUC, signaling terminate will notify again, causing the consumer to await a terminal value, which means here we would see 42 a second time

a consumer must not call deref after terminate

ok, so the first 42 is the terminal value

yes