signFMP4Direct closes its pipe reader on every return, so a signer that stops reading before the push ends can't leave the goroutine feeding it blocked forever. The harness's fMP4 push reports a non-200 answer from the node instead of a bare context cancellation.